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.

Mic

NPM · @PIPEWORX/MCP-MIC · 2 COMPONENTS

MIC — ISO 10383 Market Identifier Code decoder (fleet #3261)

79 Trust /100

Last scanned (6 hours ago)

Scores higher than 62% of npm servers

Category Finance and Payments

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 & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-mic). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 448 tokens (~224/item across 2 items; 2 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 2 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

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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 64

    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/@pipeworx/mcp-mic@0.2.1

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 pipeworx-io/mcp-mic
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-mic/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3655441952
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a422ec35a2c21e76ccfade64df02a7af8c214718c3f2d8e222504dc93765824b46f6ad33357d3aed631abcddcaed513d6952c7a9ca9e66034e589213c

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 · 2 exposed · ~397 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
decode_mic ~178

Decode an ISO 10383 Market Identifier Code (MIC) — the 4-character venue code openfigi returns as `exchCode` on an exchange listing, and the code most market-data feeds use the same way — to the trading venue's own name, legal operator, country, city, website and registry status. Reports whether the code is an OPERATING MIC (the operator as a whole, e.g. "XNYS") or a SEGMENT MIC (one specific market under an operator, e.g. "ARCX" under "XNYS"); an operating MIC also carries segment_count — call search_mics with operating_mic to list them.

NameTypeReqDescription
codestringyes4-character ISO 10383 MIC, e.g. "XNYS" (NYSE) or "XLON" (London Stock Exchange).

No output schema declared.

No examples provided.

search_mics ~219

Filter the ISO 10383 Market Identifier Code registry by country, operating MIC, status and/or a name fragment. Returns aggregate counts first (total matched, by_status, by_country) and a page of rows after. Use operating_mic to list every segment market under one venue operator (e.g. every segment under "XNYS").

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country code of the venue, e.g. "US", "GB", "JP".
limitnumber–Rows per page, 1-500 (default 50).
name_containsstring–Case-insensitive fragment of the market name, legal entity name or acronym, e.g. "nasdaq".
offsetnumber–Rows to skip for paging (default 0).
operating_micstring–List every market (segment or operating) under this operating MIC, e.g. "XNYS" to list NYSE's own segments.
statusstring–Registry status.

No output schema declared.

No examples provided.

Install

How do I install the Mic MCP server?

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

npm · @pipeworx/mcp-mic

# add to Claude Code
claude mcp add pipeworx-io-mic -- npx -y @pipeworx/mcp-mic
Common questions

What is the Mic MCP server?

Mic is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mic. MIC, ISO 10383 Market Identifier Code decoder (fleet #3261). This page covers its npm package (@pipeworx/mcp-mic).

Is the Mic MCP server safe to use?

Mic scores 79 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 Mic MCP server expose?

Mic exposes 2 tools: decode_mic, search_mics. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.

Is the Mic MCP server still maintained?

Mic 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 Mic MCP server under?

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