Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.nodoicons/nodo-icons

NPM · @NODO-ICONS/MCP

Search 5,000 Nodo icons, get SVG, React or Vue code. Free Linear style, Pro styles with a license.

Available components

63 Trust /100

Last scanned (4 hours ago)

Scores higher than 31% of npm servers

Category Design and Media

Trust breakdown (7 categories)

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 325 tokens (~81/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 61

    First indexed and scored.

Diagnostics

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/@nodo-icons/mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~286 tokens

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 →

Tool Tokens
get_icon ~134

Get ready-to-paste code for one Nodo icon: inline SVG, a React or Vue component import, or an SVG sprite reference. The "linear" style is free (MIT); the other styles are Nodo Icons Pro.

NameTypeReqDescription
colorstring–Any CSS color. Default inherits the text color.
formatstring––
namestringyesExact icon name from search_icons, e.g. "credit-card".
sizenumber––
strokeWidthnumber–Only for stroke styles. Default depends on the style (Linear 1.5).
stylestring––

No output schema declared.

No examples provided.

list_categories ~19

List icon categories with the number of icons in each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_styles ~26

List the ten Nodo Icons styles, which are free or Pro, and their stroke settings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_icons ~107

Search the Nodo Icons catalogue (5,000 UI icons on a 24×24 grid) by name, keyword or synonym. Returns icon names to use with get_icon. Use simple English words, e.g. "upload", "credit card", "settings".

NameTypeReqDescription
categorystring–Optional category filter (see list_categories).
limitinteger––
querystringyesWords describing the icon, e.g. "trash", "user add", "cloud rain".

No output schema declared.

No examples provided.

Install

How do I install the com.nodoicons/nodo-icons MCP server?

com.nodoicons/nodo-icons runs locally as an npm package, launched with npx -y @nodo-icons/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @nodo-icons/mcp

# add to Claude Code
claude mcp add com-nodoicons-nodo-icons -- npx -y @nodo-icons/mcp
Common questions

What is the com.nodoicons/nodo-icons MCP server?

com.nodoicons/nodo-icons is an MCP server listed in the public MCP registry as com.nodoicons/nodo-icons. Search 5,000 Nodo icons, get SVG, React or Vue code. Free Linear style, Pro styles with a license. This page covers its npm package (@nodo-icons/mcp).

Is the com.nodoicons/nodo-icons MCP server safe to use?

com.nodoicons/nodo-icons scores 63 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. 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.nodoicons/nodo-icons MCP server expose?

com.nodoicons/nodo-icons exposes 4 tools: search_icons, get_icon, list_styles, list_categories. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.

Is the com.nodoicons/nodo-icons MCP server still maintained?

com.nodoicons/nodo-icons 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 com.nodoicons/nodo-icons MCP server under?

com.nodoicons/nodo-icons declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.