# io.github.LassiB999/tooldash-mcp (npm · tooldash-mcp)

Offline PDF and text tools: merge, extract pages, inspect, clean text. No upload, no API key.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `tooldash-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/lassib999-tooldash-mcp/tooldash-mcp.md), [page](https://verifymcp.io/servers/lassib999-tooldash-mcp/tooldash-mcp)

## Channel facts

- Registry: `npm`
- Package: `tooldash-mcp`
- Version: `1.0.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 3 of 8 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 23 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add lassib999-tooldash-mcp -- npx -y tooldash-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "lassib999-tooldash-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tooldash-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lassib999-tooldash-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tooldash-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lassib999-tooldash-mcp -- npx -y tooldash-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lassib999-tooldash-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tooldash-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lassib999-tooldash-mcp --command npx --arg -y --arg tooldash-mcp
```

### Hermes

```yaml
mcp_servers:
  lassib999-tooldash-mcp:
    command: "npx"
    args: ["-y", "tooldash-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "lassib999-tooldash-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tooldash-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lassib999-tooldash-mcp -t stdio -c npx -a -y tooldash-mcp
```

### Other

```json
{
  "mcpServers": {
    "lassib999-tooldash-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tooldash-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 82, +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.

### 2026-09-18 (score 81, +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.

### 2026-09-16 (score 80, +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.

### 2026-09-14 (score 79, +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.

### 2026-09-12 (score 78, +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.

### 2026-09-10 (score 77, +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.

### 2026-09-08 (score 76, +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.

### 2026-09-05 (score 75, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (4)

### `pdf_info` (~69 tokens)

Inspect a PDF

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.

Input parameters:

- `path` (string, required): The PDF to inspect. Absolute, or relative to the client's working directory.

Output parameters:

- `author` (string|null)
- `name` (string)
- `pageCount` (number)
- `pages` (array)
- `path` (string)
- `sizeBytes` (number)
- `title` (string|null)

### `merge_pdfs` (~117 tokens)

Merge PDFs

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.

Input parameters:

- `inputPaths` (array, required): The PDFs to merge, in the order they should appear in the result.
- `outputPath` (string, required): 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.

Output parameters:

- `outputPath` (string)
- `pageCount` (number)
- `sizeBytes` (number)
- `sources` (array)

### `extract_pdf_pages` (~175 tokens)

Extract PDF pages

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.

Input parameters:

- `inputPath` (string, required): The PDF to take pages from. Absolute, or relative to the client's working directory.
- `outputPath` (string, required): 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, required): 1-based page selection, e.g. "1-3,7,10-12". Ranges may descend ("5-1").

Output parameters:

- `outputPath` (string)
- `pageCount` (number)
- `sizeBytes` (number)
- `sourcePages` (array): The 1-based source pages, in output order.

### `clean_text` (~153 tokens)

Clean and normalize text

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.

Input parameters:

- `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, required): The text to clean.

Output parameters:

- `after` (object)
- `before` (object)
- `changed` (boolean): False when the input was already clean.
- `removedUrls` (array): URLs stripped, when removeUrls was set.
- `text` (string): The cleaned text.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/lassib999-tooldash-mcp/tooldash-mcp#diagnostics

## Score history

- 2026-09-21: 82
- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 75
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 71

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/tooldash-mcp
- Socket report: https://socket.dev/npm/package/tooldash-mcp
- Repository: https://github.com/LassiB999/tooldash-mcp
- Changelog RSS feed: https://verifymcp.io/servers/lassib999-tooldash-mcp/tooldash-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lassib999-tooldash-mcp/tooldash-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lassib999-tooldash-mcp/tooldash-mcp