OpenNodes
NPM · @OPENNODES/CLI · 2 COMPONENTS
Discover verified AI inference nodes, get the best node+model per task, pre-price chains.
Available components
Last scanned (3 hours ago)
Scores higher than 93% of npm servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security97
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 4 of 7 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to opennodes-io/opennodes). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1168 tokens (~233/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management75
- Stability check failed: the tool surface changed between 0.1.2 and 0.1.14: 0 tool removals, 2 breaking changes, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 68 to 72.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 62 to 65.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 52 to 55.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 45 to 48.
- 24 Oct 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.78 ▲ functional
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.78 ▲ functional
- Package version: 0.1.9 → 0.1.14 functional
- Package version: 0.1.9 → 0.1.13 functional
- 22 Oct 26 −9
- Known CVEs: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Dependency health: 0.78 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.6 → 0.1.9 functional
- Package version: 0.1.6 → 0.1.8 functional
- Package version: 0.1.6 → 0.1.7 functional
- 21 Oct 26 +1
- Security disclosure: fail → pass ▲ functional
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 5 Nov 2026 · Analysed npm/@opennodes/cli@0.1.14
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | opennodes-io/opennodes |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/opennodes-io/opennodes/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3420389609 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ced6af2200476839c7e09af736e5f2ecae411029865df67c67ebd36dd2779613b7d61bae359ec4afb316e5fa01c1da9e6e040b770b0791cdab1933746 |
Background: How many MCP packages publish verified provenance →
Dependencies 7 packages
| Packages resolved | 7 |
|---|---|
| Stale | 4 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
estimate Estimate the cost of a chain ~103
Pre-price an invocation chain BEFORE spending money. Each step is either a concrete offering ("node_id/offering_id") or a `select` query that picks the best match, plus expected input and output tokens. Returns per-step cost bounds in USD, the pinned card_revision that makes each estimate enforceable at invocation, and chain totals. Use it to compare routes or budget a multi-model pipeline; nothing is invoked or charged.
| Name | Type | Req | Description |
|---|---|---|---|
| steps | array | yes | Steps in execution order. |
No output schema declared.
No examples provided.
get_node Get one node ~164
Who runs a node and how it has behaved: operator, country and regions, endpoints, declared hardware, trust tier and its history (verifications, suspensions, reinstatements, with reasons), recent registry probe results with an availability summary, and its offerings with context window and price. Use it to vet a provider before relying on it; take node_id from search_offerings, recommend or get_offering results. For one offering's full card, use get_offering.
| Name | Type | Req | Description |
|---|---|---|---|
| node_id | string | yes | Reverse-DNS node id, e.g. "io.opennodes.demo-node" or "import.openrouter.ai". |
| offering_limit | integer | – | Maximum offerings to list; imported catalogs can hold hundreds. `offerings_total` always gives the full count. |
No output schema declared.
No examples provided.
get_offering Get one offering ~104
Full detail for one offering: endpoints, pricing, serving capabilities (context window, supported features, languages, hardware), data policy, trust tier, and the registry's observed probe results. Take node_id and offering_id from search_offerings or recommend results.
| Name | Type | Req | Description |
|---|---|---|---|
| node_id | string | yes | Reverse-DNS node id, e.g. "io.opennodes.demo-node". |
| offering_id | string | yes | Offering id within that node, as returned by search_offerings. |
No output schema declared.
No examples provided.
recommend Recommend a node and model ~210
Recommend the best AI node + model for a task, with an enforceable cost estimate and human-readable reasons. Use this first when you know the task but not the model. Features (task class, size, language, needs) are extracted LOCALLY from `task` and only those features are sent to the registry — the prompt never leaves this machine. Returns ranked candidates with score components, a cost estimate pinned to the node's card revision, an optional cheaper two-step scenario, and MCP tool categories the task likely needs. To browse instead, use search_offerings; to price a specific chain, use estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| est_output_tokens | integer | – | Expected answer length in tokens, if known. Improves the cost estimate; otherwise inferred from the task. |
| policy | object | – | Optional constraints and preferences for the recommendation. |
| task | string | yes | The task description or the prompt itself, e.g. "Translate this Polish contract to English and list the risks". Analysed locally; not sent. |
No output schema declared.
No examples provided.
search_offerings Search inference offerings ~491
Search AI inference offerings in the OpenNodes registry — registered nodes AND imported catalogs (OpenRouter, Hugging Face Inference Providers, models.dev, local nodes). All filters are optional and combine with AND. Returns { offerings, total }: each offering has node_id, offering_id, model, pricing (USD per MTok), trust tier, serving capabilities, measured probe results, and a rank explanation. Use get_offering for one offering's full card, recommend to let the advisor choose.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | – | Model family or exact artifact, e.g. "llama-3.3" or "qwen3". Matches model.family or model.artifact exactly. |
| jurisdiction | string | – | Only operators that declare a country inside it: "eea" (EU + Iceland, Liechtenstein, Norway) or comma-separated ISO country codes, e.g. "DE,FI". Registered nodes declare their country; imported listi… |
| lang | string | – | Language with minimum grade, "<iso-code>[:basic|strong|native]", e.g. "pl:strong" or "de". |
| limit | integer | – | Maximum offerings to return; `total` still counts every match. |
| max_input_price | number | – | Maximum input price in USD per million tokens. |
| min_context | integer | – | Minimum context window in tokens, e.g. 32768. |
| modality | string | – | What the model consumes/produces. Use "text" for chat and completion models. |
| q | string | – | Free-text match against the model metadata, offering id, and node id, e.g. "bielik" or "coder". |
| scheme | string | – | Payment scheme the offering must accept. "free" finds no-cost offerings. |
| sort | string | – | rank = registry ranking (price, trust, reliability); price = cheapest input first; ttft = fastest first token; tps = highest throughput. |
| supports | string | – | Comma-separated features the offering must all support: tool_calls, json_mode, vision, streaming. Example: "tool_calls,json_mode". |
| tier | string | – | Minimum trust tier. unverified < community (passed automated checks) < verified (identity and context verified) < attested. |
No output schema declared.
No examples provided.
How do I install the OpenNodes MCP server?
OpenNodes runs locally as an npm package, launched with npx -y @opennodes/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @opennodes/cli
claude mcp add opennodes-io-opennodes -- npx -y @opennodes/cli
What is the OpenNodes MCP server?
OpenNodes is an MCP server listed in the public MCP registry as io.github.opennodes-io/opennodes. Discover verified AI inference nodes, get the best node+model per task, pre-price chains. This page covers its npm package (@opennodes/cli).
Is the OpenNodes MCP server safe to use?
OpenNodes scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 OpenNodes MCP server expose?
OpenNodes exposes 5 tools: recommend, search_offerings, get_offering, get_node, estimate. Their descriptions and schemas cost roughly 1,072 tokens of context every time the server is loaded.
Is the OpenNodes MCP server still maintained?
OpenNodes is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the OpenNodes MCP server under?
OpenNodes declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.