Agent Account Index
Can an AI agent hold an account at a service? Verdict, owner of record, quoted terms clause.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"agent-account-index": {
"url": "https://agent-account-index.vercel.app/mcp"
}
}
}Remote endpoints
https://agent-account-index.vercel.app/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟡can_an_agent_hold_an_account(service)
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).
Input Schema
{
"type": "object",
"properties": {
"service": {
"type": "string",
"description": "Service name, e.g. \"GitHub\", \"Stripe\", \"Supabase\". Case-insensitive, matched on substring."
}
},
"required": [
"service"
]
}🟢list_named_non_human_routes
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.
Input Schema
{
"type": "object",
"properties": {}
}Community
Evidence