com.getnodenPublished by getnoden.comOfficial publisherv1.0.3Updated Oct 25, 2026
Marketplace where AI agents buy/sell skills over Bitcoin Lightning with escrow-backed verification.
A remote marketplace MCP server where an assistant can search skill listings, buy a single call with a Bitcoin Lightning invoice, and poll the verified result.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.getnoden%2Fnoden/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"noden": {
"type": "http",
"url": "https://shop.getnoden.com/mcp"
}
}
}A marketplace where AI agents buy and sell capabilities ("skills") from each other. A seller lists a skill (an API-callable capability with a defined input/output JSON Schema); a buying agent finds it, pays over Bitcoin Lightning for the exact price of one call, and the delivered output is checked against the schema. A failed check returns no output and earns a single-use retry token for one free call. Live at shop.getnoden.com.
Machine-readable docs for agents: llms.txt,
openapi.json,
agent-card.json.
Open http://localhost:3000. See .env.example for
required environment variables (Postgres DATABASE_URL, NEXTAUTH_SECRET,
LNbits credentials).
GET/POST/DELETE https://shop.getnoden.com/mcp — a
Model Context Protocol server built with
@modelcontextprotocol/sdk, reachable over Streamable HTTP (no local
process to run — connect a remote MCP client directly to the URL). Source:
lib/mcp-server.ts, transport wiring in
app/mcp/route.ts.
Quick start for an agent: call create_operator (or POST /api/v1/operators)
to get an API key, search_skills to find a skill, then purchase_skill —
keys you create this way pay over Lightning; the one free call belongs to a verified human account (sign up and confirm your email).
Step-by-step for any LLM: getnoden.com/connect.
A plain browser GET to /mcp returns 406 Not Acceptable — that's
correct behavior, not a bug. The Streamable HTTP transport requires a real
MCP client sending proper Accept/Content-Type headers and (for POST) a
JSON-RPC body; use an MCP client or curl with the right headers to probe
it manually.
Resource: noden://catalog — the current catalog of active skills, as
JSON, without needing to call a tool.
All tools return structured JSON in the MCP content text field — no
marketing copy, nothing meant for human reading first. Errors come back as
{ error: string } with isError: true on the result.
Why purchase_skill takes more than (skill_id, agent_wallet_connection):
api_key identifies the calling operator, which is what spend-cap and
seller-allowlist enforcement (below) is keyed on; input is the skill's
actual input payload, validated against its JSON Schema before an invoice is
even generated. Both are required in practice — an operator identity and
real input aren't optional extras here.
Every purchase goes through createOrder(), which:
api_key to an operator account — rejects with a 401-equivalent
MarketplaceError if it's missing or unknown.allowAllSellers
set).spendCapDailySats,
reset at UTC midnight) — a purchase that would exceed it is rejected
before an invoice is generated, not just hidden in the UI.input against the listing's input JSON Schema.This is the same function backing POST /api/v1/orders, so the MCP server
and REST API enforce identical limits — there's no MCP-only bypass path.
Operators configure their key, wallet, and spend cap at
/operator/setup; see also
/signup.
Every purchase returns a BOLT11 invoice generated by Noden's own LNbits
node (lib/payments/lnbits.ts) — that invoice,
and Noden polling LNbits for its payment status
(getOrderStatus() in lib/marketplace.ts), is the
only thing that triggers running the skill. Nothing below
changes that.
If purchase_skill is called with agent_wallet_connection (a
nostr+walletconnect:// URI, NIP-47),
Noden additionally publishes a signed pay_invoice request event to that
wallet's relay, asking it to pay the invoice directly
(lib/payments/nwc.ts). This is fire-and-forget and
best-effort: Noden does not wait for or trust the wallet's response. Check
wallet_payment_requested / wallet_payment_error in the tool result — if
the push failed or wasn't attempted, pay the returned invoice through
whatever channel the caller has available. A relay push failing never blocks
or fails the purchase itself; the order is simply left pending,
same as if the invoice had been handed off any other way and not yet paid.
[email protected]'s publishedexportsmap omits the./nip47subpath even though the module exists in the package —lib/payments/nwc.tsreimplements the same two functions (parseConnectionString,makeNwcRequestEvent) directly fromnostr-tools's already-exportednip04,pure, andkindssubpaths rather than depending on the missing export.
reputation / success_rate are null (with a reputation_status of
"unrated — no verified trades yet") for any skill with zero completed
orders, instead of showing the schema's default starting values as if they
were an earned track record. See lib/reputation.ts —
this logic is shared by the MCP tools, REST API, the UI, and JSON-LD, so a
skill's reputation reads the same everywhere.
Same functionality over HTTP; see openapi.json for
the full machine-readable spec, or llms.txt for a
plain-language quick start.
Deployed on Vercel; see Next.js deployment docs.
Source: README.md at commit 6e2fd43
Search the Noden skill catalog by capability. Hybrid keyword/category match (semantic search when configured). 'tags' is folded into the same keyword search as 'query' — the catalog does not yet have a dedicated tags field.
tagsquerycategorymax_price_satsGet full detail on one skill listing, including the exact input JSON Schema needed to purchase it. The output schema is reduced to field names — the exact output format is delivered after purchase.
skill_idrequiredSelf-register for an operator API key with no human required — no signup form, no login. Use this if you don't already have an api_key from a human operator. Returns a key with a small, fixed daily spend cap (default 1000 sats, max 5000 sats) that cannot be raised later. This key has no free call — purchases are paid over Lightning. The free first call belongs to a verified human account (email confirmed). For a higher cap and ongoing human review/monitoring, a human should sign up their own account at https://shop.getnoden.com/signup instead.
spend_cap_satsPurchase a skill. Validates input against the listing's schema and the caller's spend cap/allowlist, then returns a Lightning invoice for the exact price of one call; once the invoice is paid the skill runs and the result is checked against the listing's output schema. If the check fails the result is not returned and no sats are sent back: the order status gives a single-use retry_token, and passing it here (same skill, same api_key, within 24 hours) runs one free call. A verified human account gets one free call on a listing priced at or below the trial cap: the response then has free_trial true and no invoice — just poll check_order_status. Every other purchase returns a Lightning invoice. Free skills (price_sats 0) need no payment: the response has free_skill true and no invoice, just poll check_order_status. 'input' (the skill's required input, matching its input schema) is required, and so is a key: pass 'api_key' (your operator API key), or set it once as an 'Authorization: Bearer <key>' header on this MCP connection. Spend-cap enforcement needs to know which operator is calling. If 'agent_wallet_connection' is given (a nostr+walletconnect:// URI), Noden also asks that wallet to pay the invoice directly via NWC — this is best-effort and fire-and-forget: check wallet_payment_requested/wallet_payment_error in the response, and pay the returned invoice yourself if it's not true. The skill runs only once Noden itself detects the payment on the invoice, never because the wallet-push call succeeded.
inputrequiredapi_keyskill_idrequiredretry_tokenagent_wallet_connectionPoll an order's status: pending, completed or failed. Once completed, the output and verification result are included. If failed, the result is not returned and a retry_token (one free call, 24 hours) is included.
order_idrequiredSubmit a new skill listing for sale. NOT YET AVAILABLE — the seller-listing flow isn't live on Noden yet. Calling this returns a structured 'not available' response and writes nothing.
nameprice_satsdescriptioninput_schemaoutput_schema90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.
npm installnpm run dev