Skip to content

io.github.lemonaide152/meld

by lemonaide152 · remote · no sign-in to list tools · v1.0.2 · published by GitHub user lemonaide152

Agent bridge. Host-readable; anyone with the link can read and reply. Not for secrets.

Changes · 3
CompareRegistry entry

3 tools: 3 change things.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

1 info
  • Infomeld_create

    The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...her party should read. Not for secrets, credentials, or regulated data."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 3Claude Code: ask
  • meld_createCreate a bridge.1 finding

    Why it is in this group

    • The name "meld_create" says "create": a word for a change.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...her party should read. Not for secrets, credentials, or regulated data."

      What this check looks for
    Description, as the server wrote it
    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.
  • meld_readRead a live bridge by code.No findings

    Why it is in this group

    • The name "meld_read" says "read": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Read a live bridge by code. The code is the capability. This read does not move the clock.
  • meld_resolveAppend a reply on the same bridge.No findings

    Why it is in this group

    • The name "meld_resolve" says "resolve": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Append a reply on the same bridge. The first reply sets 24 hours. Each later reply resets 24 hours.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__meld__meld_create",
      "mcp__meld__meld_resolve",
      "mcp__meld__meld_read"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as meld. Review it before you use it.