Noden MCP server

• Registry namecom.getnoden/nodenverified in the MCP registry

The registry name sits under getnoden.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools6
• Server calls itselfnoden
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 111 ms.

• Its tools do none of the product's use cases we checked: extract structured data from invoices and receipts; scrape web pages into structured data; enrich sales leads with additional company data.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it0 of 3 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer143 ms
• Space in an agent's context≈ 1,294 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsC · 69 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 5 of 6
• Not saying whether it only reads or can destroy: 6 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_skills

  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.

• get_skill

  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.

• create_operator

  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…

• purchase_skill

  Purchase 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…

• check_order_status

  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.

• submit_skill

  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.