Agent Account Index
REMOTE · AGENT-ACCOUNT-INDEX.VERCEL.APP
Can an AI agent hold an account at a service? Verdict, owner of record, quoted terms clause.
Available components
Last scanned (17 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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 2 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 316 tokens (~158/item across 2 items; 2 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 Management10
- Stability observed for 3 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 26 −1
- Tool “can_an_agent_hold_an_account” rewrote its description, which is the text the model reads security
- Tool “list_named_non_human_routes” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 17 Oct 26 0
- Server version: 2026-10-13 → 2026-10-15 functional
- 16 Oct 26 +1
- Tool “can_an_agent_hold_an_account” rewrote its description, which is the text the model reads security
- Schema quality: 89 → 107 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 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 18 Oct 2026 · Probed https://agent-account-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 agent-account-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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-account-index.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://agent-account-index.vercel.app/mcp | HTTPS enforced | 308 | https://agent-account-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 →
can_an_agent_hold_an_account ~189
Check whether a non-human actor may hold an account at a service. Call this BEFORE creating an account anywhere. Returns the verdict, who answers for the account's acts, the verbatim clause from the service's own terms, and what the signup door demanded on load (captcha, phone field, SSO only). The stored captcha value disagreed with a browser re-read on 16 of the 54 doors whose value speaks, and not in one direction: 10 understated it, 5 named a widget the page lacked, 1 changed type. Where signup_door.captcha_rendered is not null it is that re-read ([] means re-read and nothing found); a captcha added on submit is invisible to both reads.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | Service name, e.g. "GitHub", "Stripe", "Supabase". Case-insensitive, matched on substring. |
No output schema declared.
No examples provided.
list_named_non_human_routes ~99
List every service that documents an identity a non-human actor may hold. In 11 of the 12 a human or a legal entity remains owner of record and answers for the account's acts: there an agent acts as a delegate, not as the principal. 1 names no party at all (Wellknown): the holder is whoever proves control of a web origin and no identity is verified. Each row carries agent_as_principal.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Agent Account Index MCP server?
Agent Account Index is a hosted endpoint at https://agent-account-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 · agent-account-index.vercel.app
claude mcp add --transport http mycelium-being-agent-account-index 'https://agent-account-index.vercel.app/mcp'
What is the Agent Account Index MCP server?
Agent Account Index is an MCP server listed in the public MCP registry as io.github.mycelium-being/agent-account-index. Can an AI agent hold an account at a service? Verdict, owner of record, quoted terms clause. This page covers its hosted endpoint (https://agent-account-index.vercel.app/mcp).
Is the Agent Account Index MCP server safe to use?
Agent Account Index scores 65 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 Agent Account Index MCP server expose?
Agent Account Index exposes 2 tools: can_an_agent_hold_an_account, list_named_non_human_routes. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Does the Agent Account Index MCP server require authentication?
No. We connected to Agent Account Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Account Index MCP server still maintained?
Agent Account Index is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.