Prove end users to agents and apps: login-links, OIDC clients, and API keys over remote MCP
Connect Remote server
claude mcp add --transport http corroborate-me https://corroborateme.com/mcp/ --header "Authorization: Bearer <YOUR_API_KEY>"{
"mcpServers": {
"corroborate-me": {
"url": "https://corroborateme.com/mcp/",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}{
"servers": {
"corroborate-me": {
"type": "http",
"url": "https://corroborateme.com/mcp/",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://corroborateme.com/mcp/Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional API key as Bearer aa_... (mint in the console or via bootstrap). Required to bind a new MCP OAuth client; hosts may then use MCP OAuth instead of pasting the key. |
Details
| Endpoint | https://corroborateme.com/mcp/ (Streamable HTTP) |
| First published | 6 Nov 2026 |
| Last updated | 6 Nov 2026 |
| Registry name | com.corroborateme/corroborate-me |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.