# io.github.AshutoshRaj97/agentready-mcp (remote · www.agentready.it.com)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.agentready.it.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ashutoshraj97-agentready-mcp/api-mcp.md), [page](https://verifymcp.io/servers/ashutoshraj97-agentready-mcp/api-mcp)
- npm · `@agentreadyweb/mcp`: 39/100, [markdown](https://verifymcp.io/servers/ashutoshraj97-agentready-mcp/agentreadyweb-mcp.md), [page](https://verifymcp.io/servers/ashutoshraj97-agentready-mcp/agentreadyweb-mcp)

## Channel facts

- Endpoint: `https://www.agentready.it.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 763 tokens (~109/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http ashutoshraj97-agentready-mcp https://www.agentready.it.com/api/mcp
```

### Codex

```toml
[mcp_servers.ashutoshraj97-agentready-mcp]
url = "https://www.agentready.it.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ashutoshraj97-agentready-mcp": {
      "type": "remote",
      "url": "https://www.agentready.it.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ashutoshraj97-agentready-mcp --url https://www.agentready.it.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ashutoshraj97-agentready-mcp:
    url: "https://www.agentready.it.com/api/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +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.

### 2026-08-01 (score 69, +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.

### 2026-07-31 (score 68, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +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.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (7)

### `list_sites` (~67 tokens)

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.

### `get_site_capabilities` (~77 tokens)

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.

Input parameters:

- `domain` (string, required): Domain of the indexed site (e.g. "docs.example.com"). Accepts full URLs too.

### `plan_site_action` (~108 tokens)

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.

Input parameters:

- `domain` (string, required): Domain of the indexed site (e.g. "docs.example.com"). Accepts full URLs too.
- `request` (string, required): Natural-language request to plan against the site.

### `submit_site` (~119 tokens)

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.

Input parameters:

- `url` (string, required): Full URL of the site to index (e.g. "https://docs.example.com").

### `ask_site` (~194 tokens)

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.

Input parameters:

- `domain` (string, required): Domain of the site to query (e.g. "stripe.com"). Accepts full URLs too.
- `query` (string, required): 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.

### `refresh_site` (~94 tokens)

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.

Input parameters:

- `domain` (string, required): Domain of the site to refresh (e.g. "docs.example.com").

### `rate_answer` (~104 tokens)

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.

Input parameters:

- `comment` (string): Optional short explanation.
- `domain` (string, required): Domain that was queried.
- `rating` (integer, required): Answer quality from 1 to 5.
- `request_id` (string): request_id returned by ask_site, when available.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ashutoshraj97-agentready-mcp/api-mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 66
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://www.agentready.it.com/api/mcp
- Repository: https://github.com/AshutoshRaj97/agentready-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ashutoshraj97-agentready-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ashutoshraj97-agentready-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ashutoshraj97-agentready-mcp/api-mcp