io.github.aapd-studio/omnideck
NPM · OMNIDECK-MCP · SCANNED SEP 20
Local privacy-first tools: redact secrets, decode JWTs, compare LLM costs. No network calls.
Available components
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 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 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 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
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.
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
claude mcp add aapd-studio-omnideck -- npx -y omnideck-mcp
{
"mcpServers": {
"aapd-studio-omnideck": {
"command": "npx",
"args": [
"-y",
"omnideck-mcp"
]
}
}
} {
"servers": {
"aapd-studio-omnideck": {
"command": "npx",
"args": [
"-y",
"omnideck-mcp"
]
}
}
} codex mcp add aapd-studio-omnideck -- npx -y omnideck-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aapd-studio-omnideck": {
"type": "local",
"command": [
"npx",
"-y",
"omnideck-mcp"
],
"enabled": true
}
}
} openclaw mcp add aapd-studio-omnideck --command npx --arg -y --arg omnideck-mcp
mcp_servers:
aapd-studio-omnideck:
command: "npx"
args: ["-y", "omnideck-mcp"] {
"McpServers": {
"aapd-studio-omnideck": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"omnideck-mcp"
]
}
}
} assistant mcp add aapd-studio-omnideck -t stdio -c npx -a -y omnideck-mcp
{
"mcpServers": {
"aapd-studio-omnideck": {
"command": "npx",
"args": [
"-y",
"omnideck-mcp"
]
}
}
} 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.
- 16 Sept 26 71
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 20 Sept 2026 · Analysed npm/omnideck-mcp@1.0.1
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 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
check_output_fidelity Check AI output against its source ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_output | string | yes | The AI-generated text to check. |
| original | string | yes | The source text the output was generated from. |
No output schema declared.
No examples provided.
decode_jwt Decode a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The JWT, with or without a 'Bearer ' prefix. |
No output schema declared.
No examples provided.
estimate_llm_cost Estimate and compare 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.
| Name | Type | Req | Description |
|---|---|---|---|
| input_tokens | integer | – | Exact input token count, if you already have it. Overrides `text`. |
| output_tokens | integer | – | Expected output tokens. Defaults to 500. |
| text | string | – | The prompt text. Its tokens are counted for you. |
No output schema declared.
No examples provided.
hash_text Hash text locally ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Digest algorithm. |
| text | string | yes | The string to hash. |
No output schema declared.
No examples provided.
redact_sensitive_data 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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Which categories to mask. Defaults to all: emails, api_keys, credit_cards, iban, ip_addresses, phone_numbers. |
| text | string | yes | The text to scrub. |
No output schema declared.
No examples provided.
split_for_context Split text for a context window ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | Approximate token budget per chunk. Defaults to 8000. |
| text | string | yes | The document to split. |
No output schema declared.
No examples provided.
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 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 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 20 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 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.