In-depth architectural comparison of the AI Visibility Check and PDF Reader MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
AI Visibility Check
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
PDF Reader MCP
Developer Tools · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Verdict Summary: Choose AI Visibility Check if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose PDF Reader MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
A
Choose AI Visibility Check when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Check whether a business is visible to AI answer engines. Runs each query through a live AI search (Perplexity) and reports whether the business's site is cited, at what rank, and who gets cited instead. Pass 1-5 realistic customer-intent questions — what a potential customer would actually ask an AI (e.g. "best kitchen remodeler in Clearwater FL"). Never include the business's own name in a query. Returns a 0-100 visibility score, a tier, per-query results, the competing sources AI cited, and a shareable branded scorecard link.
PDF Reader MCP Tools (4)
inspect
Document and media evidence when Markdown is not enough. video_timeline (bounded scene/cue timeline) and render_frame (actual decoded frames), and cite_check (quote/location support, not semantic truth), are anymd Pro; PDF operations: inspect (page facts, metadata), render_page (PNG images), extract_regions (crop bounding boxes), ocr_pages / analyze_regions (configured OCR or vision provider), structure (JSON with document map, elements, geometry; profile quality|research adds trust and accessibility reports), compare (page-level diff of sources[0] vs sources[1]).
outline
Return a document heading tree with stable node ids, title paths, page/slide/chapter ranges and Markdown byte ranges. PDF bookmarks or detected headings, Word headings, PowerPoint slides, EPUB chapters and headings, HTML and Markdown. format json (default) or tree. Pass a node id to read to fetch that section.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
AI Visibility Check is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, PDF Reader MCP belongs to Developer Tools using local stdio subprocess. Select AI Visibility Check when you need capabilities focused on developer tools and PDF Reader MCP when you require tools for developer tools.
Read any document as clean Markdown: PDF, Word (DOCX), PowerPoint (PPTX), Excel (XLSX/XLS/ODS), CSV, EPUB, HTML or a web URL, Markdown/text, images (metadata + OCR), audio/video (metadata, chapters, subtitles). Pages/slides/sheets carry <!-- page N --> style markers for citation. Long documents stop at max_tokens (default 20000) and end with a cursor to continue; choose pages with pages: "1-5,8". A directory returns its readable files.
search
Search documents for text: one file, many files, whole directories (recursive, .gitignore aware), or URLs, across every format read supports. Returns each hit as file + page/slide/sheet + a snippet with the match in bold. mode auto (default) finds the exact phrase and falls back to BM25-ranked passages when there is none; literal or ranked force one. Narrow directories with glob, e.g. "*.pdf".