mcp-registry/com.pdfia/pdf-tools · v1.0.0
As of 2026-10-21 16:50 UTC, the Pdfia Pdf Tools MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Free PDF tools for AI agents: merge, split, rotate, watermark, page numbers, metadata, flatten.
Claude Code
claude mcp add --transport http pdfia-pdf-tools-mcp-server https://pdfia.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"pdfia-pdf-tools-mcp-server": {
"type": "http",
"url": "https://pdfia.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
6 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.pdfia%2Fpdf-tools/fixes
{
"name": "add_page_numbers",
"description": "Stamp page numbers onto every page of a PDF. Returns base64.",
"inputSchema": {
"type": "object",
"required": [
"file"
],
"properties": {
"file": {
"type": "string",
"description": "The PDF file, base64-encoded (max 10 MB)"
},
"size": {
"type": "number",
"description": "Font size 6–24, default 12"
},
"start": {
"type": "number",
"description": "First number, default 1"
},
"format": {
"enum": [
"n",
"page-n",
"n-of-total"
],
"type": "string",
"description": "Default n"
},
"position": {
"enum": [
"bottom-center",
"bottom-right",
"bottom-left",
"top-center"
],
"type": "string",
"description": "Default bottom-center"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "get_pdf_metadata",
"description": "Read a PDF's document properties (title, author, subject, keywords, creator, producer, dates, page count).",
"inputSchema": {
"type": "object",
"required": [
"file"
],
"properties": {
"file": {
"type": "string",
"description": "The PDF file, base64-encoded (max 10 MB)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "merge_pdfs",
"description": "Merge multiple PDF files into one, in the order given. Returns the merged PDF as base64.",
"inputSchema": {
"type": "object",
"required": [
"files"
],
"properties": {
"files": {
"type": "array",
"items": {
"type": "string",
"description": "The PDF file, base64-encoded (max 10 MB)"
},
"description": "2+ PDFs, base64-encoded, in merge order"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.pdfia/pdf-tools"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.pdfia/pdf-tools"}) over MCP.
add_page_numbers ~170 tokenswatermark_pdf ~162 tokensset_pdf_metadata ~142 tokensrotate_pdf ~126 tokenssplit_pdf ~126 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.pdfia%2Fpdf-tools?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.pdfia%2Fpdf-tools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pdfia%2Fpdf-tools.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pdfia%2Fpdf-tools.svg :target: https://glimind.com/server/mcp-registry%2Fcom.pdfia%2Fpdf-tools?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e0598f185b26f8ea…, first seen 2026-10-17, included at leaf 5495 of 40,573. Version history · verify what your client received.
Compare: most reliable files servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 16:50 UTC, the Pdfia Pdf Tools MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Pdfia Pdf Tools MCP server advertises 10 tools, including add_page_numbers, extract_pages, flatten_pdf, get_pdf_metadata, merge_pdfs.
Point your MCP client at this streamable-http endpoint: https://pdfia.com/mcp
Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.