io.github.agentwares/agent-access-index
REMOTE · AGENTWARES-ACCESS-INDEX.VERCEL.APP · SCANNED SEP 25
Whether an AI agent may fetch a URL, on what terms, and at what price. Free, no key, no signup.
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 → Why this is hard to 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 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. 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 Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · agentwares-access-index.vercel.app
claude mcp add --transport http agentwares-agent-access-index 'https://agentwares-access-index.vercel.app/mcp'
{
"mcpServers": {
"agentwares-agent-access-index": {
"url": "https://agentwares-access-index.vercel.app/mcp"
}
}
} {
"servers": {
"agentwares-agent-access-index": {
"type": "http",
"url": "https://agentwares-access-index.vercel.app/mcp"
}
}
} [mcp_servers.agentwares-agent-access-index] url = "https://agentwares-access-index.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agentwares-agent-access-index": {
"type": "remote",
"url": "https://agentwares-access-index.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add agentwares-agent-access-index --url 'https://agentwares-access-index.vercel.app/mcp' --transport streamable-http
mcp_servers:
agentwares-agent-access-index:
url: "https://agentwares-access-index.vercel.app/mcp" {
"McpServers": {
"agentwares-agent-access-index": {
"Transport": "http",
"Url": "https://agentwares-access-index.vercel.app/mcp"
}
}
} assistant mcp add agentwares-agent-access-index -t streamable-http -u 'https://agentwares-access-index.vercel.app/mcp'
{
"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.
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.
- 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
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 19 Sept 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.
- 17 Sept 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.
- 15 Sept 26 +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.
- 13 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 192 → 212 ▼ functional
- 12 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 25 Sept 2026 · Probed https://agentwares-access-index.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentwares-access-index.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | 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; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentwares-access-index.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://agentwares-access-index.vercel.app/mcp | HTTPS enforced | 308 | https://agentwares-access-index.vercel.app/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. 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 →
access_check_url Check whether an agent may fetch a URL ~283
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Absolute http(s) URL of the page to check, e.g. https://example.com/article |
No output schema declared.
No examples provided.
access_explain_verdicts What the verdicts mean ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
access_list_agents AI user-agents this index reports on ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.