Skip to content

noden MCP server

com.getnoden/nodengetnoden.comstreamable-httpv1.0.3Scanned

Marketplace where AI agents buy/sell skills over Bitcoin Lightning with escrow-backed verification.

6 tools: 1 do something that can't be undone, 2 change things and 3 only read.

Tools: 0 delete, 1 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the noden MCP server can do

The noden MCP server is published by getnoden.com, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (purchase_skill) and create or change data (2 tools: create_operator and submit_skill), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Can't be undone 1Claude Code: ask
  • purchase_skillPurchase a skill.No findings

    Why it is in this group

    • The name "purchase_skill" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Purchase a skill. Validates input against the listing's schema and the caller's spend cap/allowlist, then, unless the account has enough prepaid credits (see below), 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 account has enough prepaid credits for the call, they are used automatically: the response has paid_with_credits true, credits_charged and credits_remaining, and no invoice — just poll check_order_status. 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.
Changes things 2Claude Code: ask
  • create_operatorSelf-register for an operator API key with no human required — no signup form, no login.No findings

    Why it is in this group

    • The name "create_operator" says "create": a word for a change.
    Description, as the server wrote it
    Self-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.
  • submit_skillSubmit a new skill listing for sale.No findings

    Why it is in this group

    • The name "submit_skill" says "submit": a word for a change.
    Description, as the server wrote it
    Submit 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.
Only reads 3Show 3 read-only tools
  • check_order_statusPoll an order's status: pending, completed or failed.No findings

    Why it is in this group

    • The name "check_order_status" says "status": a word for reading.
    Description, as the server wrote it
    Poll 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.
  • get_skillGet full detail on one skill listing, including the exact input JSON Schema needed to purchase it.No findings

    Why it is in this group

    • The name "get_skill" says "get": a word for reading.
    Description, as the server wrote it
    Get 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.
  • search_skillsSearch the Noden skill catalog by capability.No findings

    Why it is in this group

    • The name "search_skills" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:39 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://shop.getnoden.com/mcp: tools/list returned 6 tools to an anonymous client, including purchase_skill (irreversible), create_operator (write), submit_skill (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http noden https://shop.getnoden.com/mcp
claude mcp add --transport http noden https://shop.getnoden.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__noden__search_skills",
      "mcp__noden__get_skill",
      "mcp__noden__check_order_status"
    ],
    "ask": [
      "mcp__noden__create_operator",
      "mcp__noden__purchase_skill",
      "mcp__noden__submit_skill"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as noden. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.getnoden/noden/verify?hash=d6a052de210eae69fad41ecf1f76b75b641fc218bd8e91aba2580826ee262a56" | jq -e '.changed == false'

Pinned hash d6a052de210e, from Nov 10, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.getnoden/noden/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.getnoden/noden
[![Anlyon Radar](https://radar.anlyon.com/badge/com.getnoden/noden.svg)](https://radar.anlyon.com/servers/com.getnoden/noden)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:55 UTC.

noden MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the noden MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the noden MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the noden MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: purchase_skill.

What tools does the noden MCP server have?

6 tools: 1 irreversible, 2 write, 3 read. purchase_skill, create_operator, submit_skill, search_skills, get_skill and check_order_status.

Does the noden MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the noden MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the noden MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.