# io.github.agentwares/agent-access-index (remote · agentwares-access-index.vercel.app)

Whether an AI agent may fetch a URL, on what terms, and at what price. Free, no key, no signup.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `agentwares-access-index.vercel.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/agentwares-agent-access-index/agentwares-access-index.md), [page](https://verifymcp.io/servers/agentwares-agent-access-index/agentwares-access-index)

## Channel facts

- Endpoint: `https://agentwares-access-index.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-09-25.

- **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 3 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 638 tokens (~212/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.agentwares/agent-access-index MCP server?

io.github.agentwares/agent-access-index is a hosted endpoint at https://agentwares-access-index.vercel.app/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.

### Claude

```bash
claude mcp add --transport http agentwares-agent-access-index 'https://agentwares-access-index.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "agentwares-agent-access-index": {
      "url": "https://agentwares-access-index.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "agentwares-agent-access-index": {
      "type": "http",
      "url": "https://agentwares-access-index.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.agentwares-agent-access-index]
url = "https://agentwares-access-index.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agentwares-agent-access-index": {
      "type": "remote",
      "url": "https://agentwares-access-index.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add agentwares-agent-access-index --url 'https://agentwares-access-index.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  agentwares-agent-access-index:
    url: "https://agentwares-access-index.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "agentwares-agent-access-index": {
      "Transport": "http",
      "Url": "https://agentwares-access-index.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add agentwares-agent-access-index -t streamable-http -u 'https://agentwares-access-index.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "agentwares-agent-access-index": {
      "type": "http",
      "url": "https://agentwares-access-index.vercel.app/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-09-25 (score 71, 0)

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

### 2026-09-24 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 69, +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-09-17 (score 68, +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-09-15 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 192 → 212

### 2026-09-12 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `access_check_url` (~283 tokens)

Check whether an agent may fetch a URL

Given a URL, say whether an AI agent may fetch it, on what terms, and at what price.
Reads robots.txt for a generic agent and for every AI user-agent the operators document,
the Content-signal and Content-Usage directives, any RSL licence the origin links, and
the live response to an honestly-identified request.

Verdicts: `allowed` (it served us), `allowed_if_identified` (the written policy permits
this but bot management refused an anonymous request — signing as a named crawler is the
documented route), `charged` (there is a price, quoted where the rail will show one),
\`blocked` (the site disallows the agents that would want this, with nothing to buy), and
\`unknown` (the origin did not answer, or the URL is not there).

Never evades: no CAPTCHA solving, no proxies, no spoofed user-agents. Refusals come back
as findings with the evidence attached.

Input parameters:

- `includeEvidence` (boolean): Include every request made, with status and headers (default false: it is large)
- `skipWellKnown` (boolean): Skip the five well-known probes; faster, and they are almost always absent
- `url` (string, required): Absolute http(s) URL of the page to check, e.g. https://example.com/article

### `access_explain_verdicts` (~63 tokens)

What the verdicts mean

Return the five verdicts this index can return, what each one means for an agent that has just been refused, and what the agent's next move is for each. Costs nothing and makes no request; call it once to interpret access_check_url results.

### `access_list_agents` (~56 tokens)

AI user-agents this index reports on

Return the AI crawler tokens this index reads robots.txt rules for — only tokens their operators document — plus the widely-written tokens that no operator sends, which make a robots rule unenforceable. Useful when writing or auditing a robots.txt.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/agentwares-agent-access-index/agentwares-access-index#diagnostics

## Score history

- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69
- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 66
- 2026-09-11: 65

## Common questions

### What is the io.github.agentwares/agent-access-index MCP server?

io.github.agentwares/agent-access-index is an MCP server listed in the public MCP registry as io.github.agentwares/agent-access-index. Whether an AI agent may fetch a URL, on what terms, and at what price. Free, no key, no signup. This page covers its hosted endpoint (https://agentwares-access-index.vercel.app/mcp).

### Is the io.github.agentwares/agent-access-index MCP server safe to use?

io.github.agentwares/agent-access-index scores 71 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.agentwares/agent-access-index MCP server expose?

io.github.agentwares/agent-access-index exposes 3 tools: access_check_url, access_explain_verdicts, access_list_agents. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.

### Does the io.github.agentwares/agent-access-index MCP server require authentication?

No. We connected to io.github.agentwares/agent-access-index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.agentwares/agent-access-index MCP server still maintained?

io.github.agentwares/agent-access-index is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agentwares-access-index.vercel.app/mcp
- Repository: https://github.com/agentwares/servers
- Website: https://agentwares-access-index.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/agentwares-agent-access-index/agentwares-access-index.xml
- Changelog JSON feed: https://verifymcp.io/servers/agentwares-agent-access-index/agentwares-access-index.json
- HTML version of this page: https://verifymcp.io/servers/agentwares-agent-access-index/agentwares-access-index