_ registry / mcp http-sse · checked 45m ago

PDF Server

https://example-server.modelcontextprotocol.io

Registry code: 2df13808986ffd28

api record

This service allows displaying, listing, reading, and saving PDF documents.

endpoint
https://example-server.modelcontextprotocol.io/pdf/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime
100%
latency
174ms

last good check

priced tools
0

of 4 tools

_ what it is for
topic
documents & files storage & sharing
used for
  • display pdf document
  • list available pdfs
  • read pdf bytes
  • save annotated pdf
takes → gives
data, documents → documents
tools
3 reads1 changes data
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_pdfs reads open 45m ago

    List available PDFs that can be displayed

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • read_pdf_bytes reads unknown never probed

    Read a range of bytes from a PDF (max 512KB per request). The model should NOT call this tool directly.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "PDF URL or local file path"
    },
    "offset": {
      "type": "number",
      "default": 0,
      "minimum": 0,
      "description": "Byte offset"
    },
    "byteCount": {
      "type": "number",
      "default": 524288,
      "maximum": 524288,
      "minimum": 1,
      "description": "Bytes to read"
    }
  }
}
    arguments 26 lines
  • display_pdf reads unknown never probed

    Show and render a PDF in a read-only viewer. Use this tool when the user wants to view or read a PDF. The renderer displays the document for viewing. The widget exposes app-registered tools for page navigation, text extraction, searching, and zoom control. Accepts local files (use list_pdfs), client MCP root directories, or any HTTPS URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "url": {
      "type": "string",
      "default": "https://arxiv.org/pdf/1706.03762",
      "description": "PDF URL or local file path"
    },
    "page": {
      "type": "number",
      "default": 1,
      "minimum": 1,
      "description": "Initial page"
    }
  }
}
    arguments 17 lines
  • save_pdf changes data unknown never probed

    Save annotated PDF bytes back to a local file. The model should NOT call this tool directly — use interact with action: save_as instead.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url",
    "data"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Original PDF URL or local file path"
    },
    "data": {
      "type": "string",
      "description": "Base64-encoded PDF bytes"
    }
  }
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2df13808986ffd28/badge.svg)](https://brick.blue/agent/2df13808986ffd28)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on modelcontextprotocol.io 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.