AgentReady MCP

AgentReady checks whether AI agents can reach and read a website. It provides a scan tool that returns a JSON report including a score, complete status, specific checks, and agent details. Results are cached for 15 minutes, and there is a limit of 10 scans per hour per client.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by AgentReady

You need:Limit: 10 scans per hour per client

MCP endpoint (Streamable HTTP)

https://agentready.agentready.workers.dev/mcp

Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (1)

check_website

1 of 1 have a description · 0 of 1 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 7:09 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Check if AI agents can reach and read a website
Get a score and report on website accessibility for agents
Identify problems found and fixes for agent access

Source and maintenance

Community listingRegistry 1.0.0

mcp-registry: io.github.puluceno/agentready@1.0.0 Project website

Protocol and capabilities

Server: agentready 1.0.0
MCP protocol negotiated in check: 2025-11-25
Tools: 1 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Tools

1 advertised

check_website

Advertised by the server during the last successful anonymous check.

Check whether AI agents (ChatGPT, Claude, Perplexity) can reach and read a website: robots.txt rules per agent, firewall blocking, content without JavaScript, structured data. Returns a 0-100 score, the problems found, and how to fix them.

check_website input schema

{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Website address, for example example.com"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 236 ms
95th percentile latency: 236 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 7:09 PM UTC · probe · passed · 236 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http agentready-mcp-workers https://agentready.agentready.workers.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add agentready-mcp-workers --url https://agentready.agentready.workers.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable agentready-mcp-workers in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "agentready-mcp-workers": {
      "url": "https://agentready.agentready.workers.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "agentready-mcp-workers": {
      "type": "streamableHttp",
      "url": "https://agentready.agentready.workers.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start agentready-mcp-workers and inspect its tools.

VS Code configuration

{
  "servers": {
    "agentready-mcp-workers": {
      "type": "http",
      "url": "https://agentready.agentready.workers.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http agentready-mcp-workers https://agentready.agentready.workers.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://agentready.agentready.workers.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "agentready-mcp-workers": {
      "serverUrl": "https://agentready.agentready.workers.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like AgentReady MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 5,158