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.

Rounder tools

NPM · @ROUNDERTOOLS/MCP

Local PDF, Office, image, archive and video tools for AI agents. Files never leave your computer.

Available components

+2 this week 70 Trust /100

Last scanned (3 hours ago)

Scores higher than 38% of npm servers

Category Documents and Files

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 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
  • 1 of 12 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 417 tokens (~139/item across 3 items; 3 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 Management0
  • Stability check failed: the tool surface changed between 0.1.0 and 0.3.0: 20 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% of tool parameters carry a description.Partial
  • Structured output schemas are declared (33% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.2.0 → 0.3.0 functional
  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.10 → fail ▼ security
    • Tool coverage: 82% → 43% ▼ functional
    • Tool coverage: 91% → 33% ▼ functional
    • Schema quality: 182 → 139 ▲ functional
    • First check of Schema quality: 100 functional
    • Destructive annotations: 100 → pass functional
    • Package version: 0.1.0 → 0.2.0 functional
  • 1 Nov 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 31 Oct 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 29 Oct 26 68

    First indexed and scored.

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/@roundertools/mcp@0.3.0

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 12 packages
Packages resolved 12
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~286 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
describe-tool ~50

The full options (as JSON Schema), inputs and an example for any Rounder tool, listed or not.

NameTypeReqDescription
toolstringyesA tool slug, like compress-pdf or png-to-jpg

No output schema declared.

No examples provided.

find-tool ~134

Search Rounder's tools by what you want done (e.g. "make a pdf smaller", "heic to jpg"). Returns matching tools, each with the tool to call and example arguments. Covers PDFs (merge, split, compress, protect, unlock, pages, watermark, text, images), images (convert, compress, resize, crop, rotate, EXIF), zip, unzip, file info, and video or audio with ffmpeg (compress, convert, trim, mute, GIF, MP3). Runs locally; files never leave this computer.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

run-tool ~102

Run any Rounder tool by slug, including ones not listed here (see find-tool and describe-tool). Options are checked against that tool's schema. Runs locally; files never leave this computer.

NameTypeReqDescription
inputsarrayyesAbsolute paths of the input files
optionsobject––
outputstring–Absolute path of a folder (or a new file) for the results. Default: next to the input
toolstringyes–
NameTypeReqDescription
dataobject––
outputsarrayyes–
textstring––
warningsarrayyes–
webstring––

No examples provided.

Install

How do I install the Rounder tools MCP server?

Rounder tools runs locally as an npm package, launched with npx -y @roundertools/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 · @roundertools/mcp

# add to Claude Code
claude mcp add adam-sari-roundertools -- npx -y @roundertools/mcp
Common questions

What is the Rounder tools MCP server?

Rounder tools is an MCP server listed in the public MCP registry as io.github.adam-sari/roundertools. Local PDF, Office, image, archive and video tools for AI agents. Files never leave your computer. This page covers its npm package (@roundertools/mcp).

Is the Rounder tools MCP server safe to use?

Rounder tools scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting 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 Rounder tools MCP server expose?

Rounder tools exposes 3 tools: find-tool, describe-tool, run-tool. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.

Is the Rounder tools MCP server still maintained?

Rounder tools 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 Rounder tools MCP server under?

Rounder tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.