Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.AshutoshRaj97/agentready-mcp

REMOTE · WWW.AGENTREADY.IT.COM · 2 COMPONENTS

Query any docs site via MCP. Submit a URL, ask questions, get cited answers.

0 this week 80 Trust /100

Last scanned (14 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability85
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 898 tokens (~112/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Aug 26 0
    • DNSSEC: DNSSEC check failed: this domain isn't protected by DNSSEC. security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://www.agentready.it.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.agentready.it.com CN=YR1,O=Let's Encrypt,C=US 24 Oct 2026 22 Jan 2027 RSA 2048 SHA256-RSA 6f1f9fa21933d5951d63227e0aa6f1919a6
SANs: www.agentready.it.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.agentready.it.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
it.com. DS published 15253 13 Verified
agentready.it.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.agentready.it.com/api/mcp Verified 200
http (plaintext) http://www.agentready.it.com/api/mcp HTTPS enforced 308 https://www.agentready.it.com/api/mcp
MCP tools · 8 exposed · ~898 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ask_site ~194

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.

NameTypeReqDescription
domainstringyesDomain of the site to query (e.g. "stripe.com"). Accepts full URLs too.
querystringyesThe question to ask about the site.
urlstring–Optional: a specific page URL to focus on. AgentReady will ensure this page is indexed before answering.

No output schema declared.

No examples provided.

get_site_capabilities ~77

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.

NameTypeReqDescription
domainstringyesDomain of the indexed site (e.g. "docs.example.com"). Accepts full URLs too.

No output schema declared.

No examples provided.

get_site_facts ~135

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.

NameTypeReqDescription
categorystring–Optional: filter facts to a single category.
domainstringyesDomain of the indexed site (e.g. "stripe.com"). Accepts full URLs too.

No output schema declared.

No examples provided.

list_sites ~67

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_site_action ~108

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.

NameTypeReqDescription
domainstringyesDomain of the indexed site (e.g. "docs.example.com"). Accepts full URLs too.
requeststringyesNatural-language request to plan against the site.

No output schema declared.

No examples provided.

rate_answer ~104

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.

NameTypeReqDescription
commentstring–Optional short explanation.
domainstringyesDomain that was queried.
ratingintegeryesAnswer quality from 1 to 5.
request_idstring–request_id returned by ask_site, when available.

No output schema declared.

No examples provided.

refresh_site ~94

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.

NameTypeReqDescription
domainstringyesDomain of the site to refresh (e.g. "docs.example.com").

No output schema declared.

No examples provided.

submit_site ~119

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.

NameTypeReqDescription
urlstringyesFull URL of the site to index (e.g. "https://docs.example.com").

No output schema declared.

No examples provided.

Install

How do I install the io.github.AshutoshRaj97/agentready-mcp server?

io.github.AshutoshRaj97/agentready-mcp is a hosted endpoint at https://www.agentready.it.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.agentready.it.com

# add to Claude Code
claude mcp add --transport http ashutoshraj97-agentready-mcp 'https://www.agentready.it.com/api/mcp'
Common questions

What is the io.github.AshutoshRaj97/agentready-mcp server?

io.github.AshutoshRaj97/agentready-mcp is listed in the public MCP registry as io.github.AshutoshRaj97/agentready-mcp. Query any docs site via MCP. Submit a URL, ask questions, get cited answers. This page covers its hosted endpoint (https://www.agentready.it.com/api/mcp).

Is the io.github.AshutoshRaj97/agentready-mcp server safe to use?

io.github.AshutoshRaj97/agentready-mcp scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.AshutoshRaj97/agentready-mcp server expose?

io.github.AshutoshRaj97/agentready-mcp exposes 8 tools: list_sites, get_site_capabilities, plan_site_action, submit_site, ask_site, and 3 more. Their descriptions and schemas cost roughly 898 tokens of context every time the server is loaded.

Does the io.github.AshutoshRaj97/agentready-mcp server require authentication?

No. We connected to io.github.AshutoshRaj97/agentready-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.AshutoshRaj97/agentready-mcp server still maintained?

io.github.AshutoshRaj97/agentready-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.AshutoshRaj97/agentready-mcp server?

VerifyMCP ran 12 checks on io.github.AshutoshRaj97/agentready-mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.AshutoshRaj97/agentready-mcp: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.