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.

PrintGo

NPM · PRINTGO

Print PDFs, images, text, Markdown and HTML to your local printers, and track or cancel the jobs.

Available components

+27 this week 66 Trust /100

Last scanned (9 hours ago)

Scores higher than 38% of npm servers

Category Documents and Files

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 Security99
  • 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
  • 11 of 52 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 397 tokens (~56/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 27% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 14 Oct 26 +27
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Destructive annotations: 100 functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 27 functional
  • 13 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 12 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 8 Oct 26 39

    First indexed and scored.

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 18 Oct 2026 · Analysed npm/printgo@0.2.0

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 52 packages
Packages resolved 52
Stale 11
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~397 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
cancelPrintJob ~32

Cancel a job created by this server. Already printed pages cannot be recalled.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

checkPrinterStatus ~22

Read printer queue status.

NameTypeReqDescription
printerIdstringyes–

No output schema declared.

No examples provided.

getPrinterCapabilities ~26

Read the options reported by the printer driver.

NameTypeReqDescription
printerIdstringyes–

No output schema declared.

No examples provided.

getPrintJobStatus ~36

Read queue status for a job created by this server. Completion does not confirm physical printing.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

listPrinters ~16

List printers configured on this computer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

printMarkup ~135

Render and print Markdown or HTML. Supply content (32 KiB max) or assetUrl (1 MiB max). Reuse the same arguments and idempotencyKey for retries.

NameTypeReqDescription
assetUrlstring–Direct public or signed HTTPS URL containing UTF-8 Markdown or HTML. Provide assetUrl or content, never both.
contentstring–Inline Markdown or HTML source, up to 32 KiB. Provide content or assetUrl, never both.
formatstringyes–
idempotencyKeystringyes–
printerIdstringyes–
settingsobject––

No output schema declared.

No examples provided.

sendPrintCommand ~130

Print PDF, PNG, JPEG or UTF-8 text from a public HTTPS URL (10 MiB max). Reuse the same arguments and idempotencyKey for retries. Submission does not confirm physical printing.

NameTypeReqDescription
assetTypestring–Defaults to auto. Use text for extensionless plain-text URLs.
assetUrlstringyesDirect public or signed HTTPS file URL; supports PDF, PNG, JPEG and UTF-8 text, up to 10 MiB.
idempotencyKeystringyes–
printerIdstringyes–
settingsobject––

No output schema declared.

No examples provided.

Install

How do I install the PrintGo MCP server?

PrintGo runs locally as an npm package, launched with npx -y printgo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · printgo

# add to Claude Code
claude mcp add nishkalkashyap-printgo -- npx -y printgo
Common questions

What is the PrintGo MCP server?

PrintGo is an MCP server listed in the public MCP registry as io.github.Nishkalkashyap/printgo. Print PDFs, images, text, Markdown and HTML to your local printers, and track or cancel the jobs. This page covers its npm package (printgo).

Is the PrintGo MCP server safe to use?

PrintGo scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 PrintGo MCP server expose?

PrintGo exposes 7 tools: listPrinters, getPrinterCapabilities, checkPrinterStatus, sendPrintCommand, printMarkup, and 2 more. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.

Is the PrintGo MCP server still maintained?

PrintGo is still listed as active in the MCP registry. We last reached this channel on 18 October 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 PrintGo MCP server under?

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