Agentready MCP is listed as active in the registry but did not answer our last check. 90 installs a week from npm. It exposes 8 tools. Last commit 15 Aug 2026.
Query any docs site via MCP. Submit a URL, ask questions, get cited answers.
Installs per day
peak 37 · avg 10 · -11% w/w
a month agotoday
Uptime history
91 days of history · worst day 0%
91 days agonow
6.6%
Uptime 24h
6 of 91 checks
8
Tools
read from the server
510 ms
Response time
average over 24h
90
Installs / week
npm and PyPI
What changed 2
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 August 2026. No other catalogue keeps this.
13 Aug
a tool appeared
get_site_facts
13 Aug
a tool changed version
Agentready MCP does not always answer
Over the last week it answered 5.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.
run in your terminal
claude mcp add agentready-mcp --transport http https://www.agentready.it.com/api/mcpSettings → Connectors → Add custom connector, then paste this address
https://www.agentready.it.com/api/mcp~/.codex/config.toml
[mcp_servers.agentready-mcp]
url = "https://www.agentready.it.com/api/mcp".cursor/mcp.json
{
"mcpServers": {
"agentready-mcp": {
"url": "https://www.agentready.it.com/api/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"agentready-mcp": {
"type": "http",
"url": "https://www.agentready.it.com/api/mcp"
}
}
}Available tools 8
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
site
get_site_capabilities
Return the AgentReady capability manifest for a website. If the site is not indexed yet, AgentReady indexes it automatically before returning its freshness, read-only limits, schemas, and available MCP and HTTP endpoints.
get_site_facts
Return structured facts extracted from a website — pricing, limits, features, contact info, and more. Facts marked as "owner-verified" have been explicitly attested by the site owner and are guaranteed accurate ground truth; use these in preference to scraped RAG answers for critical comparisons. Ideal for price comparison across multiple sites, feature matrix lookups, or any task where you need structured data rather than a natural-language synthesis.
ask
ask_site
Query any website's documentation and get cited, multi-page answers in natural language. Use ask_site when you need: (1) answers that synthesize information across multiple pages of a site, (2) documentation from JS-rendered sites (React, Next.js, Vue SPAs) where web_fetch returns empty or partial HTML, (3) citations linking back to the exact source pages, (4) faster results than fetching and reading individual pages one by one. For sites not yet indexed, ask_site auto-crawls and answers in ~60s — no separate submit_site call needed.
plan
plan_site_action
Turn a natural-language request into a grounded, read-only AgentReady plan for a website. If the site is not indexed yet, AgentReady indexes it automatically first. This prototype never executes side effects; it identifies supported steps, sources, risks, and whether a future execution would require confirmation.
rate
rate_answer
Rate the quality of a previous ask_site answer from 1 (not useful) to 5 (excellent). Pass the request_id returned in structuredContent when available so the rating can be tied to the exact answer.
refresh
refresh_site
Force a full re-crawl of a site to pick up new or changed content. If the site has never been indexed, AgentReady performs the initial indexing automatically. Use when ask_site returns outdated information or when you know the site has recently been updated. Takes ~60 seconds. After completion, ask_site returns fresh content.
sites
list_sites
List all websites currently indexed in AgentReady. Use this to check if a domain is already available before submitting it — indexed sites return instant cited answers via ask_site. The index covers developer tools, APIs, cloud platforms, frameworks, databases, and more, and grows as new sites are submitted.
submit
submit_site
Index any website so it can be queried with ask_site. Use this when the site is not yet in list_sites. Handles JS-rendered pages (React, Next.js, Vue SPAs) that web_fetch cannot read — uses a four-layer pipeline: llms.txt → HTTP+cheerio → __NEXT_DATA__ extraction → Jina Reader headless browser. Takes ~60 seconds. Once indexed, ask_site queries are instant.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://www.agentready.it.com/api/mcp | streamable-http | answering | 76 ms | 14 min ago |
Alternatives to Agentready MCP
same job, measured the same wayDomotz MCP
by servosity
Every Domotz endpoint, plus a local SQLite fleet mirror that answers cross-site questions.
repo2graph
by srinivasan-78
Ask a codebase a question, get back the source that answers it — every block cited to file:line.
Hwip
by hwipit
Notify your phone, ask questions and get answers back from AI coding agents via Hwip.
Vibe BI MCP
by vibe-bi
Ask business questions in plain English. Get instant answers from your database, no SQL needed.
Site
by consentvia
Consentvia: the site's own MCP server — dataset; every answer cites the site.
Site
by subsroom
Subsroom: the site's own MCP server — dataset; every answer cites the site.
Grounded Support Agent
by ankit512
Governed support MCP: answers only KB-grounded questions with citations, escalates the rest.
Printags docs
by printags
Answers questions about Printags cards, prices, ordering, the API and MCP servers. Read-only.
Agentready MCP — questions
Answers built from our own checks of this server.
What can Agentready MCP do?
It exposes 8 tools, read directly from the server on our last check. Among them: ask_site, get_site_capabilities, get_site_facts, list_sites, plan_site_action, rate_answer and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Agentready MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 6 of 91 checks got a reply (6.6%), average response time 510 ms. The bar chart above shows every period we have measured.
The registry lists Agentready MCP as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Agentready MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agentready MCP need an API key?
No. Agentready MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agentready MCP?
It answers our handshake in 510 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Agentready MCP?
The npm package @agentreadyweb/mcp was installed 90 times in the last week. Week over week that is -11%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Agentready MCP open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at agentready.it.com, which runs on its operator's own terms.