The Standard Icon Set
NPM · @STANDARDICON/MCP
Search line icons by meaning or by what they look like, and get them as SVG at any size and weight.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of npm servers
Category Design and Media
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 & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 729 tokens (~182/item across 4 items; 4 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 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.
- 15 Nov 26 +1
- Security disclosure: fail → pass ▲ functional
- 14 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 13 Nov 26 −10
- Stability: 0.00 → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.3.0-alpha.3 → 0.3.0-alpha.4 functional
- 12 Nov 26 68
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 21 Nov 2026 · Analysed npm/@standardicon/mcp@0.3.0-alpha.4
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 →
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 →
get_icon Get an icon ~269
Get one icon as SVG markup, at a size and weight. The SVG draws in currentColor. Sizes: 16, 18, 20, 22, 24, 28, 32, 40, 48. Weights: thin, regular, semibold, bold, black; Semibold comes in 18 and up, bold in 32 and up, and black in 40 and up. Lines grow with the size.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The icon name, or one of its aliases, as returned by search_icons. |
| size | integer | – | Pick it from the text beside the icon. Match the icon to the text beside it: 12 to 13px text takes a 16 icon, 14 to 15px takes 18, 16 to 17px takes 20, 18 to 19px takes 22, 20 to 21px takes 24, and l… |
| weight | string | – | Lines at 18px: thin 1px, regular 1.33px (the default), semibold 1.5px, bold 2px, black 2.5px. Lines grow with the size. |
No output schema declared.
No examples provided.
list_categories List categories ~19
List the icon categories and how many icons each has.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_icons List icons in a category ~35
List every icon in one category, with a description of each drawing.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | A category name from list_categories. |
No output schema declared.
No examples provided.
search_icons Search icons ~93
Find icons by meaning, name, or what they look like. Returns names with a description of each drawing and when to use it.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only search one category. list_categories gives the names. |
| limit | integer | – | – |
| query | string | yes | What the icon is for, or what it looks like. For example "delete", "upload file", or "bell with a plus". |
No output schema declared.
No examples provided.
How do I install the The Standard Icon Set MCP server?
The Standard Icon Set runs locally as an npm package, launched with npx -y @standardicon/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 · @standardicon/mcp
claude mcp add com-standardicon-icons -- npx -y @standardicon/mcp
What is the The Standard Icon Set MCP server?
The Standard Icon Set is an MCP server listed in the public MCP registry as com.standardicon/icons. Search line icons by meaning or by what they look like, and get them as SVG at any size and weight. This page covers its npm package (@standardicon/mcp).
Is the The Standard Icon Set MCP server safe to use?
The Standard Icon Set scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 The Standard Icon Set MCP server expose?
The Standard Icon Set exposes 4 tools: search_icons, get_icon, list_categories, list_icons. Their descriptions and schemas cost roughly 416 tokens of context every time the server is loaded.
Is the The Standard Icon Set MCP server still maintained?
The Standard Icon Set is still listed as active in the MCP registry. We last reached this channel on 21 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 The Standard Icon Set MCP server under?
The Standard Icon Set declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the The Standard Icon Set MCP server?
VerifyMCP ran 16 checks on The Standard Icon Set, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.