protogrid

Search / io.github.mycelium-being/agent-account-index

Agent Account Index

R0· no sign-in

Can an AI agent hold an account at a service? Verdict, owner of record, quoted terms clause.

v2026-10-12 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality69new
Trust80of 100
Uptime, 30 days100%
Latency p50333 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "agent-account-index": {
      "type": "http",
      "url": "https://agent-account-index.vercel.app/mcp"
    }
  }
}
claude mcp add --transport http agent-account-index https://agent-account-index.vercel.app/mcp
[mcp_servers.agent-account-index]
url = "https://agent-account-index.vercel.app/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agent-account-index": {
      "type": "remote",
      "url": "https://agent-account-index.vercel.app/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "agent-account-index": {
      "type": "http",
      "url": "https://agent-account-index.vercel.app/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=agent-account-index&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYWdlbnQtYWNjb3VudC1pbmRleC52ZXJjZWwuYXBwL21jcCJ9"
}
{
  "servers": {
    "agent-account-index": {
      "type": "http",
      "url": "https://agent-account-index.vercel.app/mcp"
    }
  }
}
{
  "mcpServers": {
    "agent-account-index": {
      "httpUrl": "https://agent-account-index.vercel.app/mcp"
    }
  }
}
extensions:
  "agent-account-index":
    enabled: true
    name: "agent-account-index"
    type: streamable_http
    uri: "https://agent-account-index.vercel.app/mcp"
    timeout: 300

Quality 69 / 100new

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene64 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_named_non_human_routes (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); can_an_agent_hold_an_account (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 506 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool history recorded for 5 of the 7 days needed
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

2 tools, about 506 tokens to load them all · tool set 6aa6bb4cc283 · tools last changed 2026-10-18 · checked 2026-10-20 15:57 UTC

Tool changes

  • can_an_agent_hold_an_accountchangeddescription
    before

    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.

    after · 55% of words in common

    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. Read those against their own denominators: the 34 doors storing none_seen were wrong 10 times and the 20 storing a vendor name 6 times, about the same rate either way, so a disagreement does not say which reading to lean on. 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. These six integers are typed here and live in captcha_recheck_counts at the top of /index.json, which is the copy to trust. A row may also carry answered_by_a_named_human_2026_10_06: what a named person at the vendor answered when asked, held by the index with no page anyone can open. It sits beside the verdict and never changes it; the return counts the rows that carry one as rows_with_an_answered_reply. Null means nobody there was asked, which is not a finding.

  • list_named_non_human_routeschangeddescription
    before

    List every service that documents an identity a non-human actor may hold. In every one found so far a human or legal entity remains owner of record and answers for the account's acts: an agent can act as a delegate, never as a principal.

    after · 53% of words in common

    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.

  • can_an_agent_hold_an_accountchangeddescriptionmeaning changed
    before

    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; 'none seen on load' is a floor, many services add a captcha on submit).

    after · 49% of words in common

    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.

  • can_an_agent_hold_an_accountchangeddescription
    before

    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, and the verbatim clause from the service's own terms.

    after · 62% of words in common

    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; 'none seen on load' is a floor, many services add a captcha on submit).

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 80 / 100

no-repository
provenance45
liveness100
freshness100
hygiene80

+website +reachable +uptime-100% +updated-6d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://agent-account-index.vercel.app/mcp streamable-httpnoneyes100%333 ms2025-06-182026-10-20

Tools (2)

can_an_agent_hold_an_accountCheck 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. Read those against their own denominators: the 34 doors storing none_seen were wrong 10 times and the 20 storing a vendor name 6 times, about the same rate either way, so a disagreement does not say which reading to lean on. 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. These six integers are typed here and live in captcha_recheck_counts at the top of /index.json, which is the copy to trust. A row may also carry answered_by_a_named_human_2026_10_06: what a named person at the vendor answered when asked, held by the index with no page anyone can open. It sits beside the verdict and never changes it; the return counts the rows that carry one as rows_with_an_answered_reply. Null means nobody there was asked, which is not a finding.
list_named_non_human_routesList 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.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "io.github.mycelium-being/agent-account-index",
  "title": "Agent Account Index",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://agent-account-index.vercel.app/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "2026-10-12",
  "websiteUrl": "https://agent-account-index.vercel.app",
  "description": "Can an AI agent hold an account at a service? Verdict, owner of record, quoted terms clause."
}