Small Print logo

Small Print

Query Small Print’s public record of MCP, skill, and plugin changes through four read-only MCP tools.

Install Small Print

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "small-print": {
      "command": "npx",
      "args": [
        "-y",
        "smallprint-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 4 tools correctly (Today).

Overview

Small Print MCP server exposes four read-only tools for querying Small Print’s public record of changes to MCP servers, agent skills, and plugins. It runs over stdio and can be started with npx or Docker. Use it when an agent needs to inspect recorded content changes, grades, or high- and critical-severity advisories before relying on a component. The repository also contains related CLI, GitHub Action, pre-commit hooks, and editor extensions, but those are separate from the MCP server.

Use cases

  • Query recorded changes before using an MCP server
  • Review grades for updated skills or plugins
  • Check for high or critical advisories in an agent workflow
  • Inspect Small Print’s public record from an MCP-compatible client

Key features

  • Four read-only MCP tools
  • Queries the public Small Print record
  • Covers MCP servers, skills, and plugins
  • Reports recorded changes and grades
  • Runs over stdio
  • Supports Docker-based execution

Tools4

What Small Print lets your agent do. Expand a tool for its parameters.

Verified live~2.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 17d

What it can do

From the 4 tools this server returned when we ran it; 4 declare their own safety hints.

Makes network requests · 4Read-only tools · 4
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age47 days
Maintainers1

Observed 2026-10-31 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2h ago via OSV.dev · smallprint-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.6kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed4Callable tools this server registers over MCP.

How Small Print works

What Small Print MCP server does

Small Print MCP server gives an MCP-compatible agent read-only access to Small Print’s public record. The record covers text supplied by MCP servers, agent skills, and plugins, along with changes identified between versions. Small Print grades changes using published rules and identifies high or critical advisories.

The server is intended for inspection rather than enforcement. An agent can use it to look up recorded information before using a component, while build failures and lock enforcement are handled by the separate GitHub Action and CLI included in the same repository.

How it works

The MCP implementation exposes four read-only tools over the public record. It does not mutate that record. The repository identifies the server in the registry as dev.smallprint/smallprint.

Small Print’s broader system gathers public registry listings and reads available new versions, then records and grades the changes it finds. The MCP server provides an agent-facing way to query that record. It is distinct from npx smallprint check, which examines locally installed configuration, and from npx smallprint gate, which checks recorded changes before a session.

Setup and configuration

Start the server with:

Terminal
npx -y smallprint-mcp

The repository also includes a Dockerfile that builds and runs the server over stdio. This mode is suitable for registries or MCP hosts that start a server process and communicate with it through standard input and output.

Configure the command in an MCP client that supports stdio servers. The repository also contains a Small Print extension for VS Code and Cursor, providing an editor-oriented way to use the project’s functionality.

Tools and capabilities

The MCP server provides four read-only tools for querying the public record. Together, they support agent workflows such as:

  • Checking whether a server, skill, or plugin has recorded text changes.
  • Inspecting the record associated with a component before an agent uses it.
  • Reviewing grading information for changes.
  • Looking for high or critical advisories associated with tracked versions.

The companion project can also produce local lock files, compare MCP versions and instruction-file fingerprints in CI, generate SARIF output, and run checks as pre-commit hooks. Those capabilities belong to the CLI, GitHub Action, or hooks rather than to the MCP tool interface.

Limitations and notes

The MCP interface is read-only and depends on Small Print’s public record. It is not the repository’s build gate and does not replace the local smallprint check or smallprint gate commands. The GitHub Action checks committed locks against repository files and versions; it does not inspect tool descriptions. The server itself is distributed as an stdio process, with Docker available for the same transport.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Small Print

Small Print is an MCP server that connects an AI agent to Small Print’s public record of MCP server, skill, and plugin text changes. It exposes four read-only tools for querying that record, including recorded changes and grading information, so an agent can inspect whether tracked content has changed or carries a high or critical advisory.

Run `npx -y smallprint-mcp` to start the server. It communicates over stdio, and the repository also provides a Dockerfile for running the same server in a container.

Yes, Cursor is supported by the repository’s Small Print extension. The MCP server itself runs as a standard stdio process, while the repository also provides an editor extension for Cursor and VS Code.

No, the MCP server is read-only and queries the public record. CI enforcement is provided by the separate GitHub Action, which fails a build when versions, skill files, or instruction files differ from a committed lock.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSmall Print AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/small-print?style=directory)](https://allmcps.com/mcp/small-print)
HTML Embed
<a href="https://allmcps.com/mcp/small-print"><img src="https://allmcps.com/api/badge/small-print?style=directory" alt="Small Print on AllMCPs" /></a>