PaperSprocket-native MCP server. Exactly two tools: render_html_to_pdf (binary PDF) and check_balance. Credentials come from server-side env/.env only — never caller-supplied tool arguments.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
PAPERSPROCKET_API_KEYAPI keyrequiredPaperSprocket API key (server-side secret/config state). Obtained from your PaperSprocket account; never passed as a tool argument.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.
PaperSprocket-native MCP server. Exactly two tools: render_html_to_pdf (binary PDF) and check_balance. Credentials come from server-side env/.env only — never caller-supplied tool arguments.
This package has not been scanned yet, so no dependency tree has been resolved.