
CorroborateMe
com.corroborateme由 corroborateme.com 發布官方發布者v0.2.2更新於 Nov 7, 2026
Prove end users to agents and apps: login-links, OIDC clients, and API keys over remote MCP
概覽
遠端 MCP 伺服器,用來向代理與應用程式證明終端使用者身分:登入連結、OIDC 用戶端、API 金鑰、整合密鑰與預算計費。
- 可以做什麼
- 引導建立公司帳戶,並簽發或管理 API 金鑰
- 建立一次性人工登入連結、查詢其狀態並重試簽章通知 webhook
- 註冊、撤銷 OIDC 依賴方用戶端,並允許回呼 URL 前綴
- 儲存並列出加密的整合密鑰(僅顯示前綴)
- 查詢剩餘配額,並產生 Stripe 結帳、預付機器付款或客戶入口網站連結
- 適用情境
- 當代理或應用程式需要確認終端使用者是誰時使用,例如簽發登入連結並等待使用者完成;也適合需要在一套託管服務中管理公司 API 金鑰、OIDC 用戶端註冊與整合密鑰的情境。
- 執行需求
- 遠端 Streamable HTTP 端點,不需本機套件。必須驗證:以 Authorization Bearer 標頭送出 API 金鑰,或使用 MCP OAuth(綁定新用戶端仍需 API 金鑰)。金鑰可於訂閱後從主控台取得,或透過代理引導加預付機器付款取得。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 CorroborateMe,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/com.corroborateme%2Fcorroborate-me/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"corroborateme": {
"type": "http",
"url": "https://corroborateme.com/mcp/"
}
}
}README
CorroborateMe
Prove end users to agents and apps.
[Remote MCP] [Transport] [Auth] [License: MIT] [Listed on mcpservers.org]
CorroborateMe gives agents and apps company API keys and human login-links with multi-channel notify so they can prove who the end user is - plus OIDC client registration, integration secrets, and budget-aware billing. REST is first-class; MCP is optional.
Live endpoint: https://corroborateme.com/mcp
This repository is the public catalog and schema stub for directory crawlers. It is not the hosted server. Point MCP clients at the live URL above with a CorroborateMe API key (
aa_...) or MCP OAuth (PRM at /.well-known/oauth-protected-resource). Binding a new OAuth client requires thataa_...key first (or a console member session). Running the TypeScript in this repo does not authenticate users or store secrets.
Agent guide: see AGENTS.md for discovery URLs, auth, and MCP connect snippets.
Get an API key
Zero-human (agents)
POST https://corroborateme.com/api/agents/bootstrapwith optional{ "company_name": "...", "contact_email": "[email protected]" }-> bootstrap token (no outbound mail).POST https://corroborateme.com/api/billing/machine-paywithAuthorization: Bearer <bootstrapToken>and optional{ "sku": "pro_prepaid_30d" }.- Settle Stripe MPP when enabled (see live
GET /api/configfor amounts) -> response includessecret(aa_...) when unlock succeeds.
See llms.txt and llms-full.txt. Legal: Terms · Privacy.
Human path
- Open corroborateme.com and create an account.
- Subscribe on Pricing, then mint an API key in the console. Secrets start with
aa_. - Use the company key for REST and MCP.
Never commit a real key. Use the aa_... placeholder in configs.
Connect a client
Transport is Streamable HTTP. Authenticate with either:
Authorization: Bearer aa_...(API key from console or bootstrap + machine-pay), or- MCP OAuth - get an
aa_...key first (bootstrap + machine-pay, or console). Host discovers PRM at /.well-known/oauth-protected-resource, registers via DCR, then binds the client onPOST /api/oidc/startwithAuthorization: Bearer aa_...(company from the key) or a console member session pluscompany_idbefore browser consent. A barecompany_idis rejected (401).
Cursor
Install via Cursor Marketplace (plugin)
This repo includes a Cursor plugin manifest and root mcp.json for one-click install from the Cursor Marketplace.
- Install the CorroborateMe plugin from the marketplace (or clone this repo for local plugin testing).
- Open Cursor Settings -> Customize -> CorroborateMe and set CorroborateMe API key (
aa_...from bootstrap + machine-pay or the console). - Reload the window. MCP tools should appear under the CorroborateMe server.
The plugin points at https://corroborateme.com/mcp with Authorization: Bearer ${CORROBORATE_ME_API_KEY}. Never commit a real key.
Submit the public repo at cursor.com/marketplace/publish when ready.
Manual MCP config
User or project MCP config:
Claude Desktop / Claude Code
Generic remote MCP
Discovery manifests on the product host:
Tools
Schemas in src/server.ts match the hosted server.
Typical agent loop
- Bootstrap with email OTP (
agent_bootstrapor REST/api/agents/bootstrap), then unlock prepaid Pro (billing_machine_pay) when needed. - Mint a key with
keys_createif you need a durableaa_...secret. - Allowlist callback prefixes (
webhook_allowlist_add), thencreate_login_linkfor human proof. - Poll with
get_login_status(or wait for webhook / redirect / postMessage). - Use REST or MCP for keys, OIDC clients, and integrations as needed.
Login-link password completion (REST only)
There is no MCP tool for password flows. The IdP login page can complete a session with email + password for registered users. OpenAPI documents:
POST /api/login-links/{id}/password-login— registered-user password sign-in (see Swagger for the request body)POST /api/login-links/{id}/set-password— set password with a ticket, then complete the session (see Swagger)
Company API keys (aa_...) and MCP tool names are unchanged.
Prefer live docs and llms-full.txt for recipes that may change.
OIDC apps: hosted Change password
Confidential consumer apps that sign users in through CorroborateMe should open CorroborateMe's hosted password page from a settings Change password button. Passwords never pass through your app.
- Register the client with exact
password_return_uris(separate from authorize redirects). - Your backend calls
POST https://corroborateme.com/api/account/password/startwithAuthorization: Bearer <user access token>and body{ "client_id", "client_secret", "return_uri", "state", "display" }. Keepclient_secreton the server only. - Open
continuation_urlin a popup or top-level redirect on the CorroborateMe origin (no iframe). - On return (
type=corroborateme.password_management), clear your local session and start a fresh login whenreauth_requiredis true.
Revocation after success: CorroborateMe Continue-as cookies and Better Auth bridge sessions for that user are invalidated, and that user's OAuth grant rows are stamped revoked. Offline-validated access JWTs may still work until expiry; your app must clear your own session. OpenAPI: see Account password in openapi.json (Worker 0.2.2); Swagger for interactive reference.
Auth and errors
- 401 - missing or invalid Authorization (API key
aa_...or MCP OAuth access token) - 402 / 429 - plan or quota; follow machine-readable actions from the live API
- Pricing amounts: read live
GET /api/config- do not hardcode dollars as eternal truth (at time of writing: Pro $5.99/mo, agent prepaid Pro $5.99 per 30 days)
Product docs
- App: corroborateme.com
- Docs: corroborateme.com/docs
- OpenAPI: corroborateme.com/openapi.json
- Swagger: corroborateme.com/swagger
The CorroborateMe product (Worker, billing, IdP) is closed source. This catalog is MIT-licensed so directories can list tools and install snippets.
Directory listing
Registry name: com.corroborateme/corroborate-me (domain namespace via DNS auth on corroborateme.com). Older versions were published as com.cnrcode/corroborateme.
The registry remote is https://corroborateme.com/mcp/. The Worker serves that path as the same MCP endpoint as https://corroborateme.com/mcp (no redirect). Client install snippets in this repo stay on the no-slash URL. server.json cannot use the no-slash URL: deprecated com.cnrcode/corroborateme still claims it, and registry entries cannot be deleted.
-
Ensure the TXT record
v=MCPv1; k=ed25519; p=<public key>is on thecorroborateme.comapex. -
Set GitHub repo secret
MCP_REGISTRY_KEY_CORROBORATEME(Ed25519 private key hex; never commit it or write it to a file). -
Push a version tag so GitHub Actions publishes
server.jsonto the official MCP Registry:
Directories that ingest the official registry (PulseMCP, MCPCentral, MCPFind, Glama connectors) pick the entry up from there. Other directories (Glama server listing, Smithery, mcpservers.org, mcp.directory, MCP Market, McpMux) are submitted by maintainers only. See docs/directory-listings.md.
Stdio stub (directory introspection)
This repo includes a stdio catalog stub (src/main.ts) so directories can build a container, start the process, and introspect the 14 tool definitions. It does not implement auth or billing - clients still connect to the hosted endpoint above.
Local verify:
License
MIT - catalog, documentation, and schema stub only.
來源:README.md,提交 f6c501d
工具
0版本歷史
2- v0.2.2最新Nov 7, 2026
- v0.2.1Nov 3, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分