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.

io.github.Iconmind/iconmind

NPM · @ICONMIND/MCP

Search IconMind's MIT icons by name, tag or category; get real slugs and import lines. Offline.

Available components

68 Trust /100

Last scanned (7 hours ago)

Scores higher than 38% 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 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
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 478 tokens (~18/item across 26 items; 4 tools + 22 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 21 Oct 26 53

    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 23 Oct 2026 · Analysed npm/@iconmind/mcp@0.8.3

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 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~227 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 ~38

Fetch one icon by its exact slug: metadata plus paste-ready React and HTML.

NameTypeReqDescription
sizeinteger––
slugstringyes–

No output schema declared.

No examples provided.

get_icon_code ~53

Generate one combined import plus usage for several icons at once. Prefer this over repeated get_icon calls when building a component that needs more than one.

NameTypeReqDescription
frameworkstring––
slugsarrayyes–

No output schema declared.

No examples provided.

list_category ~51

List icons in a category, optionally filtered by subcategory. With no arguments, returns the categories themselves.

NameTypeReqDescription
categorystring––
limitinteger––
subcategorystring––

No output schema declared.

No examples provided.

search_icon ~85

Search IconMind icons by keyword, concept, or description. Use this before writing any UI code that needs an icon, so you pick one that actually exists instead of guessing a name.

NameTypeReqDescription
categorystring–Restrict to one domain
limitinteger––
querystringyesKeyword or concept, e.g. 'vector database', 'agent memory'

No output schema declared.

No examples provided.

Install

How do I install the io.github.Iconmind/iconmind MCP server?

io.github.Iconmind/iconmind runs locally as an npm package, launched with npx -y @iconmind/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 · @iconmind/mcp

# add to Claude Code
claude mcp add iconmind-iconmind -- npx -y @iconmind/mcp
Common questions

What is the io.github.Iconmind/iconmind MCP server?

io.github.Iconmind/iconmind is an MCP server listed in the public MCP registry as io.github.Iconmind/iconmind. Search IconMind's MIT icons by name, tag or category; get real slugs and import lines. Offline. This page covers its npm package (@iconmind/mcp).

Is the io.github.Iconmind/iconmind MCP server safe to use?

io.github.Iconmind/iconmind scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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 io.github.Iconmind/iconmind MCP server expose?

io.github.Iconmind/iconmind exposes 4 tools: search_icon, get_icon, list_category, get_icon_code. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.

Is the io.github.Iconmind/iconmind MCP server still maintained?

io.github.Iconmind/iconmind is still listed as active in the MCP registry. We last reached this channel on 23 October 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 io.github.Iconmind/iconmind MCP server under?

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