Server data from the Official MCP Registry
Pay-per-call x402 tools: crypto market pulse, wallet reputation, token check, endpoint search.
Pay-per-call x402 tools: crypto market pulse, wallet reputation, token check, endpoint search.
This MCP server properly handles private key material (never logging or transmitting except as signed payment headers) and implements good input validation for user-supplied arguments before making network calls. File-path reads are appropriately scoped to the home directory with sensitive-location filtering. The primary security concern is that document-parsing tools upload file contents to an external API (api.suverse.io), which is acceptable but documented. Permissions align well with the server's purpose as a pay-per-call API gateway. Supply chain analysis found 8 known vulnerabilities in dependencies (2 critical, 5 high severity). Package verification found 1 issue.
7 files analyzed · 13 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: SUVERSE_API_BASE
Environment variable: SUVERSE_MAX_PAYMENT_USDC
Environment variable: SUVERSE_BASE_RPC_URL
Environment variable: SUVERSE_ALLOW_PATHS_OUTSIDE_HOME
Environment variable: SUVERSE_IDEMPOTENCY_TTL_MS
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-sudzikcoin-mcp-server": {
"env": {
"SUVERSE_API_BASE": "your-suverse-api-base-here",
"SUVERSE_BASE_RPC_URL": "your-suverse-base-rpc-url-here",
"SUVERSE_BASE_PRIVATE_KEY": "your-suverse-base-private-key-here",
"SUVERSE_MAX_PAYMENT_USDC": "your-suverse-max-payment-usdc-here",
"SUVERSE_IDEMPOTENCY_TTL_MS": "your-suverse-idempotency-ttl-ms-here",
"SUVERSE_ALLOW_PATHS_OUTSIDE_HOME": "your-suverse-allow-paths-outside-home-here"
},
"args": [
"-y",
"@suverselabs/mcp-server"
],
"command": "npx"
}
}
}From the project's GitHub README.
An MCP server that gives Claude Desktop (or any MCP client) 15 tools for SuVerse's pay-per-call US-government and freight APIs. Calls are paid automatically, per request, in USDC on Base via the x402 protocol — you fund a wallet once and Claude pays as it works. Your private key never leaves your machine.
✅ Published on npm: https://www.npmjs.com/package/@suverselabs/mcp-server
Install via npx (no local build needed):
npx -y @suverselabs/mcp-server
Add to claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"suverse": {
"command": "npx",
"args": ["-y", "@suverselabs/mcp-server"],
"env": {
"SUVERSE_BASE_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY_HERE"
}
}
}
}
The private key controls a Base wallet that pays for tool calls in USDC. Fund it with ~$5-10 USDC on Base. You don't need ETH for gas — Base settlements are gas-sponsored. Check your balance anytime with the free suverse_balance tool.
Restart Claude Desktop. The 15 SuVerse tools will appear in Claude's tool list.
SuVerse is an x402 gateway over 128 US-government data services (SEC, NPS, FBI, CMS, …) plus a freight document/routing suite. Each call costs a few tenths of a cent up to $0.50; there are no accounts or API keys — you pay per call in USDC.
Without this server you'd hand-roll x402 payments to call SuVerse. With it, the endpoints appear as native Claude tools: ask in plain language and Claude calls them, paying transparently from your funded Base wallet.
| Tool | Price | Purpose |
|---|---|---|
freight_parse_ratecon | $0.10 | Rate confirmation → JSON |
freight_parse_bol_pod | $0.15 | Bill of Lading / POD → JSON |
freight_parse_fuel_receipt | $0.05 | Fuel receipt → JSON (IFTA) |
freight_parse_w9 | $0.07 | IRS W-9 → JSON |
freight_parse_insurance_cert | $0.08 | ACORD 25 COI → JSON |
freight_parse_permit | $0.25 | Oversize/overweight permit → JSON |
freight_truck_route | $0.50 | Truck-legal routing + tolls + POIs |
freight_calculate_tolls | $0.10 | Toll estimate for a polyline |
freight_trip_telematics | $0.01 | GPS trip analytics |
gov_query | $0.005 | Any of 128 gov services by id |
gov_cms_open_payments | $0.01 | CMS Open Payments by NPI |
gov_fbi_crime_data | $0.01 | FBI crime stats by state/year |
| Tool | Purpose |
|---|---|
gov_list_services | Discover the 128 gov_query service ids + params |
suverse_estimate_cost | Price one or many calls before running them |
suverse_balance | On-chain USDC balance + calls remaining per tool |
suverse_search_endpoints | Search every x402 endpoint SuVerse knows about (own + CDP Bazaar mirror) |
| Tool | Price | Question it answers |
|---|---|---|
suverse_market_pulse | $0.10 | What regime is the crypto market in right now? |
suverse_wallet_reputation | $0.03 | Can this Solana wallet's trading be trusted or copied? |
suverse_token_check | $0.05 | Is this Solana token sane to enter right now? |
These three work differently from the paid tools above: this server does not
pay for them and holds no keys for them. Called without payment they return a
structured payment_required result — what the endpoint answers, the price, and
the verbatim x402 challenge (accepts on Base, Solana, and Cosmos Noble, all
USDC). Your agent (or its runtime) decides whether to pay: sign one of the
accepts with any x402 buyer client (e.g. @suverselabs/x402-client) and call
the tool again with payment_signature set to the base64 header value — it is
forwarded as PAYMENT-SIGNATURE / X-PAYMENT and the full paid verdict
({verdict, signals, data_quality, raw}) comes back. Wallet and mint arguments
are validated as base58 client-side before any network call.
~/Downloads/load_4471.pdf." → freight_parse_ratecon (file_path)gov_list_servicessuverse_estimate_costsuverse_balancegov_query (service: "sec.company_info")file_path inputsDocument tools accept a local file_path — the server reads the file, verifies
it's really a PDF/image via magic bytes, and base64-encodes it. No need to paste
base64 into the chat.
suverse_estimate_cost prices
ahead of time.SUVERSE_MAX_PAYMENT_USDC (default $0.60) and never more than the tool's
published price — whichever is lower.SUVERSE_BASE_PRIVATE_KEY is read from the environment, used only to sign EIP-3009
USDC authorizations locally, and never logged or transmitted anywhere except
as a signed payment header to SuVerse.file_path reads are restricted to your home directory (override with
SUVERSE_ALLOW_PATHS_OUTSIDE_HOME=true), reject sensitive locations
(.ssh, .aws, credentials, key files, …), and are content-type verified.The document-parsing tools work by uploading the file's contents (base64-encoded,
or whatever you pass via pdf_base64 / image_base64 / text) to api.suverse.io,
where they're parsed. So while your private key never leaves your machine, the
documents you ask Claude to parse do. Only pass files you're comfortable sending to
SuVerse for processing. The file_path guards above (home-directory restriction,
sensitive-location denylist, magic-byte type check) limit which files can be read,
but any file you do parse is transmitted. The free tools (gov_list_services,
suverse_estimate_cost, suverse_balance) and the on-chain balance read send no
file data.
| Env var | Default | Notes |
|---|---|---|
SUVERSE_BASE_PRIVATE_KEY | — | Required. 0x Base private key. |
SUVERSE_API_BASE | https://api.suverse.io | |
SUVERSE_MAX_PAYMENT_USDC | 0.60 | Hard per-call ceiling. |
SUVERSE_BASE_RPC_URL | viem default | For suverse_balance reads. |
SUVERSE_ALLOW_PATHS_OUTSIDE_HOME | false | Allow file_path outside $HOME. |
SUVERSE_IDEMPOTENCY_TTL_MS | 120000 | Client idempotency window. |
For contributors / running from source. End users should use the npx Quick Start above instead.
git clone https://github.com/sudzikcoin/suverse-mcp && cd suverse-mcp
npm install
npm run typecheck # tsc --noEmit
npm test # vitest (mocked HTTP)
npm run build # tsup → dist/index.js
npm run dev # run from source (tsx)
To run a local build in Claude Desktop, point command/args at the built file instead of npx:
{
"mcpServers": {
"suverse": {
"command": "node",
"args": ["/absolute/path/to/suverse-mcp/dist/index.js"],
"env": { "SUVERSE_BASE_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY_HERE" }
}
}
}
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.