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.aapd-studio/omnideck

NPM · OMNIDECK-MCP

Local privacy-first tools: redact secrets, decode JWTs, compare LLM costs. No network calls.

Available components

−1 this week 79 Trust /100

Last scanned (6 minutes ago)

Scores higher than 62% of npm servers

Category Security

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 571 tokens (~95/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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 +1

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

  • 3 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
    • Package version: 1.0.3 → 1.0.4 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 0
    • Package version: 1.0.3 → 1.0.4 functional
  • 17 Oct 26 0
    • Package version: 1.0.3 → 1.0.4 functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
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/omnideck-mcp@1.0.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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 94 packages
Packages resolved 94
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~571 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
check_output_fidelity ~102

Flag names, numbers and dates that appear in an AI-generated summary but NOT in the source text it was based on — the usual shape of a hallucination. This is a lexical heuristic, not a fact-checker: it catches invented specifics, not wrong reasoning. Use it to decide what to verify by hand.

NameTypeReqDescription
ai_outputstringyesThe AI-generated text to check.
originalstringyesThe source text the output was generated from.

No output schema declared.

No examples provided.

decode_jwt ~85

Decode the header and payload of a JSON Web Token and report its expiry status. Does NOT verify the signature (no secret is involved, and none should be pasted anywhere). Use this instead of an online JWT decoder — a token is a live credential and should never be pasted into a website.

NameTypeReqDescription
tokenstringyesThe JWT, with or without a 'Bearer ' prefix.

No output schema declared.

No examples provided.

estimate_llm_cost ~112

Compare what one request would cost across GPT, Claude and Gemini models, sorted cheapest first. Pass the prompt text, or pass input_tokens directly if you already know the count. Useful for picking a model before running a large batch job.

NameTypeReqDescription
input_tokensinteger–Exact input token count, if you already have it. Overrides `text`.
output_tokensinteger–Expected output tokens. Defaults to 500.
textstring–The prompt text. Its tokens are counted for you.

No output schema declared.

No examples provided.

hash_text ~71

Compute an MD5, SHA-1, SHA-256 or SHA-512 digest of a string, locally. Use instead of an online hash generator when the input is a password, secret or any private value.

NameTypeReqDescription
algorithmstring–Digest algorithm.
textstringyesThe string to hash.

No output schema declared.

No examples provided.

redact_sensitive_data ~115

Mask emails, API keys, credit cards, IBANs, IP addresses and phone numbers in a block of text. Use this BEFORE sending user-supplied text, logs, config files or pasted documents to any external API, or before quoting them back in a shared transcript. Runs entirely locally — nothing is transmitted.

NameTypeReqDescription
categoriesarray–Which categories to mask. Defaults to all: emails, api_keys, credit_cards, iban, ip_addresses, phone_numbers.
textstringyesThe text to scrub.

No output schema declared.

No examples provided.

split_for_context ~86

Break a long document into chunks that fit a target context window, cutting on paragraph boundaries (falling back to sentence boundaries) so no chunk ends mid-thought. Use when a file is too large to process in one pass.

NameTypeReqDescription
max_tokensinteger–Approximate token budget per chunk. Defaults to 8000.
textstringyesThe document to split.

No output schema declared.

No examples provided.

Install

How do I install the io.github.aapd-studio/omnideck MCP server?

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

# add to Claude Code
claude mcp add aapd-studio-omnideck -- npx -y omnideck-mcp
Common questions

What is the io.github.aapd-studio/omnideck MCP server?

io.github.aapd-studio/omnideck is an MCP server listed in the public MCP registry as io.github.aapd-studio/omnideck. Local privacy-first tools: redact secrets, decode JWTs, compare LLM costs. No network calls. This page covers its npm package (omnideck-mcp).

Is the io.github.aapd-studio/omnideck MCP server safe to use?

io.github.aapd-studio/omnideck scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 io.github.aapd-studio/omnideck MCP server expose?

io.github.aapd-studio/omnideck exposes 6 tools: redact_sensitive_data, decode_jwt, estimate_llm_cost, split_for_context, check_output_fidelity, hash_text. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.

Is the io.github.aapd-studio/omnideck MCP server still maintained?

io.github.aapd-studio/omnideck 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 io.github.aapd-studio/omnideck MCP server under?

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