Other · Remote MCP server

Agent Ready

Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.

Visit Agent Ready's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.mlava/agent-ready-mcp
Version
0.7.7
Status
Active
Category
other
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-09-07
Updated
2026-09-07
Publisher
mlava (GitHub) · 2 servers with pages here
Website
agent-ready.dev
Repository
github.com/mlava/agent-ready-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://agent-ready.dev/api/v1/mcpNone

Packages

RegistryPackageVersionTransportEnvironment variables
npmagent-ready-mcp0.7.7stdioAGENT_READY_API_KEY (secret)

How to connect Agent Ready

Agent Ready is a remote MCP server: there is nothing to install. Its endpoint is https://agent-ready.dev/api/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: agent-ready-mcp version 0.7.7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y agent-ready-mcp@0.7.7. It reads the environment variable AGENT_READY_API_KEY (secret); set it in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "agent-ready-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agent-ready-mcp@0.7.7"
      ],
      "env": {
        "AGENT_READY_API_KEY": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from mlava (GitHub)

ServerRunsEndpoint or package
Scholar SidekickCatch AI-fabricated citations (real DOI + fake title). Retraction, open-access, 10,000+ CSL styles.Remote & Local · HTTP, stdioscholar-sidekick.com

More other servers

All 6,730 →
ServerRunsEndpoint or package
Agent Placement TrialStart a 7-day placement trial: card on file, cancel anytime, measured agent hops.Remote · HTTPagent-observatory-sensor.nolimit-observatory.workers.dev
Agent PreflightSix paid URL-intelligence tools for autonomous agents and agent swarms.Remote · HTTPpreflight.lorensaisolutions.com
Agent ProvenanceGenesis certificates, lineage, and cascading recalls: birth certificates + bloodlines for the agent.Remote · HTTPmcp.viridisconservation.com
Agent ReadinessScores any public website on how usable it is by AI agents, with per-check evidence.Remote · HTTPwebmcp-tool.com
Agent Ready KitAgent-readiness scanner (0-5 score), robots.txt + llms.txt generators, managed agent enablement.Remote · HTTPmudko.com
Agent Ready Website CheckCheck whether a website is readable by AI agents: robots, llms.txt, sitemap, HTML. Bounded.Remote · HTTPagent-observatory-sensor.nolimit-observatory.workers.dev
Agent ReceiptsIssue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.Remote · HTTPagent-receipts.dropwatchhq.com
Agent Receipts MCPEU AI Act-ready audit trail: signed, tamper-evident receipts proving what your AI agents did.Local · stdionpm: agent-receipts-mcp