Smallprint Action

What gostanos/smallprint-action MCP server does

The gostanos/smallprint-action MCP server provides read-only access to the public Small Print record. That record tracks the text supplied by MCP servers, agent skills, and plugins, including versions, differences, tool descriptions, and schemas. Changes are assessed using the grading rules published by Small Print, with high and critical changes and advisories called out in the record.

The repository also contains a GitHub Action and command-line tooling, but the MCP portion is the smallprint-mcp package in the mcp/ directory. The action itself checks a repository’s local files and versions against a committed lock; it is separate from the MCP server’s read-only record queries.

How it works

The gostanos/smallprint-action MCP server starts with npx -y smallprint-mcp and communicates over standard input and output. Its registry name is dev.smallprint/smallprint. MCP clients can call its four read-only tools to inspect information held in the public record. The supplied material does not list the individual tool names or their argument schemas, so client configuration should rely on the package’s published MCP metadata rather than assumed names.

Small Print gathers records from public registries, reads available new versions, and grades discovered changes according to its written rules. The MCP server queries that public record; it is not described as uploading local project files or changing registry data.

Setup and configuration

Configure an MCP client to launch the package with Node and the command npx -y smallprint-mcp. The repository identifies Node-based usage through npx; its pre-commit instructions specifically require Node 20 or later, although the MCP excerpt does not state a separate minimum version for the server.

The project also includes a Dockerfile that builds and runs the server over stdio. This is intended for registries that start a server to verify that it answers. No environment variables, API credentials, account, or write permission are documented for the MCP server in the supplied material.

Tools and capabilities

The gostanos/smallprint-action MCP server offers four read-only tools over the public Small Print record. The available record covers:

• Versioned descriptions and schemas for MCP servers, skills, and plugins.
• Differences between recorded versions.
• Graded changes, including high and critical classifications.
• Public advisories associated with tracked entries.

The broader repository’s CLI can inspect installed configurations, and its GitHub Action can fail builds when locked versions or instruction files change. Those functions are not MCP tools and should not be treated as capabilities exposed by the four read-only server tools.

Limitations and notes

The provided documentation does not enumerate the four tool names, input fields, or exact response formats. It also does not describe write operations, private-record access, or client-specific setup beyond stdio execution. The record is public, while the separate Small Print account and notification features concern email or Discord briefs and are not stated to be required by this MCP server.

The repository’s local lock check does not read tool descriptions: it compares versions and file fingerprints. Use the MCP server when an agent needs the public Small Print record, and use the action or CLI when the goal is local repository enforcement.

For developers evaluating the gostanos/smallprint-action MCP server in the Developer Tools category, the key fit is read-only change and advisory lookup through a conventional stdio MCP process.