_ registry / mcp streamable-http · checked 1h ago

chain-love-mcp-gateway

https://app.chain.love

Registry code: 141932ff8a3016c3

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://app.chain.love/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is chain-love-mcp-gateway live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is chain-love-mcp-gateway free to use?
Yes — the hub reached it with no key and no payment.
What tools does chain-love-mcp-gateway have?
5 tools: discover_networks, discover_categories, bind_credentials_bag, execute, search.
Is chain-love-mcp-gateway safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.4%

90 days 99.1%· all time 99.1%

latency
495ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 317 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
developer tools apis & integration
used for
  • discover web3 infrastructure services by chain
  • search blockchain infra registry
  • execute registry actions through a gateway
takes → gives
text, data → data
tools
3 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search reads open 17h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of tags to filter by"
    },
    "chain": {
      "type": "string",
      "description": "Target chain key. Prefer passing a value returned by discover_networks"
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Pagination limit (max 20)"
    },
    "query": {
      "type": "string",
      "description": "Free-form query text"
    },
    "offset": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Pagination offset"
    },
    "filters": {
      "type": "object",
      "description": "Dynamic filter object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "category": {
      "type": "string",
      "description": "Top-level category key. Prefer passing a value returned by discover_categories"
    },
    "analytics": {
      "type": "object",
      "properties": {
        "source": {
          "type": "string",
          "description": "Optional analytics source identifier."
        },
        "user_query": {
          "type": "string",
          "description": "Original user query or prompt that led to this tool call, if available."
        },
        "interaction_id": {
          "type": "string",
          "description": "Optional interaction/message identifier."
        },
        "conversation_id": {
          "type": "string",
          "description": "Optional conversation identifier."
        }
      },
      "description": "Optional analytics context. It is ignored by tool execution and recorded only for usage analytics."
    }
  }
}
    arguments 67 lines
  • discover_networks reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "analytics": {
      "type": "object",
      "properties": {
        "source": {
          "type": "string",
          "description": "Optional analytics source identifier."
        },
        "user_query": {
          "type": "string",
          "description": "Original user query or prompt that led to this tool call, if available."
        },
        "interaction_id": {
          "type": "string",
          "description": "Optional interaction/message identifier."
        },
        "conversation_id": {
          "type": "string",
          "description": "Optional conversation identifier."
        }
      },
      "description": "Optional analytics context. It is ignored by tool execution and recorded only for usage analytics."
    }
  }
}
    arguments 28 lines
  • discover_categories reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "chain"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "minLength": 1,
      "description": "Canonical chain key from discover_networks, for example 'filecoin'"
    },
    "analytics": {
      "type": "object",
      "properties": {
        "source": {
          "type": "string",
          "description": "Optional analytics source identifier."
        },
        "user_query": {
          "type": "string",
          "description": "Original user query or prompt that led to this tool call, if available."
        },
        "interaction_id": {
          "type": "string",
          "description": "Optional interaction/message identifier."
        },
        "conversation_id": {
          "type": "string",
          "description": "Optional conversation identifier."
        }
      },
      "description": "Optional analytics context. It is ignored by tool execution and recorded only for usage analytics."
    }
  }
}
    arguments 36 lines
  • bind_credentials_bag changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "analytics": {
      "type": "object",
      "properties": {
        "source": {
          "type": "string",
          "description": "Optional analytics source identifier."
        },
        "user_query": {
          "type": "string",
          "description": "Original user query or prompt that led to this tool call, if available."
        },
        "interaction_id": {
          "type": "string",
          "description": "Optional interaction/message identifier."
        },
        "conversation_id": {
          "type": "string",
          "description": "Optional conversation identifier."
        }
      },
      "description": "Optional analytics context. It is ignored by tool execution and recorded only for usage analytics."
    },
    "credentials_bag": {
      "type": "object",
      "description": "Optional session-scoped credentials map. When omitted, the server will attempt to bind credentials from request headers such as x-chainlove-cred-github.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": "string"
      }
    }
  }
}
    arguments 38 lines
  • execute changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "analytics": {
      "type": "object",
      "properties": {
        "source": {
          "type": "string",
          "description": "Optional analytics source identifier."
        },
        "user_query": {
          "type": "string",
          "description": "Original user query or prompt that led to this tool call, if available."
        },
        "interaction_id": {
          "type": "string",
          "description": "Optional interaction/message identifier."
        },
        "conversation_id": {
          "type": "string",
          "description": "Optional conversation identifier."
        }
      },
      "description": "Optional analytics context. It is ignored by tool execution and recorded only for usage analytics."
    },
    "arguments": {
      "type": "object",
      "description": "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",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "operation": {
      "type": "string",
      "description": "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": {
      "type": "string",
      "minLength": 1,
      "description": "Registry service identifier. Required for service-scoped operations such as get_details, open_actions, and connect_mcp"
    }
  }
}
    arguments 45 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 141932ff8a3016c3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/141932ff8a3016c3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/141932ff8a3016c3/badge.svg)](https://brick.blue/agent/141932ff8a3016c3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on chain.love 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.