Fatstack MCP server
Commit 28 Sep 2026Memungkinkan AI agent untuk menemukan dan membayar pemanggilan MCP tool menggunakan USDC di jaringan Base melalui marketplace non-custodial.
Juga dikenal sebagai f4tst4ck/fatstack-tools, fatstack-tools
- Stars
- 0
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 1.0.0
- Commit terakhir
- 28 Sep 2026
- Lisensi
- MIT
Apa itu Fatstack MCP?
Memungkinkan AI agent untuk menemukan dan membayar pemanggilan MCP tool menggunakan USDC di jaringan Base melalui marketplace non-custodial.
Ringkasan dibuat dari README proyek
Tentang Fatstack MCP server
Fatstack menyediakan marketplace non-custodial yang dirancang agar AI agent dapat menemukan dan membeli akses ke API serta pemanggilan MCP tool. Dengan menggunakan protokol x402 di jaringan Base, sistem ini memungkinkan penetapan harga per-call dalam USDC. Platform ini berfungsi sebagai registry di mana provider mendaftarkan tool dan agent menemukannya untuk mengeksekusi tugas. Karena bersifat non-custodial, layanan ini tidak pernah memegang dana pengguna, private keys, atau wallet platform dalam jalur pembayaran. Sebaliknya, pembayaran berpindah langsung dari wallet agent ke wallet provider.
Developer dapat mengintegrasikan sistem ini menggunakan @fatstack/x402 SDK untuk provider atau package @fatstack/ai-sdk-tools untuk agent. Agent menggunakan wallet sebagai identitas mereka, sehingga tidak memerlukan akun tradisional atau API keys. Untuk mencegah pengeluaran yang tidak terkendali, client agent memerlukan guard tertentu, seperti limit maxPerDay atau maxPerCall. Sistem ini menggunakan proses otorisasi EIP-3009 sehingga agent cukup menandatangani izin daripada harus membayar gas untuk setiap transaksi individual.
Apa yang bisa Anda lakukan dengannya
- 1Monetisasi route API yang sudah adaDeveloper dapat menambahkan paywall pada route Hono, Express, atau Next.js yang sudah ada untuk mengenakan harga USDC tertentu per call.
- 2Membekali agent dengan tool berbayarAI agent dapat diberikan akses ke katalog tool sambil tetap mematuhi batasan pengeluaran harian dan per-call yang ketat.
- 3Otomatisasi penemuan toolAgent dapat menjelajahi seluruh katalog marketplace hanya dengan menambahkan satu endpoint MCP server.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Fatstack MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Fatstack MCP di Claude Code
$ claude mcp add --transport http fatstack-tools https://www.fatstack.net/api/mcpInstal Fatstack MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"fatstack-tools": {
"url": "https://www.fatstack.net/api/mcp"
}
}
}Instal Fatstack MCP di VS Code
.vscode/mcp.json
{
"servers": {
"fatstack-tools": {
"type": "http",
"url": "https://www.fatstack.net/api/mcp"
}
}
}Instal Fatstack MCP di VS Code CLI
$ code --add-mcp '{"name":"fatstack-tools","type":"http","url":"https://www.fatstack.net/api/mcp"}'Instal Fatstack MCP di Codex
$ codex mcp add fatstack-tools --url https://www.fatstack.net/api/mcpInstal Fatstack MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.fatstack-tools] url = "https://www.fatstack.net/api/mcp"
Instal Fatstack MCP di Gemini CLI
$ gemini mcp add -s user --transport http fatstack-tools https://www.fatstack.net/api/mcpInstal Fatstack MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"fatstack-tools": {
"url": "https://www.fatstack.net/api/mcp",
"type": "http"
}
}
}Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkauf4tst4ck/fatstack-tools is public and reachablegithub.com/f4tst4ck/fatstack-tools ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-09-28github.com/f4tst4ck/fatstack-tools ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPinitialize answered with protocol 2025-06-18 in 506 msLolos
README
Lihat di GitHubFatstack
A non-custodial marketplace where AI agents discover and pay for API and MCP tool calls in USDC, per call, over x402 on Base.
A provider lists a tool. An agent finds it in the registry and calls it. The tool answers
402 Payment Required with a price. The agent signs a USDC payment authorisation and
retries. The call goes through and the money moves wallet to wallet.
Fatstack never touches the money. There is no custody, no withdrawal function, no platform wallet in the payment path, and no stored private keys. Payment is a direct transfer from the agent's wallet to the provider's — or, once a provider's promotional period ends, through an immutable splitter contract that pays the provider and a 2% platform fee in one atomic transaction. If a change would let Fatstack move someone else's money, it is a bug.
Use it from an agent, in one line
Add one MCP server and your agent has the whole catalog:
https://www.fatstack.net/api/mcp
Listing what is available is free; only calls cost anything. There is no account, no API key
and no signup — the wallet is the identity. Paying needs an
x402-capable client; any MCP client can browse.
Published in the official MCP registry as net.fatstack/registry.
This repository holds the parts you run, audit, or depend on. The marketplace application itself is closed; everything an integrator touches is here, under MIT.
The payment cycle
sequenceDiagram
participant A as Agent
participant T as Tool (provider)
participant F as Facilitator
participant C as USDC on Base
A->>T: call the tool
T-->>A: 402 Payment Required + price, asset, payTo, resource
Note over A: signs an EIP-3009 authorisation<br/>covering exactly this resource
A->>T: retry with X-PAYMENT
T->>F: verify
F-->>T: valid
T->>T: run the handler
T->>F: settle
F->>C: transferWithAuthorization
C-->>F: mined
T-->>A: 200 + result
The agent signs an authorisation, not a transaction: it never pays gas and never sends a transfer itself. The facilitator broadcasts it and pays the gas.
Payments are final. Once settled on chain the transfer cannot be reversed, and there are no refunds. That sentence appears in every 402 body, every quote object, and every payment-facing page, and it is not decoration — it is the property that makes per-call pricing work without an escrow.
Quickstart — providers
Put a paywall in front of a route you already have. Two lines of setup, and the price is per call.
npm install @fatstack/x402
import { Hono } from 'hono';
import { paywall } from '@fatstack/x402';
import { honoPaywall } from '@fatstack/x402/hono';
const app = new Hono();
app.use(
'/convert',
honoPaywall(
paywall({
price: '0.001', // USDC, per call
wallet: '0xYourWallet', // paid directly, wallet to wallet
toolId: 'unit-convert',
network: 'base-sepolia', // test here before base
}),
),
);
app.post('/convert', (c) => c.json({ celsius: 20, fahrenheit: 68 }));
Adapters ship for Hono, Express and Next on their own entry points —
@fatstack/x402/hono, /express, /next — so importing the client into an edge runtime
does not drag a Node framework in with it.
Full walkthrough, including listing the tool: docs/provider-quickstart.md
Quickstart — agents
Give a model a set of paid tools it can call, with a spending limit it cannot exceed.
npm install @fatstack/ai-sdk-tools ai viem
import { generateText } from 'ai';
import { fatstackTools } from '@fatstack/ai-sdk-tools';
import { privateKeyToAccount } from 'viem/accounts';
const tools = await fatstackTools({
wallet: privateKeyToAccount(process.env.AGENT_PRIVATE_KEY),
networks: ['base'], // the catalogue is mainnet-only; USDC here is real
guards: {
maxPerDay: 0.5, // hard ceiling per UTC day, in USD
maxPerCall: 0.01, // refuse any single call dearer than this
},
});
const { text } = await generateText({ model, tools, prompt: 'Convert 20C to F.' });
guards is a required argument with no default. A tool set that can spend money should
never be constructible by accident, so omitting it is a type error rather than an
unlimited budget.
Full walkthrough: docs/agent-quickstart.md
What is in here
| Path | What it is |
|---|---|
sdk/ |
@fatstack/x402 — provider middleware and agent client |
integrations/ai-sdk-tools/ |
@fatstack/ai-sdk-tools — a Vercel AI SDK tool set that pays per call |
contracts/ |
The USDC payment splitter and its factory, with tests and deployment gates |
facilitator/THREAT-MODEL.md |
Written verdicts on six attack classes against the payment path |
docs/ |
Provider and agent quickstarts, and the registry format |
Packages: @fatstack/x402 ·
@fatstack/ai-sdk-tools
Marketplace: fatstack.net ·
Registry: registry.json
Security
The payment path was audited against six attack classes — replay, concurrency, cross-resource substitution, verify/settle ordering, field binding, and misconfiguration. Each has a written verdict and at least one test that proves the safe behaviour, run against a real facilitator and real settlements on Base Sepolia rather than mocks.
facilitator/THREAT-MODEL.md has the verdicts. contracts/SECURITY.md covers the splitter.
One class came back vulnerable, and it is worth reading even if you never use Fatstack, because it is a property of x402 rather than of this implementation.
Cross-resource replay
An EIP-3009 authorisation covers (from, to, value, validAfter, validBefore, nonce). It
does not cover what was bought. So an authorisation signed to pay for one tool was
accepted by a different, more expensive tool from the same provider — same payee, same
asset, a valid signature, and nothing in the signed material to say otherwise.
Reproduced on Base Sepolia, settled on chain:
0xd95ea771333c8f33f346c316fad30a64585156831d09e298d501c5b1e17e5659
Fixed in @fatstack/x402 0.2.0 (current release 0.2.1, which is the same code
under the correct MIT licence metadata). The middleware now binds a payment to the resource it
was quoted for and refuses a mismatch with resource_mismatch, before the facilitator is
called — so a mismatched payment costs nothing and is never settled. Nothing a 402 quotes
to agents changed.
If you built on x402 without checking that the payment in hand was quoted for the resource in hand, check now.
The finding that shaped the contract
An earlier draft of the splitter took the provider as a call argument. That argument is not covered by the payer's signature either, so anyone observing a pending authorisation could have submitted it with their own address and taken the provider's 98%. The provider is now fixed at construction — one splitter per provider, its address derivable in advance with CREATE2 — which removes the parameter and with it the attack.
See The finding that changed the design in contracts/SECURITY.md.
Reporting
Found something? Open an issue for anything already public. For an unreported vulnerability in the payment path, please report privately through GitHub's security advisories on this repository rather than in a public issue.
The contracts are unaudited
The splitter is small, immutable, and has no owner, no pause, no proxy, and no upgrade
path. It is covered by 34 tests including a fork test against real USDC on Base, and its
fee arithmetic is asserted against the same
vectors.json as the TypeScript implementation, so an
on-chain split and a quoted price cannot drift apart.
No third party has reviewed it. Read it yourself before depending on it — it is about fifteen lines of code that move money and a hundred lines explaining why.
Contributing to this repository
Some files here differ from their counterparts in the closed repository, because operator
detail has been removed. .redactions lists them and scripts/check-redactions.sh refuses
anything that puts that material back. Run it before pushing.
Licence
MIT. See LICENSE.
Pertanyaan tentang Fatstack MCP
Bagaimana cara menambahkan Fatstack MCP ke Claude Code?
Jalankan claude mcp add --transport http fatstack-tools https://www.fatstack.net/api/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Fatstack MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bagaimana cara agent membayar tool?
Agent menandatangani otorisasi pembayaran USDC untuk resource tertentu, yang kemudian diselesaikan melalui facilitator di jaringan Base.
Apakah Fatstack menyimpan dana pengguna?
Tidak, Fatstack adalah marketplace non-custodial dan tidak pernah menyentuh uang atau menyimpan private keys.
Apakah saya bisa mendapatkan pengembalian dana jika pembayaran sudah dilakukan?
Tidak, semua pembayaran bersifat final setelah diselesaikan di blockchain.
Apakah diperlukan akun atau API key untuk menggunakan registry ini?
Tidak, tidak diperlukan pendaftaran atau API key; wallet pengguna berfungsi sebagai identitas mereka.