mcp-conform
An eslint for your MCP server. It's a deterministic, author-side conformance and safety linter you run before publishing a Model Context Protocol server to npm, PyPI, or the official MCP registry.
Alimenter votre agent
La commande propre à l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
npx -y @fernforge/[email protected]Claude Code n'a pas de lien d'installation pour une commande locale. Copiez la commande ci-dessous et exécutez-la dans un terminal.
claude mcp add fernforge-mcp-conform -- npx -y @fernforge/mcp-conform@0.2.0À exécuter dans un terminal.
{ "mcpServers": { "fernforge-mcp-conform": { "command": "npx", "args": [ "-y", "@fernforge/[email protected]" ] } }}claude_desktop_config.json
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
An eslint for your MCP server. It's a deterministic, author-side conformance and safety linter you run before publishing a Model Context Protocol server to npm, PyPI, or the official MCP registry.
Author-side conformance, safety & spec-migration linter for MCP (Model Context Protocol) servers — eslint for your MCP server. Checks tool annotations, schema hygiene, tool-poisoning/injection patterns, registry/distribution metadata, and scans your sourc
It catches the things that get servers bounced from app directories or make agents call your tools wrong: missing tool annotations, thin or ambiguous schemas, tool-poisoning patterns in descriptions, and incomplete registry metadata. Every issue comes with a one-line fix.
npx @fernforge/mcp-conform --cmd "node dist/index.js"
mcp-conform — 7 tool(s) checked
delete_record
✖ error ann/missing-destructive-hint Tool "delete_record" may modify state but does not set destructiveHint.
fix: Set annotations.destructiveHint (true for irreversible ops like delete).
✖ error safety/injection-phrase Tool description contains an injection-style phrase (instruction override).
fix: Remove instruction-like text; describe behavior, don't issue commands to the agent.
1 error · 4 warning · 5 info
Conformance score: 76/100 FAIL
No LLM key, no network, fully deterministic. It's a linter, not a model, so it's safe to run in CI, free to run a thousand times a day, and its verdict never drifts.
The 2026-07-28 MCP spec is the largest revision since launch, and it's not backward compatible. Sessions are gone at the protocol layer (Mcp-Session-Id removed, SEP-2567), the initialize/initialized handshake is removed (SEP-2575), error code -32002 becomes -32602, two new routing headers (Mcp-Method, Mcp-Name) are required, and roots/sampling/logging are deprecated. It's all in the official release candidate. What that post doesn't give you is a tool that reads your code and tells you which lines break.
The spec-migrate rule pack does that. It scans your TypeScript/JavaScript/Python source for the removed and changed APIs and reports each hit with file:line and a fix:
npx @fernforge/mcp-conform --ruleset spec-migrate --project .
server.ts:18
✖ error migrate/session-id-header Mcp-Session-Id is removed (SEP-2567). The 2026-07-28 transport is stateless; this header no longer exists.
fix: Read protocol version, client info and capabilities from params._meta on each request instead of a per-session store.
server.ts:21
✖ error migrate/error-code-32002 JSON-RPC error code -32002 is reassigned to -32602 (Invalid Params).
fix: Change -32002 to -32602.
Hard breaks (sessions, handshake, error code) are errors; the deprecations on the 12-month runway (roots/sampling/logging, Tasks-to-extension) are warnings, so CI fails on what actually breaks on day one and nudges you on the rest. Run --ruleset all to combine it with the standing conformance lint.
Doing the migration by hand? MIGRATION.md is the line-by-line: each break with before/after code, the SEP behind it, grep commands to find every occurrence, and a checklist.
It lints what actually ships. Point it at your server's launch command and it starts the server over stdio, calls tools/list, and inspects the real schemas your users will receive, not a guess from your source.
A drop-in GitHub Action scores every PR and writes a job summary.
The MCP ecosystem is shipping tens of thousands of servers, and the app directories have gotten strict about what they accept.
Bad tool annotations are the top cause of rejection from the ChatGPT and Claude app directories. The spec says a client must assume the worst case (destructive, open-world) when a hint is missing, so if you don't set readOnlyHint / destructiveHint / openWorldHint / title, clients treat your safe read tool as dangerous.
Tool descriptions are an injection surface. They're injected straight into the agent's context, so an "ignore previous instructions" line or an invisible Unicode payload in a description is a real tool-poisoning vector.
The official registry now does namespace-verified publishing. Reverse-DNS names, a server.json manifest, and clean package metadata are part of being publishable and discoverable.
The community is drafting a pre-publish conformance checklist (modelcontextprotocol Discussion #2682). mcp-conform automates it.
Existing MCP security tools are consumer/runtime-side: they scan servers you're about to install. mcp-conform works the other way. It makes your server conformant before anyone installs it.
Run it with npx, no install needed:
npx @fernforge/mcp-conform --cmd "node dist/index.js"
To pin it in CI or as a dev dependency:
npm install --save-dev @fernforge/mcp-conform
Requires Node ≥ 18. The MCP SDK is an optional peer dependency, only needed for live --cmd introspection (most projects already have it).
mcp-conform always lints your project metadata (package.json, server.json) and takes the tools to lint from one of three sources:
mcp-conform --cmd "node dist/index.js"
mcp-conform --cmd "python -m my_server"
mcp-conform --cmd "uvx my-mcp-server"
It launches the server over stdio, initializes a client, and lints the real tools/list output plus capability/transport hygiene.
mcp-conform --manifest tools.json
Where tools.json is either a tools/list result ({ "tools": [...] }) or a bare array of tool definitions. Handy for Python/Go servers or for snapshotting in tests.
mcp-conform # checks package.json + server.json in the current dir
mcp-conform --cmd "node dist/index.js" --json # machine-readable
mcp-conform --cmd "node dist/index.js" --markdown --out report.md
mcp-conform --cmd "node dist/index.js" --min-score 80 # fail under 80
mcp-conform --cmd "node dist/index.js" --max-warnings 0 # fail on any warning
mcp-conform exits non-zero when there's any error-severity finding, so it fails CI by default. Tighten the gate with --min-score and --max-warnings.
Add .github/workflows/mcp-conform.yml to your server repo:
name: MCP Conformance
on: [pull_request, push]
jobs:
conform:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: 20 }
- run: npm ci && npm run build
- uses: fernforge/[email protected]
with:
cmd: "node dist/index.js"
min-score: "80"
It writes a Markdown report to the job summary and fails the check when the score drops below your threshold.
Every finding carries a rule id, a severity (error / warning / info), and a concrete fix. The conformance score (0–100) is a single deterministic number you can track over time.
import { lint, introspect, loadProjectMetadata } from "mcp-conform";
const live = await introspect({ command: "node", args: ["dist/index.js"] });
const meta = await loadProjectMetadata(process.cwd());
const result = lint({ ...live, ...meta });
console.log(result.score, result.pass);
for (const f of result.findings) console.log(f.severity, f.rule, f.message);
--fix for the mechanical annotation/metadata gapsmcpconform.json) to set severities and disable rulesmcpconform-config-recommended ruleset that tracks the community conformance checklist as it finalizesIssues and rule suggestions welcome — the rule set is meant to track the standard as it forms.
MIT © fernforge
Author-side conformance, safety & spec-migration linter for MCP (Model Context Protocol) servers — eslint for your MCP server. Checks tool annotations, schema hygiene, tool-poisoning/injection pattern
{ "mcpServers": { "fernforge-mcp-conform": { "command": "npx", "args": [ "-y", "@fernforge/[email protected]" ] } }}Vue d'ensemble
Author-side conformance, safety & spec-migration linter for MCP (Model Context Protocol) servers — eslint for your MCP server. Checks tool annotations, schema hygiene, tool-poisoning/injection patterns, registry/distribution metadata, and scans your sourc
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
@fernforge/mcp Conform s'exécute en local via stdio.
Dernière vérification : 2026-11-16. Author-side conformance, safety & spec-migration linter for MCP (Model Context Protocol) servers — eslint for your MCP server. Checks tool annotations, schema hygiene, tool-poisoning/injection patterns, registry/distribution metadata, and scans your sourc