Frisk vs Shinjuku Shielded — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Frisk vs Shinjuku Shielded
In-depth architectural comparison of the Frisk and Shinjuku Shielded MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Frisk
Finance & Fintech · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Shinjuku Shielded
Finance & Fintech · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Frisk if you need specialized Finance & Fintech tools running via a local process. Choose Shinjuku Shielded if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Frisk when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Screen a counterparty an agent is about to pay. Runs entirely offline: address sanity, dynamic-payTo comparison, transport check, and your spending policy. Returns allow / review / block with reasons. Advisory: the caller decides. Set FRISK_API_KEY to add hosted reputation signals.
Shinjuku Shielded Tools (9)
shinjuku_setup
Asks you to confirm in your MCP client that it may create a Shinjuku Shielded wallet on this machine, and shows the caps. Then it runs the setup and switches the same server to the wallet tools. It never asks for a secret. A client that cannot ask is told to run `npx -y shinjuku-shielded setup` in…
wallet_status
Says whether the wallet is set up, and what to do next.
wallet_shield
Moves USDC from the wallet's own Solana key into your shielded balance. It is on with `--proof-tools`. `--no-shield` turns it off. Funding takes minutes: the first call starts it and returns a stage. Call again with the same `request_id` to see the stage. It never starts a second deposit. When the…
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Frisk is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Shinjuku Shielded belongs to Finance & Fintech using local stdio subprocess. Select Frisk when you need capabilities focused on finance & fintech and Shinjuku Shielded when you require tools for finance & fintech.
Searches public x402 listings (Coinbase x402 Bazaar, PayAI, Dexter, and others) on your machine and returns the sellers that match. Pays nothing. The first call takes about 15 s.
x402_preview
One unpaid request. Returns the seller's price, the scheme, and whether your caps allow it. Pays nothing. For a standard `exact` seller it adds `feeAtomic` (our fee) and `totalAtomic` (price plus fee, what leaves your balance). A seller that lists several networks is priced from its Solana offer.
x402_pay
Pays the URL (if it asks for payment) and returns the answer. A URL that does not answer 402 is fetched once and nothing is paid. An image answer (image bytes, or JSON `image_base64`) comes back as an MCP image block, and the file is saved. A payment that landed, from a seller that gives no answer,…
wallet_unshield
Sends shielded USDC to a public Solana address. It is on with `--exit-proof-tools` and `--profile`. Our facilitator pays every network fee. The same `request_id` never unshields twice. An address that you named with `--unshield-to` is sent at once. Any other address is sent only after you confirm i…
wallet_balance
ONE balance (`balanceAtomic`, what `x402_pay` can spend) and UNSHIELDED (plain USDC on the wallet's own Solana key). `breakdown` names the parts of the one balance: `shieldedAtomic` (what `wallet_unshield` can send), `refundsInFlightAtomic` (a Shinjuku refund on its way back), and `setAsideAtomic`…
wallet_receipts
Your most recent paid receipts: host (never the full URL), amount, transaction, time.