MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

Agent Account Index

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

Checks passed
11 / 22

3 failed · 8 not measured

Median response
940 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
2

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
222

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 940 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-06-18, serverInfo.name agent-account-index.

  • Pass
    Lists tools

    tools/list returned 2 tools.

  • Pass
    Current protocol

    Negotiated 2025-06-18. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 940 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 940 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    1 of 1 parameters have a description (100%). The bar is 80%.

  • Fail
    Safety hints

    2 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Fail
    Repo owner matches

    The GitHub repository owner does not match the namespace login.

  • Pass
    Recently updated

    Updated 2026-10-14T22:34:39.659148Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using Agent Account Index

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http agent-account-index https://agent-account-index.vercel.app/mcp

Capabilities

Tools 2

can_an_agent_hold_an_account

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.

Discovered
list_named_non_human_routes

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected940 ms2