Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.bitterdev/pixelletter-mcp

NPM · PIXELLETTER-MCP · SCANNED AUG 3

Send physical letters and faxes through the PixelLetter interface, test mode included.

Available components

+37 this week 61 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1700 tokens (~283/item across 6 items; 6 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · pixelletter-mcp

# add to Claude Code
claude mcp add bitterdev-pixelletter-mcp -- npx -y pixelletter-mcp
# add to Codex CLI
codex mcp add bitterdev-pixelletter-mcp -- npx -y pixelletter-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bitterdev-pixelletter-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pixelletter-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bitterdev-pixelletter-mcp --command npx --arg -y --arg pixelletter-mcp
# ~/.hermes/config.yaml
mcp_servers:
  bitterdev-pixelletter-mcp:
    command: "npx"
    args: ["-y", "pixelletter-mcp"]
// mcp.json
{
  "mcpServers": {
    "bitterdev-pixelletter-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pixelletter-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.

  • 2 Aug 26 +30
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass 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
    • Security disclosure: fail → unverified functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 1 Aug 26 +26
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass functional
    • Tool coverage: unverified → 100 functional
  • 31 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −50
    • Known CVEs: partial → unverified security
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • License: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Dependency health: partial → unverified functional
    • Maintenance: pass → unverified functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 28 Jul 26 +32
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Schema quality: unverified → good functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Licence: MIT functional
  • 27 Jul 26 24

    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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~1,589 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.

Tool Tokens
cancel_order ~70

Cancels a submitted order by its PixelLetter order id, which is on the order confirmation e-mail. Only works while the order has not been printed yet, otherwise PixelLetter answers with error 055.

NameTypeReqDescription
orderIdstringyesPixelLetter order id from the confirmation e-mail or the customer area.

No output schema declared.

No examples provided.

get_account_info ~47

Reads the stored customer data and the current credit of the PixelLetter account. Use it before sending to make sure the balance covers the order, error 021 means the credit is too low.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_interface_reference ~64

Returns what the PixelLetter interface documents: action values, dispatch centres, additional service codes, allowed upload types, limits and the published error codes. Offline lookup, no API call.

NameTypeReqDescription
errorCodestringLook up a single error code, for example "021".

No output schema declared.

No examples provided.

send_fax ~408

Sends documents or plain text as a fax through PixelLetter, without posting a letter. Additional services such as registered mail do not apply to faxes.

NameTypeReqDescription
addressarrayRecipient address, one line per array entry, country included. PixelLetter typesets it. Required when no file is sent.
controlstringRaw value for the control field of the interface. The only value in public use is NODUPLEX, which the duplex parameter sets for you, so only reach for this when PixelLetter gave you another token.
faxNumberstringyesFax number in international format, for example "+49 89 72448483".
filesarrayAbsolute paths of the documents to send, for example the PDF written by pdf-letter-mcp. Several files are converted and merged into one letter, in this order. Allowed: .pdf, .doc, .xls, .ppt, .rtf, .…
inlineFilesarrayDocuments passed as base64 instead of a path.
locationstringDispatch centre: 1 = Munich (DE), 2 = Hausleiten near Vienna (AT), 3 = Hamburg (DE). Default of the API is 1.
subjectstringSubject of the letter.
testModebooleanyesTest mode. true runs the order exactly like a real one but PixelLetter never prints, never sends and never charges. false really sends the letter. Always required, so nothing goes out by accident.
textstringLetter text as plain text, no HTML. Long texts run onto more pages automatically, your sender address is added by PixelLetter. "%Unterschrift%" on its own line inserts the signature stored in your Pi…
transactionstringYour own transaction id or short note. PixelLetter returns it with the response.

No output schema declared.

No examples provided.

send_letter ~772

Sends a letter through PixelLetter, either as ready made documents (absolute file paths, PDF preferred) or as plain text plus a recipient address that PixelLetter typesets. Optionally faxes the same document as well. Returns the result code and the transaction id.

NameTypeReqDescription
additionalServiceCodesarrayRaw addoption codes for services PixelLetter documents elsewhere or agrees per account. Only use numbers PixelLetter gave you.
addressarrayRecipient address, one line per array entry, country included. PixelLetter typesets it. Required when no file is sent.
alsoSendFaxbooleanSend the same document as a fax too. Needs faxNumber. Additional services stay letter only.
cashOnDeliveryobjectBank details for cash on delivery. Setting this block adds additional service 31.
colorPrintbooleanColour print instead of black and white (addoption 33). Letters only, and not available through every dispatch centre, see error 038.
controlstringRaw value for the control field of the interface. The only value in public use is NODUPLEX, which the duplex parameter sets for you, so only reach for this when PixelLetter gave you another token.
destinationstringDestination country as a two letter ISO code, for example DE, AT, CH. Mandatory for letters, a wrong code leads to wrong postage.
duplexbooleanPrint on both sides (true, the default of PixelLetter) or on one side only (false, sent as control NODUPLEX). Letters only.
faxNumberstringFax number in international format, for example "+49 89 72448483". Only needed with alsoSendFax.
filesarrayAbsolute paths of the documents to send, for example the PDF written by pdf-letter-mcp. Several files are converted and merged into one letter, in this order. Allowed: .pdf, .doc, .xls, .ppt, .rtf, .…
goGreenbooleanGoGreen, CO2 neutral postage (addoption 44). Letters only.
inlineFilesarrayDocuments passed as base64 instead of a path.
locationstringDispatch centre: 1 = Munich (DE), 2 = Hausleiten near Vienna (AT), 3 = Hamburg (DE). Default of the API is 1.
personalDeliverybooleanEigenhändig, personal delivery (code 29). Only together with registered.
registeredbooleanEinschreiben, registered mail (code 27). Germany only.
registeredDropInbooleanEinschreiben Einwurf, drop-in registered mail (code 30). Cannot be combined with the other registered variants.
returnAddressstringRaw value for the returnaddress field of the interface. Undocumented in the public handbooks.
returnReceiptbooleanRückschein, return receipt (code 28). Only together with registered.
subjectstringSubject of the letter.
testModebooleanyesTest mode. true runs the order exactly like a real one but PixelLetter never prints, never sends and never charges. false really sends the letter. Always required, so nothing goes out by accident.
textstringLetter text as plain text, no HTML. Long texts run onto more pages automatically, your sender address is added by PixelLetter. "%Unterschrift%" on its own line inserts the signature stored in your Pi…
transactionstringYour own transaction id or short note. PixelLetter returns it with the response.

No output schema declared.

No examples provided.

sign_invoice ~228

Sends documents to the PixelLetter invoice signing service (action 4) and optionally mails the signed PDF to the invoice recipient. The account needs electronic signatures enabled once in the customer area, otherwise PixelLetter answers with error 046.

NameTypeReqDescription
filesarrayAbsolute paths of the documents to send, for example the PDF written by pdf-letter-mcp. Several files are converted and merged into one letter, in this order. Allowed: .pdf, .doc, .xls, .ppt, .rtf, .…
inlineFilesarrayDocuments passed as base64 instead of a path.
notificationobjectLeave this out and nothing is mailed to the invoice recipient, you only get the signed file yourself.
testModebooleanyesTest mode. true signs with an advanced signature only, which is not legally sufficient, and costs nothing. false creates the qualified signature.
transactionstringYour own transaction id or short note. PixelLetter returns it with the response.

No output schema declared.

No examples provided.