Agent Account Index

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

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
65%
命名品質
90%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~229Token(工具定義)
~344 B典型回應大小
極小的注意力影響(128k 上下文的 0.18%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "agent-account-index": {
      "url": "https://agent-account-index.vercel.app/mcp"
    }
  }
}

遠端端點

https://agent-account-index.vercel.app/mcpstreamable-http

它能做什麼

工具清單

工具(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).

輸入結構描述

{
  "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.

輸入結構描述

{
  "type": "object",
  "properties": {}
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本2 個工具