io.github.bitterdev/pixelletter-mcp
NPM · PIXELLETTER-MCP · SCANNED SEP 21
Send physical letters and faxes through the PixelLetter interface, test mode included.
Available components
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 & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).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 Management93
- Stability observed for 28 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_letter" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.bitterdev/pixelletter-mcp server?
io.github.bitterdev/pixelletter-mcp runs locally as an npm package, launched with npx -y pixelletter-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 · pixelletter-mcp
claude mcp add bitterdev-pixelletter-mcp -- npx -y pixelletter-mcp
{
"mcpServers": {
"bitterdev-pixelletter-mcp": {
"command": "npx",
"args": [
"-y",
"pixelletter-mcp"
]
}
}
} {
"servers": {
"bitterdev-pixelletter-mcp": {
"command": "npx",
"args": [
"-y",
"pixelletter-mcp"
]
}
}
} codex mcp add bitterdev-pixelletter-mcp -- npx -y pixelletter-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bitterdev-pixelletter-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"pixelletter-mcp"
],
"enabled": true
}
}
} openclaw mcp add bitterdev-pixelletter-mcp --command npx --arg -y --arg pixelletter-mcp
mcp_servers:
bitterdev-pixelletter-mcp:
command: "npx"
args: ["-y", "pixelletter-mcp"] {
"McpServers": {
"bitterdev-pixelletter-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pixelletter-mcp"
]
}
}
} assistant mcp add bitterdev-pixelletter-mcp -t stdio -c npx -a -y pixelletter-mcp
{
"mcpServers": {
"bitterdev-pixelletter-mcp": {
"command": "npx",
"args": [
"-y",
"pixelletter-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/pixelletter-mcp@1.0.3
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 →
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 →
cancel_order 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.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | PixelLetter order id from the confirmation e-mail or the customer area. |
No output schema declared.
No examples provided.
get_account_info Get account info and balance ~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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| errorCode | string | – | Look up a single error code, for example "021". |
No output schema declared.
No examples provided.
send_fax 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | array | – | Recipient address, one line per array entry, country included. PixelLetter typesets it. Required when no file is sent. |
| control | string | – | Raw 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. |
| faxNumber | string | yes | Fax number in international format, for example "+49 89 72448483". |
| files | array | – | Absolute 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, .… |
| inlineFiles | array | – | Documents passed as base64 instead of a path. |
| location | string | – | Dispatch centre: 1 = Munich (DE), 2 = Hausleiten near Vienna (AT), 3 = Hamburg (DE). Default of the API is 1. |
| subject | string | – | Subject of the letter. |
| testMode | boolean | yes | Test 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. |
| text | string | – | Letter 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… |
| transaction | string | – | Your own transaction id or short note. PixelLetter returns it with the response. |
No output schema declared.
No examples provided.
send_letter 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.
| Name | Type | Req | Description |
|---|---|---|---|
| additionalServiceCodes | array | – | Raw addoption codes for services PixelLetter documents elsewhere or agrees per account. Only use numbers PixelLetter gave you. |
| address | array | – | Recipient address, one line per array entry, country included. PixelLetter typesets it. Required when no file is sent. |
| alsoSendFax | boolean | – | Send the same document as a fax too. Needs faxNumber. Additional services stay letter only. |
| cashOnDelivery | object | – | Bank details for cash on delivery. Setting this block adds additional service 31. |
| colorPrint | boolean | – | Colour print instead of black and white (addoption 33). Letters only, and not available through every dispatch centre, see error 038. |
| control | string | – | Raw 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. |
| destination | string | – | Destination country as a two letter ISO code, for example DE, AT, CH. Mandatory for letters, a wrong code leads to wrong postage. |
| duplex | boolean | – | Print on both sides (true, the default of PixelLetter) or on one side only (false, sent as control NODUPLEX). Letters only. |
| faxNumber | string | – | Fax number in international format, for example "+49 89 72448483". Only needed with alsoSendFax. |
| files | array | – | Absolute 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, .… |
| goGreen | boolean | – | GoGreen, CO2 neutral postage (addoption 44). Letters only. |
| inlineFiles | array | – | Documents passed as base64 instead of a path. |
| location | string | – | Dispatch centre: 1 = Munich (DE), 2 = Hausleiten near Vienna (AT), 3 = Hamburg (DE). Default of the API is 1. |
| personalDelivery | boolean | – | Eigenhändig, personal delivery (code 29). Only together with registered. |
| registered | boolean | – | Einschreiben, registered mail (code 27). Germany only. |
| registeredDropIn | boolean | – | Einschreiben Einwurf, drop-in registered mail (code 30). Cannot be combined with the other registered variants. |
| returnAddress | string | – | Raw value for the returnaddress field of the interface. Undocumented in the public handbooks. |
| returnReceipt | boolean | – | Rückschein, return receipt (code 28). Only together with registered. |
| subject | string | – | Subject of the letter. |
| testMode | boolean | yes | Test 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. |
| text | string | – | Letter 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… |
| transaction | string | – | Your own transaction id or short note. PixelLetter returns it with the response. |
No output schema declared.
No examples provided.
sign_invoice Sign invoice electronically ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Absolute 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, .… |
| inlineFiles | array | – | Documents passed as base64 instead of a path. |
| notification | object | – | Leave this out and nothing is mailed to the invoice recipient, you only get the signed file yourself. |
| testMode | boolean | yes | Test mode. true signs with an advanced signature only, which is not legally sufficient, and costs nothing. false creates the qualified signature. |
| transaction | string | – | Your own transaction id or short note. PixelLetter returns it with the response. |
No output schema declared.
No examples provided.
What is the io.github.bitterdev/pixelletter-mcp server?
io.github.bitterdev/pixelletter-mcp is listed in the public MCP registry as io.github.bitterdev/pixelletter-mcp. Send physical letters and faxes through the PixelLetter interface, test mode included. This page covers its npm package (pixelletter-mcp).
Is the io.github.bitterdev/pixelletter-mcp server safe to use?
io.github.bitterdev/pixelletter-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.bitterdev/pixelletter-mcp server expose?
io.github.bitterdev/pixelletter-mcp exposes 6 tools: send_letter, send_fax, get_account_info, cancel_order, sign_invoice, get_interface_reference. Their descriptions and schemas cost roughly 1,589 tokens of context every time the server is loaded.
Is the io.github.bitterdev/pixelletter-mcp server still maintained?
io.github.bitterdev/pixelletter-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.bitterdev/pixelletter-mcp server under?
io.github.bitterdev/pixelletter-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.