Is the Chain App Chainlove MCP server down?

mcp-registry/love.chain.app/chainlove-mcp · v0.1.0

healthy
Last checked 2026-10-26 18:50 UTC · handshake 250ms

As of 2026-10-26 18:50 UTC, the Chain App Chainlove MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 98.8% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
98.8%
checks observed
4,638
outages (90d)
24
tools
5

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

Point your MCP client at this streamable-http endpoint: https://app.chain.love/mcp

Agent-readiness: C (79/100)

C (79/100): 0 error(s), 3 warning(s) across 5 tool(s); ~1,684 tokens of tool definitions.
Scores higher than 16% of 15,767 MCP servers Glimind has audited.
Its tool list costs an agent ~1,684 tokens per session — lighter than 60% of servers.
80 → 79 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints4
Token cost100
Client compatibility70
Protocol100
Reliability75
Stability100

What to fix (4)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: bind_credentials_bag, discover_categories, discover_networks, execute, search

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: execute

Reachable 98.8% of the time over the last 30 days; median recovery 3 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Flove.chain.app%2Fchainlove-mcp/fixes

execute 1 change
{
  "name": "execute",
  "description": "Unified execution entrypoint for registry actions, saved connection management, downstream MCP connection validation, and downstream MCP runtime actions",
  "inputSchema": {
    "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"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Unified Execute"
}
search 1 change
{
  "name": "search",
  "description": "Search Chain.Love registry services. Prefer passing explicit chain/category from discover_networks and discover_categories, but standalone search still works without prior discovery.",
  "inputSchema": {
    "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."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Registry Search"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/love.chain.app/chainlove-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/love.chain.app/chainlove-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Flove.chain.app%2Fchainlove-mcp.svg)](https://glimind.com/server/mcp-registry%2Flove.chain.app%2Fchainlove-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Flove.chain.app%2Fchainlove-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Flove.chain.app%2Fchainlove-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Flove.chain.app%2Fchainlove-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Flove.chain.app%2Fchainlove-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a1a93210aa76a7f0…, first seen 2026-10-17, included at leaf 9788 of 74,836. Version history · verify what your client received.

Tools (5)

Compare: most reliable security servers · most reliable knowledge servers · most reliable devops servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Chain App Chainlove MCP server down right now?

As of 2026-10-26 18:50 UTC, the Chain App Chainlove MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 98.8% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Chain App Chainlove MCP server provide?

Chain App Chainlove MCP server advertises 5 tools, including bind_credentials_bag, discover_categories, discover_networks, execute, search.

How do I install Chain App Chainlove MCP server?

Point your MCP client at this streamable-http endpoint: https://app.chain.love/mcp

Is the Chain App Chainlove MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Chain App Chainlove MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve