mcp-registry/com.cocoeatsai/launch-lab-xrp · v1.0.0
As of 2026-10-23 18:01 UTC, the Cocoeatsai Launch Lab Xrp MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 1 minutes.
XRP research, paper arena and free XRPL transaction explanations / x402 diagnostics. No signing.
Claude Code
claude mcp add --transport http cocoeatsai-launch-lab-xrp-mcp-server https://cocoeatsai.com/area4/agent/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"cocoeatsai-launch-lab-xrp-mcp-server": {
"type": "http",
"url": "https://cocoeatsai.com/area4/agent/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
6 of 6 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 →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.cocoeatsai%2Flaunch-lab-xrp/fixes
{
"name": "xrpl_explain_tx",
"description": "FREE safety check: explain an XRPL transaction in plain English before signing it (JSON or hex blob) and flag risks such as wallet-drainer patterns, fake RLUSD issuers, missing destination tags and partial payments. Returns a verdict: looks_normal, review or do_not_sign.",
"inputSchema": {
"type": "object",
"required": [
"tx"
],
"properties": {
"tx": {
"description": "Transaction JSON object or hex blob",
"type": "string"
},
"signer": {
"type": "string",
"description": "Optional: the account you expect to be signing"
},
"max_xrp": {
"type": "number",
"description": "Optional spending cap in XRP"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "xrpl_wallet_report_preview",
"description": "Free wallet safety preview: heuristic score and up to three issues; full report is paid. Public ledger reads only, no wallet signing.",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}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/com.cocoeatsai/launch-lab-xrp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.cocoeatsai/launch-lab-xrp"}) over MCP.
xrpl_explain_tx ~167 tokensxrp_brief_sample ~117 tokensx402_doctor ~115 tokensxrpl_wallet_report_preview ~80 tokensxrp_paid_endpoints ~62 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fcom.cocoeatsai%2Flaunch-lab-xrp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.cocoeatsai%2Flaunch-lab-xrp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cocoeatsai%2Flaunch-lab-xrp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cocoeatsai%2Flaunch-lab-xrp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.cocoeatsai%2Flaunch-lab-xrp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1449ae631de34a20…, first seen 2026-10-17, included at leaf 4020 of 53,585. Version history · verify what your client received.
Compare: most reliable web servers · most reliable finance servers · most reliable security servers
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.
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"
}
}
}
As of 2026-10-23 18:01 UTC, the Cocoeatsai Launch Lab Xrp MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 1 minutes.
Cocoeatsai Launch Lab Xrp MCP server advertises 6 tools, including x402_doctor, xrp_brief_sample, xrp_paid_endpoints, xrp_track_record, xrpl_explain_tx.
Point your MCP client at this streamable-http endpoint: https://cocoeatsai.com/area4/agent/mcp
Glimind scanned all 6 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.
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.