com.getnoden/noden
REMOTE · SHOP.GETNODEN.COM · SCANNED SEP 26
Marketplace where AI agents buy/sell skills over Bitcoin Lightning with escrow-backed verification.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 699 tokens (~99/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.getnoden/noden MCP server?
com.getnoden/noden is a hosted endpoint at https://shop.getnoden.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · shop.getnoden.com
claude mcp add --transport http com-getnoden-noden 'https://shop.getnoden.com/mcp'
{
"mcpServers": {
"com-getnoden-noden": {
"url": "https://shop.getnoden.com/mcp"
}
}
} {
"servers": {
"com-getnoden-noden": {
"type": "http",
"url": "https://shop.getnoden.com/mcp"
}
}
} [mcp_servers.com-getnoden-noden] url = "https://shop.getnoden.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-getnoden-noden": {
"type": "remote",
"url": "https://shop.getnoden.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-getnoden-noden --url 'https://shop.getnoden.com/mcp' --transport streamable-http
mcp_servers:
com-getnoden-noden:
url: "https://shop.getnoden.com/mcp" {
"McpServers": {
"com-getnoden-noden": {
"Transport": "http",
"Url": "https://shop.getnoden.com/mcp"
}
}
} assistant mcp add com-getnoden-noden -t streamable-http -u 'https://shop.getnoden.com/mcp'
{
"mcpServers": {
"com-getnoden-noden": {
"type": "http",
"url": "https://shop.getnoden.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://shop.getnoden.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shop.getnoden.com | CN=YR1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | RSA 2048 | SHA256-RSA | 535f6a9e019b15ea1d2ede7f6fc641edee1 |
| SANs: shop.getnoden.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of shop.getnoden.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| getnoden.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shop.getnoden.com/mcp | Verified | 200 | |
| http (plaintext) | http://shop.getnoden.com/mcp | HTTPS enforced | 308 | https://shop.getnoden.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_order_status ~44
Poll an order's status. Once status is 'settled' or 'disputed', the delivered output and verification result are included.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
create_operator ~131
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; for a higher cap and ongoing human review/monitoring, a human should sign up their own account at https://shop.getnoden.com/signup instead.
| Name | Type | Req | Description |
|---|---|---|---|
| spend_cap_sats | number | – | Requested daily spend cap in sats. Defaults to 1000, capped at 5000. |
No output schema declared.
No examples provided.
get_skill ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_id | string | yes | – |
No output schema declared.
No examples provided.
purchase_skill ~264
Purchase a skill. Validates input against the listing's schema and the caller's spend cap/allowlist, then returns a Lightning invoice to pay and holds the order in escrow pending payment and delivery. 'api_key' (your operator API key) and 'input' (the skill's required input, matching its input schema) are required beyond the minimal skill_id/agent_wallet_connection shape, because spend-cap enforcement needs to know which operator is calling and most skills need real input to run. 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. Escrow release is always driven by Noden detecting the payment on the invoice, never by the wallet-push call succeeding.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_wallet_connection | string | – | Optional nostr+walletconnect:// URI — if given, Noden asks this wallet to pay the invoice |
| api_key | string | yes | Your operator API key |
| input | object | yes | Input matching the skill's input JSON Schema |
| skill_id | string | yes | – |
No output schema declared.
No examples provided.
search_skills ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| max_price_sats | number | – | – |
| query | string | – | Free-text capability description, e.g. 'reviews contracts' |
| tags | array | – | Extra keywords, matched the same way as query |
No output schema declared.
No examples provided.
submit_skill ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| input_schema | object | – | – |
| name | string | – | – |
| output_schema | object | – | – |
| price_sats | number | – | – |
No output schema declared.
No examples provided.
What is the com.getnoden/noden MCP server?
com.getnoden/noden is an MCP server listed in the public MCP registry as com.getnoden/noden. Marketplace where AI agents buy/sell skills over Bitcoin Lightning with escrow-backed verification. This page covers its hosted endpoint (https://shop.getnoden.com/mcp).
Is the com.getnoden/noden MCP server safe to use?
com.getnoden/noden scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.getnoden/noden MCP server expose?
com.getnoden/noden exposes 6 tools: search_skills, get_skill, create_operator, purchase_skill, check_order_status, submit_skill. Their descriptions and schemas cost roughly 683 tokens of context every time the server is loaded.
Does the com.getnoden/noden MCP server require authentication?
No. We connected to com.getnoden/noden without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.getnoden/noden MCP server still maintained?
com.getnoden/noden is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.