mcp-registry/io.github.eamwhite1/agent-trust · v4.1.3
As of 2026-10-23 12:55 UTC, the Eamwhite1 Agent Trust MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments.
Claude Code
claude mcp add --transport http eamwhite1-agent-trust-mcp-server https://xrpl-referee.onrender.com
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"eamwhite1-agent-trust-mcp-server": {
"type": "http",
"url": "https://xrpl-referee.onrender.com"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool definition(s) exceed ~1,200 tokens each (largest: create_escrow_vault, ~1,935).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~2,048 tokens every session. How to fix →
46 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
2 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 →
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 →
Reachable 98.6% of the time over the last 30 days; median recovery 2 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
7 of 46 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 →
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%2Fio.github.eamwhite1%2Fagent-trust/fixes
{
"name": "create_agent_wallet",
"description": "Convenience tool: generate a new XRPL keypair and return the seed.\n\n⚠ NOT RECOMMENDED FOR PRODUCTION. The seed (private key) is returned in plaintext\nand will appear in your conversation transcript and any logs. For production agents,\ncall get_wallet_setup_guide() instead — it documents the secure local approach\n(Wallet.generate() + seed in .env) where the seed never leaves your environment.\n\nUse this tool only for throwaway wallets, local development, or quick demos.\nNEVER paste the returned se",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create Agent Wallet"
}{
"name": "explain_agenttrust_trust_model",
"description": "Returns the AgentTrust trust model: what is guaranteed, where trust remains,\nand when to use proof gates vs AI audit. Read this before designing an escrow flow.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Explain Agenttrust Trust Model"
}{
"name": "get_batch_dvp_payload",
"description": "XLS-56 Atomic NFT DvP — live on XRPL mainnet.\n\nReturns a pre-built Batch transaction (TF_ALL_OR_NOTHING) the buyer signs once\nto atomically accept the seller's NFT transfer and release the escrow payment in a\nsingle ledger close. Both legs succeed or both revert — no settlement gap.\n\nTwo supported modes:\n- AI audit + atomic settlement: referee evaluates work first; PASS verdict gates\n entry to the Batch tx. The AI verdict and atomic settlement work in sequence,\n not as alternatives. Use when t",
"inputSchema": {
"type": "object",
"required": [
"escrow_id"
],
"properties": {
"escrow_id": {
"type": "string",
"description": "The escrow vault ID for an NFT DvP job in PASS_AWAITING_NFT state."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Batch Dvp Payload"
}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.eamwhite1/agent-trust"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.eamwhite1/agent-trust"}) over MCP.
create_escrow_vault ~1,935 tokenshire_and_pay ~1,313 tokenscreate_skill_listing ~673 tokensevaluate_escrow_work ~499 tokenspost_job ~456 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%2Fio.github.eamwhite1%2Fagent-trust?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust?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:63fd174cade67df7…, first seen 2026-10-22, included at leaf 46844 of 52,173. Version history · verify what your client received.
Compare: most reliable security servers · most reliable ml servers · most reliable finance servers · most reliable knowledge servers · most reliable other 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 12:55 UTC, the Eamwhite1 Agent Trust MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Eamwhite1 Agent Trust MCP server advertises 50 tools, including assess_counterparty_and_job, audit, audit_task, award_job, batch_wallet_trust_scores.
Point your MCP client at this streamable-http endpoint: https://xrpl-referee.onrender.com
Glimind scanned all 46 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.