oxpdf-mcp@0.1.0
VERIFIED· not startedPublisher claims: "MCP server for 0xPdf — schema-first PDF to structured JSON for AI agents" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
PDF_PARSING_API_KEYPDF_PARSING_BEARER_TOKENPDF_PARSING_MCP_MAX_ESTIMATED_TOKENSConfiguration, not credentials: ENV, ENVIRONMENT, PDF_PARSING_ALLOWED_API_HOSTS, PDF_PARSING_ALLOWED_FILE_ROOTS, PDF_PARSING_API_BASE_URL, PDF_PARSING_API_PREFIX, PDF_PARSING_API_TIMEOUT_SECONDS, PDF_PARSING_MCP_DISALLOW_FULL_RESPONSE_MODE, PDF_PARSING_MCP_MAX_BATCH_FILES, PDF_PARSING_MCP_MAX_BATCH_TOTAL_MB, PDF_PARSING_MCP_MAX_CONCURRENT_HEAVY_TOOLS, PDF_PARSING_MCP_MAX_LIST_ITEMS, PDF_PARSING_MCP_MAX_OBJECT_DEPTH, PDF_PARSING_MCP_MAX_RETRIES, PDF_PARSING_MCP_MAX_STRING_CHARS, PDF_PARSING_MCP_RESPONSE_BUDGET_POLICY, PDF_PARSING_MCP_RESPONSE_CHAR_LIMIT, PDF_PARSING_MCP_RETRY_BACKOFF_BASE_SECONDS, PDF_PARSING_REQUIRE_HTTPS- Where it talks to
- no vendor host named in the codeAlso 0xpdf.io — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names 0xpdf.io as well as its own vendor. The guard injects PDF_PARSING_API_KEY, PDF_PARSING_BEARER_TOKEN, PDF_PARSING_MCP_MAX_ESTIMATED_TOKENS only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 2,283 lines in 15 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for oxpdf-mcp@0.1.0 as of 5 h ago. This is the package itself, not its dependencies.