Home / MCP registry index / io.usefulapi/api2pdf
Api2Pdf MCP by usefulapi
io.usefulapi/api2pdf in the official MCP registry.
Endpoint https://api2pdf.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: MCP server for Api2Pdf — generate PDFs & images from HTML, URLs or office files; merge, barcodes.
We read its 16 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
api2pdf_html_to_pdf api2pdf_url_to_pdf api2pdf_markdown_to_pdf api2pdf_html_to_image api2pdf_url_to_image api2pdf_wkhtml_to_pdf api2pdf_office_to_pdf api2pdf_merge_pdfs api2pdf_compress_pdf api2pdf_extract_pages api2pdf_add_password api2pdf_convert_to_markdown api2pdf_generate_barcode api2pdf_get_balance api2pdf_get_status api2pdf_delete_file
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-api2pdf)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.