tradex (benz16107/tradex) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 5 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

tradex

Enables agents to discover and pay for AI services per call via USDC on Solana, supporting marketplace search, listing details, on-chain reputation, wallet info, and paid calls.

→ benz16107/tradex· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

benz16107

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
5 tools verified — handlers match their declared behaviour
4 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 6 credentials: BUYER_WALLET_SECRET, GEMINI_API_KEY, GOOGLE_API_KEY, MCP_AUTH_TOKEN, MCP_WALLET_SECRET, TREASURY_WALLET_SECRET
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.
configAPP_PORT
🔐 secretBUYER_WALLET_SECRETThe agent brings its own wallet () and points at whichever marketplace it
configFACILITATOR_URL
🔐 secretGEMINI_API_KEY
configGEMINI_MODEL
🔐 secretGOOGLE_API_KEY
🔐 secretMCP_AUTH_TOKENbearer-token gated: send Authorization: Bearer $. Without that, anyone who found
configMCP_MAX_PRICE_USDCruns. Two hard caps sit in front of it — per call (default 0.10) and
configMCP_MAX_SPEND_USDCfor the process (default 1.00) — and it refuses rather than overspending. If
🔐 secretMCP_WALLET_SECRET
configPAYMENT_DECIMALS
configPAYMENT_MINT
configPROVIDER_WALLET
configREPUTATION_PROGRAM_ID
configSOLANA_CLUSTERdevnet npm run setup
configSOLANA_RPC_URL
configTRADEX_URL"": "http://localhost:3777",
🔐 secretTREASURY_WALLET_SECRET
configX402_MODEfund the buyer at [faucet.circle.com](https://faucet.circle.com) and set =hosted. Nothing
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployNEXT_PUBLIC_APP_URL
deployNEXT_PUBLIC_REPUTATION_PROGRAM_ID
deployNEXT_PUBLIC_SOLANA_RPC_URL
// quality suggestions

All four hints declared on every tool

5/5 tools missing one or more hints — search_marketplace (missing: destructiveHint, idempotentHint); get_listing (missing: destructiveHint, idempotentHint); buy (missing: destructiveHint), +2 more. 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.

Tool inputs are validated

4/5 tool handlers declare input schemas (80%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/5 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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 Score](https://m8ven.ai/badge/mcp/benz16107/tradex)](https://m8ven.ai/mcp/benz16107/tradex)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9bbeecff02211350116a45198268e9b3cc9690a0
code hash: 55a4e256b24785677604e286874fc83e849e64cdfaebb8ac69b78e103e72e90e
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