
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 分