io.github.deckflow/deckprobe
NPM · @DECKFLOW/DECKPROBE-MCP · SCANNED SEP 20
Inspect PDF, Office, and iWork documents without rendering: counts, metadata, security signals
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 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
- 0 of 11 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to deckflow/deckprobe-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1349 tokens (~269/item across 5 items; 4 tools + 1 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 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
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.deckflow/deckprobe MCP server?
io.github.deckflow/deckprobe runs locally as an npm package, launched with npx -y @deckflow/deckprobe-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 · @deckflow/deckprobe-mcp
claude mcp add deckflow-deckprobe -- npx -y @deckflow/deckprobe-mcp
{
"mcpServers": {
"deckflow-deckprobe": {
"command": "npx",
"args": [
"-y",
"@deckflow/deckprobe-mcp"
]
}
}
} {
"servers": {
"deckflow-deckprobe": {
"command": "npx",
"args": [
"-y",
"@deckflow/deckprobe-mcp"
]
}
}
} codex mcp add deckflow-deckprobe -- npx -y @deckflow/deckprobe-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"deckflow-deckprobe": {
"type": "local",
"command": [
"npx",
"-y",
"@deckflow/deckprobe-mcp"
],
"enabled": true
}
}
} openclaw mcp add deckflow-deckprobe --command npx --arg -y --arg @deckflow/deckprobe-mcp
mcp_servers:
deckflow-deckprobe:
command: "npx"
args: ["-y", "@deckflow/deckprobe-mcp"] {
"McpServers": {
"deckflow-deckprobe": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@deckflow/deckprobe-mcp"
]
}
}
} assistant mcp add deckflow-deckprobe -t stdio -c npx -a -y @deckflow/deckprobe-mcp
{
"mcpServers": {
"deckflow-deckprobe": {
"command": "npx",
"args": [
"-y",
"@deckflow/deckprobe-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.
- 19 Sept 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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/@deckflow/deckprobe-mcp@0.1.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 | deckflow/deckprobe-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/deckflow/deckprobe-mcp-server/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 2565164267 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3de2a0b2922baa2939ef97a54065db866d1d30ab4761dc12bb566287373fa21a653b3d7f1b5dace19d7cf67c90cd4591aa4029fdd8c78c1cb087d9f88 |
Background: How many MCP packages publish verified provenance →
Dependencies 11 packages
| Packages resolved | 11 |
|---|---|
| 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 →
list_formats List supported formats ~45
List the document formats DeckProbe can inspect: drivers, the extensions each one handles, and where support stops. Call this when you are unsure whether a file type is supported at all.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_targets List targets for a format ~149
List every target a format supports, with its aliases, value type, minimum probe level, cost class, and which @selectors include it. Call this before naming a target you have not already seen — probe rejects an unknown one rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | compact (default): target names, aliases, descriptions, levels, and selector membership. full: the complete report, including each target's JSON Schema fragment and every selector's expanded member l… |
| format | string | yes | A format profile from list_formats, such as "pdf", "docx", "xlsx", "pptx", "doc", "xls", "ppt", "key", "numbers", or "pages". |
No output schema declared.
No examples provided.
probe Probe a document ~416
Read facts about one local PDF, Microsoft Office, or Apple iWork document without opening or rendering it: page, slide, and sheet counts; title, author, and dates; encryption, macro, signature, and active-content signals; structure; embedded assets; and integrity. Handles .pdf, .docx/.xlsx/.pptx, legacy .doc/.xls/.ppt, and modern .key/.numbers/.pages. Start with targets ["@summary"], or ["@security"] to triage an untrusted file. Prefer this over unzipping the document or parsing its bytes by hand. Reports facts ABOUT the document, never its text: it does not extract, render, run macros, follow external references, or open a network connection.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | object | – | Override the level's resource limits. Raise after a BUDGET_EXCEEDED error. |
| level | string | – | Probe budget and eligible paths. header: identity only. metadata (default). deep: higher-cost paths, needed only when a target's min_level says so. |
| min_confidence | string | – | Weakest evidence a path may offer. Default high; lower it to accept an approximation. |
| path | string | yes | Path to the document. The filename extension selects the format driver, and the container is then verified against it. |
| target_confidence | object | – | Per-target override, e.g. {"slide_count": "exact"} to force the authoritative path. |
| targets | array | – | Short names (slide_count), canonical names (powerpoint.slide_count), or presets: @header, @summary, @security, @structure, @assets, @quality, @format, @all. Defaults to the driver's own set. Call lis… |
| view | string | – | report: full evidence — value, confidence, path, and cost per target. values: a compact target-to-value map. |
| Name | Type | Req | Description |
|---|---|---|---|
| schema_version | number | – | – |
| status | string | – | – |
No examples provided.
probe_batch Probe several documents ~347
Probe many local documents in one call — inventory a folder, triage a batch of uploads, or compare a set of files. One engine process handles the whole batch, so this is much cheaper than calling probe once per file. Takes literal paths; expand any glob yourself first. Returns one entry per path, in the order given, each carrying that file's report or its own error envelope. A file that fails does not affect the others. Defaults to the compact "values" view because inventory rarely needs per-target evidence; pass view: "report" when it does.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | object | – | Override the level's resource limits. Raise after a BUDGET_EXCEEDED error. |
| level | string | – | Probe budget and eligible paths. header: identity only. metadata (default). deep: higher-cost paths, needed only when a target's min_level says so. |
| min_confidence | string | – | Weakest evidence a path may offer. Default high; lower it to accept an approximation. |
| paths | array | yes | Document paths, at most 64 per call. Literal paths only. |
| targets | array | – | Short names (slide_count), canonical names (powerpoint.slide_count), or presets: @header, @summary, @security, @structure, @assets, @quality, @format, @all. Defaults to the driver's own set. Call lis… |
| view | string | – | report: full evidence — value, confidence, path, and cost per target. values: a compact target-to-value map. |
| Name | Type | Req | Description |
|---|---|---|---|
| reports | array | yes | One entry per requested path, in order. A per-file failure is confined to it. |
No examples provided.
What is the io.github.deckflow/deckprobe MCP server?
io.github.deckflow/deckprobe is an MCP server listed in the public MCP registry as io.github.deckflow/deckprobe. Inspect PDF, Office, and iWork documents without rendering: counts, metadata, security signals. This page covers its npm package (@deckflow/deckprobe-mcp).
Is the io.github.deckflow/deckprobe MCP server safe to use?
io.github.deckflow/deckprobe scores 95 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. 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 io.github.deckflow/deckprobe MCP server expose?
io.github.deckflow/deckprobe exposes 4 tools: probe, probe_batch, list_formats, list_targets. Their descriptions and schemas cost roughly 957 tokens of context every time the server is loaded.
Is the io.github.deckflow/deckprobe MCP server still maintained?
io.github.deckflow/deckprobe 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.deckflow/deckprobe MCP server under?
io.github.deckflow/deckprobe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.