Connect Chain.Love and your agent gets 5 tools, among them bind_credentials_bag, discover_categories, discover_networks. It answers at https://app.chain.love/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Hosted MCP gateway for Web3 infra discovery across 20+ networks via one endpoint.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
bind_credentials_bag | Optionally bind session-scoped downstream credentials immediately after initialize. Safe to call even when no credentials are available. Inputs: analytics, credentials_bag |
discover_categories | For a chosen chain, list its dynamic categories and compact category summaries. Call this after discover_networks and before search when you want deterministic retrieval. Inputs: analytics, chain |
discover_networks | List authoritative chain/network keys available in the current release. Call this first to choose a valid chain before discover_categories or search. Inputs: analytics |
execute | Unified execution entrypoint for registry actions, saved connection management, downstream MCP connection validation, and downstream MCP runtime actions Inputs: analytics, service_id, operation, arguments |
search | Search Chain.Love registry services. Prefer passing explicit chain/category from discover_networks and discover_categories, but standalone search still works without prior discovery. Inputs: analytics, query, chain, category, tags, limit |
Every block below points at https://app.chain.love/mcp. Pick your client and copy.
claude mcp add --transport http chain-love https://app.chain.love/mcp
{
"mcpServers": {
"chain-love": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://app.chain.love/mcp"]
}
}
}{
"mcpServers": {
"chain-love": {
"url": "https://app.chain.love/mcp"
}
}
}{
"servers": {
"chain-love": {
"type": "http",
"url": "https://app.chain.love/mcp"
}
}
}{
"context_servers": {
"chain-love": {
"url": "https://app.chain.love/mcp"
}
}
}{
"mcpServers": {
"chain-love": {
"serverUrl": "https://app.chain.love/mcp"
}
}
}{
"mcpServers": {
"chain-love": {
"url": "https://app.chain.love/mcp"
}
}
}name: Chain.Love
version: 0.0.1
schema: v1
mcpServers:
- name: Chain.Love
type: streamable-http
url: https://app.chain.love/mcp{
"mcpServers": {
"chain-love": {
"httpUrl": "https://app.chain.love/mcp"
}
}
}{
"mcpServers": {
"chain-love": {
"type": "http",
"url": "https://app.chain.love/mcp"
}
}
}{
"mcpServers": {
"chain-love": {
"url": "https://app.chain.love/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapp.chain.love%2Fmcp&type=streamable_http&id=chain-love&name=Chain.Love
It answered our last check on 24 October 2026 in 452 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by chain.love and served from app.chain.love, the vendor's own domain: https://app.chain.love/mcp.
5, as returned by the server's own tools/list on 22 September 2026: bind_credentials_bag, discover_categories, discover_networks, execute, search.
It answered our last check on 24 October 2026 in 452 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://app.chain.love/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: love.chain.app. Endpoint host: app.chain.love. ARD identifier: urn:air:love.chain.app:mcp:chainlove-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.