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.

OpenFormatDB

NPM · @OPENFORMATDB/MCP

Identify a file, find open tools for its format, convert it locally with WebAssembly.

Available components

+2 this week 91 Trust /100

Last scanned (11 hours ago)

Scores higher than 88% 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 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
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to openformatdb/openformatdb). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-or-later).Pass
  • Actively maintained (last published 27 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1345 tokens (~168/item across 8 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
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 9 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 0
    • Stability: 0.97 → pass security
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 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.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

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 22 Nov 2026 · Analysed npm/@openformatdb/mcp@0.3.0

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 openformatdb/openformatdb
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/openformatdb/openformatdb/.github/workflows/release-mcp.yml@refs/heads/main
Rekor log index 3455913698
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8be62e356dc2488ca7b562cb5f3f3449f2b413701a3f116cb182a7894fab12b357008d82d35aaffdc34e6177d01edc67737c3df874860fa45f1b246a6

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,190 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
claim_format ~256

Say you are reverse engineering or documenting a format, so nobody duplicates the work: adds a claim (who, contact, scope, up to 90 days) to data/formats/<id>.yaml, creating the record if the format is new. Call lookup_format first.

NameTypeReqDescription
agentstring–Agent/tooling used
categorystring–Required only for a new format
contactstringyesHow others reach the claimant: email, GitHub handle, issue URL
daysinteger–Claim duration (default 30, max 90)
extensionsarray–Extensions of a new format, without the dot
force_newboolean–Create a new record even though a similar format exists
idstring–Format id if it exists (from identify_file, lookup_format or search_formats). Otherwise give name + category.
namestring–Format name, for a format not in OpenFormatDB yet
scopestringyesWhat you will document, e.g. "header and index", "full read support"
versionstring––
whostringyesWho is working on it: your human's name or handle

No output schema declared.

No examples provided.

convert_file ~228

Convert a file on this machine to another format with open-source converters compiled to WebAssembly: ImageMagick (images, raw photos), resvg (SVG), FFmpeg (audio, video), Pandoc (documents, markup), 7-Zip (archives), GDAL (geodata), Assimp (3D). Nothing is uploaded. Each engine is downloaded once on first use (2 to 59 MB, pinned versions, SHA-256 checked) into ~/.cache/openformatdb/engines. Call with only `path` to list what the file can become; chains of two engines are planned automatically (svg → png → webp). Writes next to the input unless `output` is given, and never overwrites a file.

NameTypeReqDescription
outputstring–Output file path (default: next to the input, same name, new extension)
pathstringyesFile to convert (absolute, or relative to the server's working directory)
tostring–Target extension: webp, mp3, docx, kml, glb, zip…

No output schema declared.

No examples provided.

find_conversion ~110

How to convert a file from one format to another with open tools: the cheapest chains (lossless first), each step with its tool, command and what is lost. Formats as ids or extensions ("docx", "report.wpd"). Without `to`, lists the direct conversions.

NameTypeReqDescription
fromstringyesSource format id, extension or file name
max_stepsinteger–Longest chain (default 3)
tostring–Target format id, extension or file name

No output schema declared.

No examples provided.

identify_file ~243

Candidate formats for a file, ranked: a signature match beats a MIME type, which beats an extension. Read the bytes yourself and pass them as hex; the file never leaves the machine: magic_hex = the first bytes (`xxd -p -l 1024 file`), tail_hex = the last bytes (`tail -c 512 file | xxd -p`) so end-of-file signatures can be checked, whole_file when magic_hex is the entire file. Full PRONOM signatures and their priorities decide between close formats (PNG 1.0 / 1.2 / APNG). Then call lookup_format on the best candidate.

NameTypeReqDescription
extensionstring–File name or extension, e.g. report.doc or .doc
limitinteger––
magic_hexstring–First bytes of the file as hex, spaces allowed (1024 bytes recommended)
mimestring–MIME type if known, e.g. from `file --mime-type`
tail_hexstring–Last bytes of the file as hex (512 bytes recommended)
whole_fileboolean–magic_hex holds the entire file

No output schema declared.

No examples provided.

list_sources ~24

Sources aggregated in OpenFormatDB, with record counts, licences and snapshot dates.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_format ~130

Full record of a format: identifiers, which software reads or writes it (open source first), grammars, specification, family and versions, live claims, and advice on what to do next. Find it by id, PRONOM PUID, Wikidata QID, or MIME type.

NameTypeReqDescription
idstring–OpenFormatDB id, from identify_file or search_formats
mimestring––
puidstring–PRONOM id, e.g. fmt/13
wikidatastring–Wikidata QID, e.g. Q178051

No output schema declared.

No examples provided.

publish_findings ~118

Merge what you found into data/formats/<id>.yaml: structure, grammars, tools, conversions, specification, identifiers, verification. Status only moves forward. Optionally release your claim. Then open a pull request.

NameTypeReqDescription
allow_downgradeboolean–Allow lowering the status (explain why in the summary or a verification note)
idstringyesFormat id
patchobjectyes–
release_claim_ofstring–Remove the live claims of this claimant now that the work is published

No output schema declared.

No examples provided.

search_formats ~81

Ranked formats matching a name, alias, extension, MIME type, PUID or QID, optionally by category or status.

NameTypeReqDescription
categorystring––
limitinteger––
querystringyes–
statusstring–unknown, in-progress, partial, readable (open code reads it), writable (open code writes it)

No output schema declared.

No examples provided.

Install

How do I install the OpenFormatDB MCP server?

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

# add to Claude Code
claude mcp add org-openformatdb-openformatdb -- npx -y @openformatdb/mcp
Common questions

What is the OpenFormatDB MCP server?

OpenFormatDB is an MCP server listed in the public MCP registry as org.openformatdb/openformatdb. Identify a file, find open tools for its format, convert it locally with WebAssembly. This page covers its npm package (@openformatdb/mcp).

Is the OpenFormatDB MCP server safe to use?

OpenFormatDB scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 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 OpenFormatDB MCP server expose?

OpenFormatDB exposes 8 tools: identify_file, lookup_format, search_formats, find_conversion, convert_file, and 3 more. Their descriptions and schemas cost roughly 1,190 tokens of context every time the server is loaded.

Is the OpenFormatDB MCP server still maintained?

OpenFormatDB is still listed as active in the MCP registry. We last reached this channel on 22 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 OpenFormatDB MCP server under?

OpenFormatDB declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the OpenFormatDB MCP server?

VerifyMCP ran 16 checks on OpenFormatDB, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.