Home / MCP registry index / io.github.imnotamob/solmachina-x402
io.github.imnotamob/solmachina-x402
io.github.imnotamob/solmachina-x402 in the official MCP registry.
Endpoint https://api.solmachina.com/mcp. Source: github.com/imnotamob/solmachina-x402-mcp.
The registry describes it as: Solana & Base DeFi intelligence for AI agents over x402: decisions, risk, signed receipts.
We read its 25 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http solmachina-x402 https://api.solmachina.com/mcp{
"mcpServers": {
"solmachina-x402": {
"url": "https://api.solmachina.com/mcp"
}
}
}code --add-mcp '{"name":"solmachina-x402","type":"http","url":"https://api.solmachina.com/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.
Tools it advertises
solmachina_catalog solmachina_sample solmachina_how_to_pay solmachina_verify_receipt solmachina_status solmachina_smri solmachina_simulate solmachina_decision solmachina_token_holders solmachina_slippage_map solmachina_tipfloor solmachina_epoch solmachina_kamino_markets solmachina_sgp_checkpoint solmachina_token_risk solmachina_wallet_scan solmachina_token_intel solmachina_batch_token_risk solmachina_priority_fee solmachina_dex_quote solmachina_trending_tokens solmachina_new_pairs solmachina_nft_collection solmachina_tx_inspect solmachina_pretrade
Run this server? Show the check in your README
The badge reflects the latest weekly read:
[](https://lazaretto.dev/mcp-registry/io-github-imnotamob-solmachina-x402)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |