# io.github.lemonaide152/meld (remote · meld.mergeinc.workers.dev)

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

- Trust score: 59/100 (low)
- Change this week: +41
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

- remote · `meld.mergeinc.workers.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/lemonaide152-meld/meld.md), [page](https://verifymcp.io/servers/lemonaide152-meld/meld)

## Channel facts

- Endpoint: `https://meld.mergeinc.workers.dev`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-01.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 391 tokens (~130/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 4 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the io.github.lemonaide152/meld MCP server?

io.github.lemonaide152/meld is a hosted endpoint at https://meld.mergeinc.workers.dev/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http lemonaide152-meld 'https://meld.mergeinc.workers.dev/'
```

### Cursor

```json
{
  "mcpServers": {
    "lemonaide152-meld": {
      "url": "https://meld.mergeinc.workers.dev/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lemonaide152-meld": {
      "type": "http",
      "url": "https://meld.mergeinc.workers.dev/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lemonaide152-meld]
url = "https://meld.mergeinc.workers.dev/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lemonaide152-meld": {
      "type": "remote",
      "url": "https://meld.mergeinc.workers.dev/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lemonaide152-meld --url 'https://meld.mergeinc.workers.dev/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lemonaide152-meld:
    url: "https://meld.mergeinc.workers.dev/"
```

### Netclaw

```json
{
  "McpServers": {
    "lemonaide152-meld": {
      "Transport": "http",
      "Url": "https://meld.mergeinc.workers.dev/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lemonaide152-meld -t streamable-http -u 'https://meld.mergeinc.workers.dev/'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-01 (score 59, 0)

- [security regression] Stability: 0.10 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “meld_create” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 98 → 130
- [functional regression] “meld_create” added a required parameter “ttl”, so existing callers break
- [functional] Schema quality: good → excellent
- [cosmetic] “meld_create” reworded the description of “context”

### 2026-09-30 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 58, +40)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100

### 2026-09-25 (score 18, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 18)

First indexed and scored.

## MCP tools (3)

### `meld_create` (~174 tokens)

Create a timed bridge. Returns a capability URL (the shared bearer) for the other party. You must set ttl to exactly one of 3m, 1hr, or 1d. There is no default lifetime. Pilot bridges are free. The host can read the exchange while it is live; anyone with the link can too. Not for secrets. Dissolves when that TTL ends.

Input parameters:

- `context` (string, required): Working context the other party should read. Not for secrets, credentials, or regulated data.
- `pin` (string): Optional PIN the other party must supply to answer.
- `ttl` (string, required): Required bridge time. 3m = 3 minutes, 1hr = 1 hour, 1d = 1 day. The server enforces this TTL. There is no default.

### `meld_resolve` (~81 tokens)

Resolve a meld you received a link for. Submit your context/answer. Returns the other party's context. The meld dissolves shortly after.

Input parameters:

- `code` (string, required): The meld code from the link (the part after /m/).
- `context` (string, required): Your answer/context.
- `pin` (string): PIN if the meld has one.

### `meld_read` (~60 tokens)

Owner: read the resolved result of your meld. The owner token rotates on every read — use the newest one.

Input parameters:

- `code` (string, required): The meld code.
- `owner_token` (string, required): Your owner token (from meld_create or the previous read).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lemonaide152-meld/meld#diagnostics

## Score history

- 2026-10-01: 59
- 2026-09-30: 59
- 2026-09-29: 58
- 2026-09-28: 58
- 2026-09-27: 58
- 2026-09-26: 18
- 2026-09-25: 18
- 2026-09-24: 18
- 2026-09-23: 18

## Common questions

### What is the io.github.lemonaide152/meld MCP server?

io.github.lemonaide152/meld is an MCP server listed in the public MCP registry as io.github.lemonaide152/meld. Ephemeral context bridge: one link carries context to another agent, returns one answer, dissolves. This page covers its hosted endpoint (https://meld.mergeinc.workers.dev).

### Is the io.github.lemonaide152/meld MCP server safe to use?

io.github.lemonaide152/meld scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.lemonaide152/meld MCP server expose?

io.github.lemonaide152/meld exposes 3 tools: meld_create, meld_resolve, meld_read. Their descriptions and schemas cost roughly 315 tokens of context every time the server is loaded.

### Does the io.github.lemonaide152/meld MCP server require authentication?

No. We connected to io.github.lemonaide152/meld without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.lemonaide152/meld MCP server still maintained?

io.github.lemonaide152/meld is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://meld.mergeinc.workers.dev/
- Repository: https://github.com/lemonaide152/meld
- Changelog RSS feed: https://verifymcp.io/servers/lemonaide152-meld/meld.xml
- Changelog JSON feed: https://verifymcp.io/servers/lemonaide152-meld/meld.json
- HTML version of this page: https://verifymcp.io/servers/lemonaide152-meld/meld