Home / MCP registry index / io.github.mlava/agent-ready-mcp

Agent Ready

io.github.mlava/agent-ready-mcp in the official MCP registry. Endpoint https://agent-ready.dev/api/v1/mcp. Source: github.com/mlava/agent-ready-mcp.

The registry describes it as: Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.

Not read yet. The index re-reads every listed server about once a week, and this one is in the queue. You can check it yourself right now.

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mlava-agent-ready-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mlava-agent-ready-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Vercel and Netlify MCP servers

Sandbox Timer
com.botrecipe/timer
5 tools, nothing matched
2026-10-22
co.encorehq/encore-pages
co.encorehq/encore-pages
needs credentials to list tools
2026-10-22
com.edgethirteen.www/vercelpycheck
com.edgethirteen.www/vercelpycheck
not read yet
Mode VC Chart: Vercel AI SDK Downloads vs. the Lab SDKs
com.modevc/chart-vercel-ai-sdk-downloads-vs-lab-sdks
not read yet
com.vercel/vercel-mcp
com.vercel/vercel-mcp
not read yet
io.github.holiday-forever/holiday-photo-plus
io.github.holiday-forever/holiday-photo-plus
not read yet