io.github.LassiB999/tooldash-mcp
NPM · TOOLDASH-MCP · SCANNED SEP 21
Offline PDF and text tools: merge, extract pages, inspect, clean text. No upload, no API key.
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
- 3 of 8 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 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 572 tokens (~143/item across 4 items; 4 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 Management80
- Stability observed for 24 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 (100% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
How do I install the io.github.LassiB999/tooldash-mcp server?
io.github.LassiB999/tooldash-mcp runs locally as an npm package, launched with npx -y tooldash-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 · tooldash-mcp
claude mcp add lassib999-tooldash-mcp -- npx -y tooldash-mcp
{
"mcpServers": {
"lassib999-tooldash-mcp": {
"command": "npx",
"args": [
"-y",
"tooldash-mcp"
]
}
}
} {
"servers": {
"lassib999-tooldash-mcp": {
"command": "npx",
"args": [
"-y",
"tooldash-mcp"
]
}
}
} codex mcp add lassib999-tooldash-mcp -- npx -y tooldash-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lassib999-tooldash-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tooldash-mcp"
],
"enabled": true
}
}
} openclaw mcp add lassib999-tooldash-mcp --command npx --arg -y --arg tooldash-mcp
mcp_servers:
lassib999-tooldash-mcp:
command: "npx"
args: ["-y", "tooldash-mcp"] {
"McpServers": {
"lassib999-tooldash-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tooldash-mcp"
]
}
}
} assistant mcp add lassib999-tooldash-mcp -t stdio -c npx -a -y tooldash-mcp
{
"mcpServers": {
"lassib999-tooldash-mcp": {
"command": "npx",
"args": [
"-y",
"tooldash-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.
- 20 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.
- 18 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.
- 16 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.
- 14 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.
- 12 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.
- 10 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.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
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 21 Sept 2026 · Analysed npm/tooldash-mcp@1.0.2
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 8 packages
| Packages resolved | 8 |
|---|---|
| Stale | 3 |
| 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 →
clean_text Clean and normalize text ~153
Normalize messy text: collapse repeated spaces, strip trailing whitespace and invisible characters, unify line endings, and optionally collapse blank lines, convert smart punctuation to ASCII, or remove URLs. Runs entirely offline — nothing is uploaded and no network call is made.
| Name | Type | Req | Description |
|---|---|---|---|
| collapseBlankLines | boolean | – | Collapse runs of two or more blank lines into a single blank line. |
| normalizeQuotes | boolean | – | Replace curly quotes, en/em dashes and ellipsis characters with their ASCII equivalents. |
| removeUrls | boolean | – | Strip every http/https URL from the text. Note: this removes ALL URLs — the server is offline and cannot tell a working link from a dead one. |
| text | string | yes | The text to clean. |
| Name | Type | Req | Description |
|---|---|---|---|
| after | object | yes | – |
| before | object | yes | – |
| changed | boolean | yes | False when the input was already clean. |
| removedUrls | array | yes | URLs stripped, when removeUrls was set. |
| text | string | yes | The cleaned text. |
No examples provided.
extract_pdf_pages Extract PDF pages ~175
Write a selection of pages from a local PDF into a new file, leaving the original untouched. Pages are 1-based and may be given as a list and ranges, e.g. "1-3,7,10-12". Order is preserved, so "3,1" produces a two-page file in that order.
| Name | Type | Req | Description |
|---|---|---|---|
| inputPath | string | yes | The PDF to take pages from. Absolute, or relative to the client's working directory. |
| outputPath | string | yes | Where to write the extracted pages. Absolute, or relative to the client's working directory. |
| overwrite | boolean | – | Replace outputPath if a file is already there. |
| pages | string | yes | 1-based page selection, e.g. "1-3,7,10-12". Ranges may descend ("5-1"). |
| Name | Type | Req | Description |
|---|---|---|---|
| outputPath | string | yes | – |
| pageCount | number | yes | – |
| sizeBytes | number | yes | – |
| sourcePages | array | yes | The 1-based source pages, in output order. |
No examples provided.
merge_pdfs Merge PDFs ~117
Combine two or more local PDFs into a single file, in the order given. Runs entirely on this machine with pdf-lib — nothing is uploaded and no URL is fetched. Refuses to overwrite an existing output unless overwrite is true.
| Name | Type | Req | Description |
|---|---|---|---|
| inputPaths | array | yes | The PDFs to merge, in the order they should appear in the result. |
| outputPath | string | yes | Where to write the merged PDF. Absolute, or relative to the client's working directory. |
| overwrite | boolean | – | Replace outputPath if a file is already there. |
| Name | Type | Req | Description |
|---|---|---|---|
| outputPath | string | yes | – |
| pageCount | number | yes | – |
| sizeBytes | number | yes | – |
| sources | array | yes | – |
No examples provided.
pdf_info Inspect a PDF ~69
Report the page count, per-page dimensions and document metadata of a local PDF. Read-only: the file is never modified. Call this before merging or extracting so page numbers are known to be valid.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The PDF to inspect. Absolute, or relative to the client's working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string|null | yes | – |
| name | string | yes | – |
| pageCount | number | yes | – |
| pages | array | yes | – |
| path | string | yes | – |
| sizeBytes | number | yes | – |
| title | string|null | yes | – |
No examples provided.
What is the io.github.LassiB999/tooldash-mcp server?
io.github.LassiB999/tooldash-mcp is listed in the public MCP registry as io.github.LassiB999/tooldash-mcp. Offline PDF and text tools: merge, extract pages, inspect, clean text. No upload, no API key. This page covers its npm package (tooldash-mcp).
Is the io.github.LassiB999/tooldash-mcp server safe to use?
io.github.LassiB999/tooldash-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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.LassiB999/tooldash-mcp server expose?
io.github.LassiB999/tooldash-mcp exposes 4 tools: pdf_info, merge_pdfs, extract_pdf_pages, clean_text. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.
Is the io.github.LassiB999/tooldash-mcp server still maintained?
io.github.LassiB999/tooldash-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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.LassiB999/tooldash-mcp server under?
io.github.LassiB999/tooldash-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.