Is the Lemonaide152 Meld MCP server down?

mcp-registry/io.github.lemonaide152/meld · v1.0.0

healthy
Last checked 2026-10-21 13:37 UTC · handshake 1.6s

As of 2026-10-21 13:37 UTC, the Lemonaide152 Meld MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.7%
checks observed
3,545
outages (90d)
1
tools
3

Ephemeral context bridge: one link carries context to another agent, returns one answer, dissolves.

Install Lemonaide152 Meld MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http lemonaide152-meld-mcp-server https://meld.mergeinc.workers.dev

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "lemonaide152-meld-mcp-server": {
      "type": "http",
      "url": "https://meld.mergeinc.workers.dev"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (74/100)

C (74/100): 0 error(s), 4 warning(s) across 3 tool(s); ~460 tokens of tool definitions.
Scores higher than 9% of 15,461 MCP servers Glimind has audited.
Its tool list costs an agent ~460 tokens per session — lighter than 95% of servers.
74 → 74 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol40
Reliability85
Stability68

What to fix (6)

3 of 3 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: meld_create, meld_read, meld_resolve

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: meld_create

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Handshake + tools/list takes ~2,073 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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 →

In the last 30 days: 0 tool(s) removed and 8 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 3 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%2Fio.github.lemonaide152%2Fmeld/fixes

meld_create 1 change
{
  "name": "meld_create",
  "description": "Create a bridge. Send one note in context. Returns one capability URL. Send that URL privately. Creation opens 36 hours. The first reply sets 24 hours. Each later reply resets 24 hours. Do not send a ttl. Pilot creates are free. The host can read the bridge while it is live. Not for secrets.",
  "inputSchema": {
    "type": "object",
    "required": [
      "context"
    ],
    "properties": {
      "for": {
        "type": "string",
        "description": "Optional, for older clients. Defaults to context."
      },
      "pin": {
        "type": "string",
        "description": "Optional PIN the other party must supply to answer."
      },
      "learn": {
        "type": "boolean",
        "description": "JSON boolean true opts into the pilot reply. Strings and the integer 1 do not."
      },
      "context": {
        "type": "string",
        "description": "Working context the other party should read. Not for secrets, credentials, or regulated data."
      },
      "not_for": {
        "type": "string",
        "description": "Optional, for older clients. Defaults to context."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
meld_read 1 change
{
  "name": "meld_read",
  "description": "Read a live bridge by code. The code is the capability. This read does not move the clock.",
  "inputSchema": {
    "type": "object",
    "required": [
      "code"
    ],
    "properties": {
      "code": {
        "type": "string",
        "description": "The meld code from the capability URL."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
meld_resolve 1 change
{
  "name": "meld_resolve",
  "description": "Append a reply on the same bridge. The first reply sets 24 hours. Each later reply resets 24 hours.",
  "inputSchema": {
    "type": "object",
    "required": [
      "code",
      "context"
    ],
    "properties": {
      "pin": {
        "type": "string",
        "description": "PIN if the meld has one."
      },
      "code": {
        "type": "string",
        "description": "The meld code from the link (the part after /m/)."
      },
      "context": {
        "type": "string",
        "description": "Your answer/context."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/io.github.lemonaide152/meld"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lemonaide152/meld"}) 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%2Fio.github.lemonaide152%2Fmeld.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lemonaide152%2Fmeld?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lemonaide152%2Fmeld?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lemonaide152%2Fmeld.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lemonaide152%2Fmeld.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lemonaide152%2Fmeld?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:ae80eca5bad764a2…, first seen 2026-10-17, included at leaf 16291 of 39,812. Version history · verify what your client received.

Tools (3)

Compare: most reliable communication 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 Lemonaide152 Meld MCP server down right now?

As of 2026-10-21 13:37 UTC, the Lemonaide152 Meld MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Lemonaide152 Meld MCP server provide?

Lemonaide152 Meld MCP server advertises 3 tools, including meld_create, meld_read, meld_resolve.

How do I install Lemonaide152 Meld MCP server?

Point your MCP client at this streamable-http endpoint: https://meld.mergeinc.workers.dev

Is the Lemonaide152 Meld MCP server safe to connect to an AI agent?

Glimind scanned all 3 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 Lemonaide152 Meld 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