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.

Iconoteka

NPM · ICONOTEKA-MCP · SCANNED SEP 25

Search 1300 open-source icons in 7 weights and 2 styles, and get paste-ready SVG.

Available components

−2 this week 73 Trust /100
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 Security98
  • 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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 232 tokens (~77/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the Iconoteka MCP server?

Iconoteka runs locally as an npm package, launched with npx -y iconoteka-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 · iconoteka-mcp

# add to Claude Code
claude mcp add turbaba-iconoteka -- npx -y iconoteka-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "turbaba-iconoteka": {
      "command": "npx",
      "args": [
        "-y",
        "iconoteka-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "turbaba-iconoteka": {
      "command": "npx",
      "args": [
        "-y",
        "iconoteka-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add turbaba-iconoteka -- npx -y iconoteka-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "turbaba-iconoteka": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "iconoteka-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add turbaba-iconoteka --command npx --arg -y --arg iconoteka-mcp
# ~/.hermes/config.yaml
mcp_servers:
  turbaba-iconoteka:
    command: "npx"
    args: ["-y", "iconoteka-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "turbaba-iconoteka": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "iconoteka-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add turbaba-iconoteka -t stdio -c npx -a -y iconoteka-mcp
// mcp.json
{
  "mcpServers": {
    "turbaba-iconoteka": {
      "command": "npx",
      "args": [
        "-y",
        "iconoteka-mcp"
      ]
    }
  }
}
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.

  • 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
  • 22 Sept 26 +1

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

  • 20 Sept 26 +1

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

  • 19 Sept 26 −5
    • Source repository: pass → fail ▼ security
  • 18 Sept 26 +1

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

  • 16 Sept 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.

  • 15 Sept 26 +15
    • Stability: 0.20 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.1 → 0.2.2 functional
  • 14 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
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 25 Sept 2026 · Analysed npm/iconoteka-mcp@0.2.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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~232 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 ~112

Return paste-ready SVG markup. Pass one name, or an array of names to get several in a single call — building a toolbar needs one request, not eight. The path uses fill="currentColor", so it inherits the surrounding text colour. Licensed MIT — free to use, no attribution required.

NameTypeReqDescription
name–yesOne icon name from search_icons, e.g. "bell", or several: ["bell", "trash"]
stylestring–Default stroke
weightstring–Default regular

No output schema declared.

No examples provided.

list_categories ~18

List every category with how many icons it holds.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_icons ~102

Search the Iconoteka icon library by meaning or name. Returns ranked matches with the weights and styles available for each. Use this before get_icon to find the right icon name.

NameTypeReqDescription
categorystring–Restrict to one category, e.g. Interface, Nature, Transportation
limitinteger–Max results (default 20)
querystringyesWhat the icon should depict, e.g. "notification bell" or "shopping cart"

No output schema declared.

No examples provided.

Common questions

What is the Iconoteka MCP server?

Iconoteka is an MCP server listed in the public MCP registry as io.github.turbaba/iconoteka. Search 1300 open-source icons in 7 weights and 2 styles, and get paste-ready SVG. This page covers its npm package (iconoteka-mcp).

Is the Iconoteka MCP server safe to use?

Iconoteka scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 Iconoteka MCP server expose?

Iconoteka exposes 3 tools: search_icons, get_icon, list_categories. Their descriptions and schemas cost roughly 232 tokens of context every time the server is loaded.

Is the Iconoteka MCP server still maintained?

Iconoteka is still listed as active in the MCP registry. We last reached this channel on 25 September 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 Iconoteka MCP server under?

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