Hosted MCP gateway for Web3 infra discovery across 20+ networks via one endpoint.
https://app.chain.love/mcpHeaders: x-chainlove-cred-github
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"love-chain-app-chainlove-mcp": {
"url": "https://app.chain.love/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.
Optional session-scoped credential example for downstream MCP access. This example uses GitHub: send your raw GitHub token in x-chainlove-cred-github. Other downstream MCP credentials can be passed similarly using x-chainlove-cred-<credential_key>.
Chain.Love MCP is an MCP server for Hosted MCP gateway for Web3 infra discovery across 20+ networks via one endpoint.. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://app.chain.love/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://app.chain.love/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://app.chain.love/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://app.chain.love/mcp.
Chain.Love MCP uses HTTP transport. Endpoint: https://app.chain.love/mcp.
Chain.Love MCP inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Chain.Love MCP does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.