C
Warning
74/100
9 hours ago

AgentTrust

35-tool MCP server for agent-to-agent payments on the XRP Ledger — job marketplace, crypto-condition escrow, AI-verified work delivery, trust scoring, and wallet bootstrap from Coinbase

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

eamwhite1

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
10 flows detected: ANCHAIN_API_KEY, TELEGRAM_BOT_TOKEN, XUMM_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 12 credentials: COINBASE_API_KEY, COINBASE_API_SECRET, ANCHAIN_API_KEY, BITHOMP_API_KEY, REVIEWER_BYPASS_TOKEN, RESEND_API_KEY, TELEGRAM_BOT_TOKEN, TELEGRAM_API_KEY, FULFILLMENT_ENCRYPTION_KEY, XUMM_API_KEY, XUMM_API_SECRET, GEMINI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretCOINBASE_API_KEY
🔐 secretCOINBASE_API_SECRET
🔐 secretANCHAIN_API_KEY
configXRPL_URL
🔐 secretBITHOMP_API_KEY
configBASE_WALLET_ADDRESS
configBASE_RPC_URL
🔐 secretREVIEWER_BYPASS_TOKEN
🔐 secretRESEND_API_KEY
configRESEND_FROM
configSITE_URL
🔐 secretTELEGRAM_BOT_TOKEN
🔐 secretTELEGRAM_API_KEY
configTELEGRAM_CHAT_ID
🔐 secretFULFILLMENT_ENCRYPTION_KEY
configDEFAULT_MAX_SUBMISSIONS
configXRPL_SEED
🔐 secretXUMM_API_KEY
🔐 secretXUMM_API_SECRET
🔐 secretGEMINI_API_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// quality suggestions

Tool annotations

32/35 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/35 tools missing one or more hints — submit_escrow_transaction (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_agent_wallet (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fund_xrpl_wallet_via_coinbase (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

openWorldHint matches behaviour

4 tools claim openWorldHint=false but make outbound HTTP — get_wallet_verification_challenge → dynamic (line 977); rate_wallet → dynamic (line 1252); send_job_message → dynamic (line 1309)

Either flip openWorldHint to true (acknowledging external reach) or refactor the handler to avoid outbound HTTP. If the only network calls are to a known fixed endpoint that you consider part of the tool itself, document that and keep openWorldHint=false; otherwise true is honest.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets stay with their owner

2 secret/sensitive values flow into network calls (GEMINI_API_KEY → dynamic, GEMINI_API_KEY → dynamic) (8 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not logged

5 secret values sent to console.log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/eamwhite1-xrpl-referee-1lruah?variant=verified)](https://m8ven.ai/mcp/eamwhite1-xrpl-referee-1lruah)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 9bb7b6c289652b00a0cb1c39f442637ca5b8e444
code hash: d13c867cd6bfdb54f2d87f731ab88a32b48ab87068c8ddc26115d6128da88a90
verified: 8/19/2026, 9:11:25 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client