Chain.Love MCP

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Hosted MCP gateway for Web3 infra discovery across 20+ networks via one endpoint.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Chain.Love MCP": {
      "url": "https://app.chain.love/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• 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.

  Parameters:

  • analytics — object — Optional analytics context. It is ignored by tool execution and recorded only for usage analytics.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Parameters:

  • chain (required) — string — Canonical chain key from discover_networks, for example 'filecoin'
  • analytics — object — Optional analytics context. It is ignored by tool execution and recorded only for usage analytics.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Parameters:

  • tags — array — List of tags to filter by
  • chain — string — Target chain key. Prefer passing a value returned by discover_networks
  • limit — integer — Pagination limit (max 20)
  • query — string — Free-form query text
  • offset — integer — Pagination offset
  • filters — object — Dynamic filter object
  • category — string — Top-level category key. Prefer passing a value returned by discover_categories
  • analytics — object — Optional analytics context. It is ignored by tool execution and recorded only for usage analytics.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• bind_credentials_bag

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

  Parameters:

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

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• execute

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

  Parameters:

  • analytics — object — Optional analytics context. It is ignored by tool execution and recorded only for usage analytics.
  • arguments — object — Operation-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
  • operation — string — Unified 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
  • service_id — string — Registry service identifier. Required for service-scoped operations such as get_details, open_actions, and connect_mcp

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.