io.github.AshutoshRaj97/agentready-mcp
REMOTE · WWW.AGENTREADY.IT.COM · 2 COMPONENTS · SCANNED AUG 3
Query any docs site via MCP. Submit a URL, ask questions, get cited answers.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 763 tokens (~109/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.agentready.it.com
claude mcp add --transport http ashutoshraj97-agentready-mcp https://www.agentready.it.com/api/mcp
[mcp_servers.ashutoshraj97-agentready-mcp] url = "https://www.agentready.it.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ashutoshraj97-agentready-mcp": {
"type": "remote",
"url": "https://www.agentready.it.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add ashutoshraj97-agentready-mcp --url https://www.agentready.it.com/api/mcp --transport streamable-http
mcp_servers:
ashutoshraj97-agentready-mcp:
url: "https://www.agentready.it.com/api/mcp" {
"mcpServers": {
"ashutoshraj97-agentready-mcp": {
"type": "http",
"url": "https://www.agentready.it.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
First indexed and scored.
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 3 Aug 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 | 21 Jun 2026 | 19 Sept 2026 | RSA 2048 | SHA256-RSA | 5934869ce40e1ec3d5ec60693f1fb4ed124 |
| 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 |
DNSSEC insecure
Validation of www.agentready.it.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| it.com. | present | 2371 | 13 | Verified |
| agentready.it.com. | absent | 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 |
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 |
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.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain of the site to query (e.g. "stripe.com"). Accepts full URLs too. |
| query | string | yes | The question to ask about the site. |
| url | string | — | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain of the indexed site (e.g. "docs.example.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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain of the indexed site (e.g. "docs.example.com"). Accepts full URLs too. |
| request | string | yes | Natural-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.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | — | Optional short explanation. |
| domain | string | yes | Domain that was queried. |
| rating | integer | yes | Answer quality from 1 to 5. |
| request_id | string | — | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the site to index (e.g. "https://docs.example.com"). |
No output schema declared.
No examples provided.