# OpenFormatDB (npm · @openformatdb/mcp)

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

- Trust score: 91/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- npm · `@openformatdb/mcp`: 91/100 (this document), [markdown](https://verifymcp.io/servers/org-openformatdb-openformatdb/openformatdb-mcp.md), [page](https://verifymcp.io/servers/org-openformatdb-openformatdb/openformatdb-mcp)

## Channel facts

- Registry: `npm`
- Package: `@openformatdb/mcp`
- Version: `0.3.0`
- 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-11-22.

- **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.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to openformatdb/openformatdb).
  - Clear OSI-approved license (AGPL-3.0-or-later).
  - Actively maintained (last published 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **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 9 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 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.

### Claude

```bash
claude mcp add org-openformatdb-openformatdb -- npx -y @openformatdb/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "org-openformatdb-openformatdb": {
      "command": "npx",
      "args": [
        "-y",
        "@openformatdb/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-openformatdb-openformatdb": {
      "command": "npx",
      "args": [
        "-y",
        "@openformatdb/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add org-openformatdb-openformatdb -- npx -y @openformatdb/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add org-openformatdb-openformatdb --command npx --arg -y --arg @openformatdb/mcp
```

### Hermes

```yaml
mcp_servers:
  org-openformatdb-openformatdb:
    command: "npx"
    args: ["-y", "@openformatdb/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "org-openformatdb-openformatdb": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@openformatdb/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-openformatdb-openformatdb -t stdio -c npx -a -y @openformatdb/mcp
```

### Other

```json
{
  "mcpServers": {
    "org-openformatdb-openformatdb": {
      "command": "npx",
      "args": [
        "-y",
        "@openformatdb/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-11-20 (score 91, 0)

- [security] Stability: 0.97 → pass

### 2026-11-19 (score 91, +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.

### 2026-11-17 (score 90, +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.

### 2026-11-15 (score 89, +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.

### 2026-11-13 (score 88, +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-11-10 (score 87, +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.

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

### 2026-11-06 (score 85, +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.

## MCP tools (8)

### `identify_file` (~243 tokens)

Identify a file

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.

Input parameters:

- `extension` (string): File name or extension, e.g. report.doc or .doc
- `limit` (integer)
- `magic_hex` (string): First bytes of the file as hex, spaces allowed (1024 bytes recommended)
- `mime` (string): MIME type if known, e.g. from `file --mime-type`
- `tail_hex` (string): Last bytes of the file as hex (512 bytes recommended)
- `whole_file` (boolean): magic_hex holds the entire file

### `lookup_format` (~130 tokens)

Look up a format

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.

Input parameters:

- `id` (string): OpenFormatDB id, from identify_file or search_formats
- `mime` (string)
- `puid` (string): PRONOM id, e.g. fmt/13
- `wikidata` (string): Wikidata QID, e.g. Q178051

### `search_formats` (~81 tokens)

Search formats

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

Input parameters:

- `category` (string)
- `limit` (integer)
- `query` (string, required)
- `status` (string): unknown, in-progress, partial, readable (open code reads it), writable (open code writes it)

### `find_conversion` (~110 tokens)

Find a conversion

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.

Input parameters:

- `from` (string, required): Source format id, extension or file name
- `max_steps` (integer): Longest chain (default 3)
- `to` (string): Target format id, extension or file name

### `convert_file` (~228 tokens)

Convert a file locally

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.

Input parameters:

- `output` (string): Output file path (default: next to the input, same name, new extension)
- `path` (string, required): File to convert (absolute, or relative to the server's working directory)
- `to` (string): Target extension: webp, mp3, docx, kml, glb, zip…

### `list_sources` (~24 tokens)

List sources

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

### `claim_format` (~256 tokens)

Claim a format

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.

Input parameters:

- `agent` (string): Agent/tooling used
- `category` (string): Required only for a new format
- `contact` (string, required): How others reach the claimant: email, GitHub handle, issue URL
- `days` (integer): Claim duration (default 30, max 90)
- `extensions` (array): Extensions of a new format, without the dot
- `force_new` (boolean): Create a new record even though a similar format exists
- `id` (string): Format id if it exists (from identify_file, lookup_format or search_formats). Otherwise give name + category.
- `name` (string): Format name, for a format not in OpenFormatDB yet
- `scope` (string, required): What you will document, e.g. "header and index", "full read support"
- `version` (string)
- `who` (string, required): Who is working on it: your human's name or handle

### `publish_findings` (~118 tokens)

Publish findings

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.

Input parameters:

- `allow_downgrade` (boolean): Allow lowering the status (explain why in the summary or a verification note)
- `id` (string, required): Format id
- `patch` (object, required)
- `release_claim_of` (string): Remove the live claims of this claimant now that the work is published

## Diagnostics

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

## Score history

- 2026-11-22: 91
- 2026-11-21: 91
- 2026-11-20: 91
- 2026-11-19: 91
- 2026-11-18: 90
- 2026-11-17: 90
- 2026-11-16: 89
- 2026-11-15: 89
- 2026-11-14: 88
- 2026-11-13: 88
- 2026-11-12: 87
- 2026-11-11: 87
- 2026-11-10: 87
- 2026-11-09: 86
- 2026-11-08: 86
- 2026-11-07: 85
- 2026-11-06: 85
- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 67

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

## Links

- npm package: https://www.npmjs.com/package/@openformatdb/mcp
- Socket report: https://socket.dev/npm/package/@openformatdb/mcp
- Repository: https://github.com/openformatdb/openformatdb
- Website: https://openformatdb.org/agents/
- Changelog RSS feed: https://verifymcp.io/servers/org-openformatdb-openformatdb/openformatdb-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-openformatdb-openformatdb/openformatdb-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-openformatdb-openformatdb/openformatdb-mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-openformatdb-openformatdb/openformatdb-mcp
