io.github.lemonaide152/meld
REMOTE · MELD.MERGEINC.WORKERS.DEV · SCANNED OCT 1
Ephemeral context bridge: one link carries context to another agent, returns one answer, dissolves.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 391 tokens (~130/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 4 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
remote · meld.mergeinc.workers.dev
claude mcp add --transport http lemonaide152-meld 'https://meld.mergeinc.workers.dev/'
{
"mcpServers": {
"lemonaide152-meld": {
"url": "https://meld.mergeinc.workers.dev/"
}
}
} {
"servers": {
"lemonaide152-meld": {
"type": "http",
"url": "https://meld.mergeinc.workers.dev/"
}
}
} [mcp_servers.lemonaide152-meld] url = "https://meld.mergeinc.workers.dev/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lemonaide152-meld": {
"type": "remote",
"url": "https://meld.mergeinc.workers.dev/",
"enabled": true
}
}
} openclaw mcp add lemonaide152-meld --url 'https://meld.mergeinc.workers.dev/' --transport streamable-http
mcp_servers:
lemonaide152-meld:
url: "https://meld.mergeinc.workers.dev/" {
"McpServers": {
"lemonaide152-meld": {
"Transport": "http",
"Url": "https://meld.mergeinc.workers.dev/"
}
}
} assistant mcp add lemonaide152-meld -t streamable-http -u 'https://meld.mergeinc.workers.dev/'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 0
- Stability: 0.10 → fail ▼ security
- 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 security
- Schema quality: 98 → 130 ▼ functional
- “meld_create” added a required parameter “ttl”, so existing callers break ▼ functional
- Schema quality: good → excellent functional
- “meld_create” reworded the description of “context” cosmetic
- 30 Sept 26 +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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +40
- Injection markers: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 1 Oct 2026 · Probed https://meld.mergeinc.workers.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mergeinc.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6dea6737a6449747f6e9d58fb0336b920e6 |
| SANs: *.mergeinc.workers.dev, mergeinc.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of meld.mergeinc.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'unsafe-inline'; style-src 'unsafe-inline'; img-src 'self' data:; connect-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meld.mergeinc.workers.dev | Verified | 200 | |
| http (plaintext) | http://meld.mergeinc.workers.dev | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
meld_create ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | yes | Required bridge time. 3m = 3 minutes, 1hr = 1 hour, 1d = 1 day. The server enforces this TTL. There is no default. |
No output schema declared.
No examples provided.
meld_read ~60
Owner: read the resolved result of your meld. The owner token rotates on every read — use the newest one.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The meld code. |
| owner_token | string | yes | Your owner token (from meld_create or the previous read). |
No output schema declared.
No examples provided.
meld_resolve ~81
Resolve a meld you received a link for. Submit your context/answer. Returns the other party's context. The meld dissolves shortly after.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The meld code from the link (the part after /m/). |
| context | string | yes | Your answer/context. |
| pin | string | – | PIN if the meld has one. |
No output schema declared.
No examples provided.
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.