Awesome MCP Servers by AI Anytime

Directory / Search & discovery

Chain.Love MCP

Discover and compare Web3 infrastructure across supported networks. Endpoint: https://app.chain.love/mcp · Docs

Live  Answered an MCP handshake without credentials and listed 5 tools.

Category
Search & discovery
Transport
http
Source
https://github.com/Chain-Love/chain.love-mcp
Endpoint
https://app.chain.love/mcp
Reports itself as
chain-love-mcp-gateway 0.1.0
Protocol
2025-06-18
Tools
5
Context cost
about 1,516 tokens for the tool definitions (estimated at four characters per token)
Tool definitions last changed
no change seen since first check
Handshake time
67 ms
Repository
2 stars · last push 2026-04-16
Last checked
2026-11-03 10:54:36 UTC
Listed since
2026-10-17

Health and compatibility

Endpoint reachableVerifiedResponded in 67 ms
MCP handshake (initialize)VerifiedCompleted without credentials
Tool discovery (tools/list)Verified5 tools listed
AuthenticationVerifiedNone needed to connect
Protocol versionVerified2025-06-18
TransportVerifiedStreamable HTTP
Capabilities declaredVerifiedresources, tools

Last checked . Verified means the check saw it happen; it says nothing about whether the server is safe.

Recent history

100% of the last 13 daily checks reachable; median response 232 ms. Green answered, violet asked for auth, red did not answer.

Set up in your client

Claude Code

Run this in a terminal:

claude mcp add --transport http chain-love-mcp https://app.chain.love/mcp

Claude Desktop

Open Settings → Connectors → Add custom connector and paste this URL:

https://app.chain.love/mcp

Or bridge it through mcp-remote in claude_desktop_config.json (needs Node.js):

{
  "mcpServers": {
    "chain-love-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.chain.love/mcp"
      ]
    }
  }
}

Cursor

Add to Cursor

Or add it to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "chain-love-mcp": {
      "url": "https://app.chain.love/mcp"
    }
  }
}

VS Code

Add to VS Code

Or add it to .vscode/mcp.json:

{
  "servers": {
    "chain-love-mcp": {
      "type": "http",
      "url": "https://app.chain.love/mcp"
    }
  }
}

Or from a terminal:

code --add-mcp '{"name": "chain-love-mcp", "type": "http", "url": "https://app.chain.love/mcp"}'

Windsurf

Add it to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "chain-love-mcp": {
      "serverUrl": "https://app.chain.love/mcp"
    }
  }
}

Other clients

Most clients accept this shape. The endpoint is:

https://app.chain.love/mcp
{
  "mcpServers": {
    "chain-love-mcp": {
      "type": "http",
      "url": "https://app.chain.love/mcp"
    }
  }
}

If it does not connect

Tools 5

Names, descriptions and input schemas exactly as the server returned them on 2026-11-03. This is the server author's own text. Nothing is run from this page. Raw JSON

bind_credentials_bagOptionally bind session-scoped downstream credentials immediately after initialize. Safe to call even when no …

Optionally bind session-scoped downstream credentials immediately after initialize. Safe to call even when no credentials are available.

ParameterTypeDescription
analyticsobjectoptionalOptional analytics context. It is ignored by tool execution and recorded only for usage analytics.
credentials_bagobjectoptionalOptional session-scoped credentials map. When omitted, the server will attempt to bind credentials from request headers such as x-chainlove-cred-github.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "bind_credentials_bag",
    "arguments": {}
  }
}
discover_categoriesFor a chosen chain, list its dynamic categories and compact category summaries. Call this after …

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.

ParameterTypeDescription
analyticsobjectoptionalOptional analytics context. It is ignored by tool execution and recorded only for usage analytics.
chainstringrequiredCanonical chain key from discover_networks, for example 'filecoin'

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "discover_categories",
    "arguments": {
      "chain": "..."
    }
  }
}
discover_networksList authoritative chain/network keys available in the current release. Call this first to choose a valid …

List authoritative chain/network keys available in the current release. Call this first to choose a valid chain before discover_categories or search.

ParameterTypeDescription
analyticsobjectoptionalOptional analytics context. It is ignored by tool execution and recorded only for usage analytics.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "discover_networks",
    "arguments": {}
  }
}
executeUnified execution entrypoint for registry actions, saved connection management, downstream MCP connection …

Unified execution entrypoint for registry actions, saved connection management, downstream MCP connection validation, and downstream MCP runtime actions

ParameterTypeDescription
analyticsobjectoptionalOptional analytics context. It is ignored by tool execution and recorded only for usage analytics.
service_idstringoptionalRegistry service identifier. Required for service-scoped operations such as get_details, open_actions, and connect_mcp
operationstringoptionalUnified operation name: get_details | open_actions | connect_mcp | list_connections | create_connection | get_connection | update_connection_label | delete_connection | list_mcps | bind_mcp_tokens | list_mcp_tools | call_mcp_tool
argumentsobjectoptionalOperation-specific arguments. Preferred runtime flow uses create_connection or bind_credentials_bag, then connect_mcp, then connection_id for list_mcp_tools and call_mcp_tool

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "execute",
    "arguments": {}
  }
}
searchSearch Chain.Love registry services. Prefer passing explicit chain/category from discover_networks and …

Search Chain.Love registry services. Prefer passing explicit chain/category from discover_networks and discover_categories, but standalone search still works without prior discovery.

ParameterTypeDescription
analyticsobjectoptionalOptional analytics context. It is ignored by tool execution and recorded only for usage analytics.
querystringoptionalFree-form query text
chainstringoptionalTarget chain key. Prefer passing a value returned by discover_networks
categorystringoptionalTop-level category key. Prefer passing a value returned by discover_categories
tagsstring[]optionalList of tags to filter by
limitintegeroptionalPagination limit (max 20)
offsetintegeroptionalPagination offset
filtersobjectoptionalDynamic filter object

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "search",
    "arguments": {}
  }
}

Resources 100

Badge

Maintain this server? Put its live status in your README:

MCP status badge

[![MCP status](https://mcp.aianytime.net/badge/chain-love-mcp.svg)](https://mcp.aianytime.net/s/chain-love-mcp/)

Edit this entry · Report a problem

More in Search & discovery

Checks record what a server answered, not whether it is safe. A listing is not a security audit; read a server's source and permissions before you connect it. Add a server · JSON · llms.txt · llms-full.txt

Browse: Agents, IDEs & developer tools · Search & discovery · Knowledge, memory & context · Media & generation · Security · Finance & markets · Marketing, content & social · Cloud, ops & data · Commerce, travel & logistics · Work & productivity · No account needed · Local servers