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.

dev.smallprint/smallprint

NPM · SMALLPRINT-MCP · SCANNED SEP 26

The small print of MCP servers, skills and plugins, hashed, diffed and graded, from the record.

Available components

+4 this week 69 Trust /100
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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1361 tokens (~340/item across 4 items; 4 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Install

How do I install the dev.smallprint/smallprint MCP server?

dev.smallprint/smallprint runs locally as an npm package, launched with npx -y smallprint-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 · smallprint-mcp

# add to Claude Code
claude mcp add dev-smallprint-smallprint -- npx -y smallprint-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-smallprint-smallprint": {
      "command": "npx",
      "args": [
        "-y",
        "smallprint-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-smallprint-smallprint": {
      "command": "npx",
      "args": [
        "-y",
        "smallprint-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dev-smallprint-smallprint -- npx -y smallprint-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-smallprint-smallprint": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "smallprint-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-smallprint-smallprint --command npx --arg -y --arg smallprint-mcp
# ~/.hermes/config.yaml
mcp_servers:
  dev-smallprint-smallprint:
    command: "npx"
    args: ["-y", "smallprint-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-smallprint-smallprint": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "smallprint-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dev-smallprint-smallprint -t stdio -c npx -a -y smallprint-mcp
// mcp.json
{
  "mcpServers": {
    "dev-smallprint-smallprint": {
      "command": "npx",
      "args": [
        "-y",
        "smallprint-mcp"
      ]
    }
  }
}
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.

  • 26 Sept 26 +1

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

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

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

  • 22 Sept 26 +1

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

  • 20 Sept 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.2 functional
  • 18 Sept 26 +1

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

  • 17 Sept 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 50% → 100% ▲ functional
    • Stability: unverified → 0.10 ▲ functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: unverified functional
    • Schema quality: good → excellent functional
    • Package version: 0.1.0 → 0.2.0 functional
  • 15 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
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 26 Sept 2026 · Analysed npm/smallprint-mcp@0.2.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,222 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
advisories_for ~275

Every public security advisory on record that names one entry, each attributed to the database or report that published it, with its severity criterion and the affected version range. Use it when deciding whether a specific version is inside a known advisory, or after lookup_entry reported advisories; it adds nothing for an entry with none. Small Print attributes and never judges: the severity is the source's or a printed CVSS band. Read-only: one HTTPS GET to smallprint.dev per call, no account, no key, nothing about the caller sent, and the server or skill asked about is never run or contacted. Rate limited to one entry per request; a 429 answer says to wait a minute. A name not in the catalog returns a plain error, not a guess.

NameTypeReqDescription
namestringyesThe entry, with its registry prefix when known: npm:@scope/name, pypi:name, mcp-registry:io.github.owner/server, skills.sh:owner/repo/skill, oci:ghcr.io/owner/image. A bare name is read as an npm pac…
versionstring–A version string to read the affected ranges against, for example 1.4.2. Optional; the ranges are returned either way and the caller compares.
NameTypeReqDescription
advisoriesarrayyes–
canonicalNamestringyes–
totalnumberyes–
urlstringyes–

No examples provided.

changed_since_approval ~340

Yes or no, before using a server or skill: has its small print moved since the version, content hash or date that was reviewed? The answer opens with UNCHANGED, CHANGED or UNKNOWN, then the releases that changed it since and their worst grade, then whether the review can stand. Use it on every run when an approval is on file, instead of re-reading the tools; use lookup_entry when nothing was approved yet and changes_since to read the diffs after a CHANGED answer. UNKNOWN means the approved version is not on record or its small print was never read, so nothing is compared; treat it as no answer, not as safe. Read-only: one HTTPS GET to smallprint.dev per call, no account, no key, nothing about the caller sent, and the server or skill asked about is never run or contacted. Rate limited to one entry per request; a 429 answer says to wait a minute. A name not in the catalog returns a plain error, not a guess.

NameTypeReqDescription
approvedstringyesWhat was reviewed: a version string exactly as published (1.4.2), the 64-character hex content hash from an earlier answer, or an ISO date YYYY-MM-DD. A date compares against releases published after…
namestringyesThe entry, with its registry prefix when known: npm:@scope/name, pypi:name, mcp-registry:io.github.owner/server, skills.sh:owner/repo/skill, oci:ghcr.io/owner/image. A bare name is read as an npm pac…
NameTypeReqDescription
advisoriesnumberyes–
canonicalNamestringyes–
latestContentHashstring|nullyes–
latestVersionstring|nullyes–
releasesSincearrayyes–
statusstringyes–
urlstringyes–
worstGradestring|nullyes–

No examples provided.

changes_since ~358

The releases of one entry whose tool descriptions, schemas or instructions changed, each with its diff, its grade and the rule that graded it (rules at https://smallprint.dev/how-we-grade). Use it to read what actually changed, after lookup_entry or changed_since_approval said something did; use changed_since_approval instead when the question is only whether anything moved since an approved version. Filters: since keeps releases published on or after a date; min_severity drops changes below a grade (default low, so plain version bumps and identical releases are never listed). Returns at most 12 releases in text; the structured result carries all of them. Read-only: one HTTPS GET to smallprint.dev per call, no account, no key, nothing about the caller sent, and the server or skill asked about is never run or contacted. Rate limited to one entry per request; a 429 answer says to wait a minute. A name not in the catalog returns a plain error, not a guess.

NameTypeReqDescription
min_severitystring–Lowest grade to include: info, low, medium, high or critical. Default low. Use high to see only changes that name a secret, a destination or an instruction to hide something.
namestringyesThe entry, with its registry prefix when known: npm:@scope/name, pypi:name, mcp-registry:io.github.owner/server, skills.sh:owner/repo/skill, oci:ghcr.io/owner/image. A bare name is read as an npm pac…
sincestring–ISO date, YYYY-MM-DD; only releases published on or after it. Omit for every release on record.
NameTypeReqDescription
canonicalNamestringyes–
releasesarrayyes–
totalnumberyes–
urlstringyes–

No examples provided.

lookup_entry ~249

What the record holds for one MCP server, skill or plugin: versions on record, the tools read from the pinned version, how many releases changed the small print and the worst grade, and the advisories that name it. Use it first, when nothing about the entry is known yet, or to confirm an entry exists before the other tools; use changes_since for the diffs and advisories_for for advisory detail. Not for private or unpublished servers, which have no page. Read-only: one HTTPS GET to smallprint.dev per call, no account, no key, nothing about the caller sent, and the server or skill asked about is never run or contacted. Rate limited to one entry per request; a 429 answer says to wait a minute. A name not in the catalog returns a plain error, not a guess.

NameTypeReqDescription
namestringyesThe entry, with its registry prefix when known: npm:@scope/name, pypi:name, mcp-registry:io.github.owner/server, skills.sh:owner/repo/skill, oci:ghcr.io/owner/image. A bare name is read as an npm pac…
NameTypeReqDescription
advisoriesarrayyes–
canonicalNamestringyes–
kindstringyes–
latestVersionstring|nullyes–
releasesChangednumberyes–
toolsReadnumber|nullyes–
urlstringyes–
versionsOnRecordnumberyes–
worstGradestringyes–

No examples provided.

Common questions

What is the dev.smallprint/smallprint MCP server?

dev.smallprint/smallprint is an MCP server listed in the public MCP registry as dev.smallprint/smallprint. The small print of MCP servers, skills and plugins, hashed, diffed and graded, from the record. This page covers its npm package (smallprint-mcp).

Is the dev.smallprint/smallprint MCP server safe to use?

dev.smallprint/smallprint scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. 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 dev.smallprint/smallprint MCP server expose?

dev.smallprint/smallprint exposes 4 tools: lookup_entry, changes_since, advisories_for, changed_since_approval. Their descriptions and schemas cost roughly 1,222 tokens of context every time the server is loaded.

Is the dev.smallprint/smallprint MCP server still maintained?

dev.smallprint/smallprint is still listed as active in the MCP registry. We last reached this channel on 26 September 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 dev.smallprint/smallprint MCP server under?

dev.smallprint/smallprint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.