Developer · Remote MCP server
Chain.Love MCP
Hosted MCP gateway for Web3 infra discovery across 20+ networks via one endpoint.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
love.chain.app/chainlove-mcp- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-04-15
- Updated
- 2026-04-15
- Publisher
- love.chain.app
- Namespace
- Namespace verified by the MCP Registry via the domain app.chain.love or a parent domain of it · how
- Website
- chain.love/mcp-gateway
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.chain.love/mcp | x-chainlove-cred-github (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- chain-love-mcp-gateway 0.1.0 · protocol 2025-06-18
- Tools discovered
- 5:
discover_networks,discover_categories,search,bind_credentials_bag,execute - Checked on
- 2026-10-05
How to connect Chain.Love MCP
Chain.Love MCP is a remote MCP server: there is nothing to install. Its endpoint is https://app.chain.love/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: x-chainlove-cred-github (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Cesium MCP DevCesiumJS API docs, code generation and development tools for IDE AI assistants. | Local · stdio |
| CGIS Code GraphCode graph for AI agents: impact analysis and call tracing for Python and TypeScript. | Local · stdio |
| CgraphyCode knowledge graph over MCP: token-budgeted context for AI coding agents. | Local · stdio |
| Chain SignerSecurity suite for AI agents: flag drains, permit-phishing & risky actions before signing. | Local · stdio |
| ChainWeaverExpose deterministic ChainWeaver flows as MCP tools without LLM calls between steps. | Local · stdio |
| Chainweb APIChainweb HTTP API: local sim, pre-signed send, poll, table reads, SPV proofs, module deploys. | Local · stdio |
| ChangeflowAI-powered web monitoring. Track any website, get structured change intelligence. | Local · stdio |
| ChangegamerAgent-first resource directory for AI agents: protocols, security, RAG, memory, evals, and more. | Remote · HTTPLive check: ✓ handshake |