docpage-extract
Registry code: 2d0c2b25096c992d
doc.page PDF engine. Extraction: extract_pdf for markdown/elements (mode hybrid = tables + bounding boxes), get_chunks for RAG chunks, list_tables for structured tables with citations — always from a public PDF URL. Doc Links (API key required): create_doc_link publishes a PDF as a tracked share link, list_doc_links recovers links from earlier sessions, get_doc_link_stats reports visits/companies/per-page reading, revoke_doc_link disables a link.
- endpoint
- https://doc.page/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is docpage-extract live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is docpage-extract free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does docpage-extract have?
- 7 tools: get_chunks, list_tables, extract_pdf, create_doc_link, revoke_doc_link, get_doc_link_stats, list_doc_links.
- Is docpage-extract safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 7 tools
- degraded → live
- unknown → live
- used for
- extract a pdf to markdown
- chunk a pdf for rag
- extract tables from a pdf
- publish a pdf as a tracked link
- get reading stats for a shared pdf
- takes → gives
- documents, web pages → text, data
- tools
- 5 reads2 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
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.
extract_pdf reads auth-required never probed
Extract a PDF into clean Markdown and structured elements (headings, paragraphs). Returns the canonical ExtractedDocument object. mode "hybrid" runs a heavier semantic engine that also reconstructs tables and bounding boxes; the default "fast" engine is prose-only (low confidence.tables).
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "http(s) URL of the PDF to extract." }, "mode": { "enum": [ "fast", "hybrid" ], "type": "string", "description": "fast = prose engine. hybrid = semantic engine with tables + bounding boxes when deployed; falls back to fast with a warning otherwise." }, "outputs": { "type": "array", "items": { "enum": [ "markdown", "elements", "chunks", "images" ], "type": "string" }, "description": "Subset of outputs to include. Default: markdown and elements." }, "chunkTokens": { "type": "integer", "description": "Target chunk size in tokens (when chunks are requested). Default 512." } }, "additionalProperties": false }arguments 38 linescreate_doc_link changes data auth-required never probed
Publish a PDF as a tracked doc.page Doc Link and get back a shareable URL. The link belongs to the API key's account and also appears in its doc.page library. Requires an API key. Free plan: up to 3 active links; custom vanity slugs are premium-only. Optional expiry and open-notification toggle.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "http(s) URL of the PDF to publish (max 25 MB)." }, "name": { "type": "string", "description": "Display name in the library. Defaults to the filename." }, "slug": { "type": "string", "description": "Custom vanity slug (premium plans only). Lowercase letters, digits and hyphens." }, "expiresAt": { "type": "string", "description": "ISO 8601 date-time after which the link stops working. Omit for no expiry." }, "notifyOnOpen": { "type": "boolean", "description": "Email the account owner on the first open. Default true." } }, "additionalProperties": false }arguments 29 linesrevoke_doc_link changes data auth-required never probed
Disable a Doc Link of the API key's account (by id or slug) so the public URL stops serving. The item and its stats remain in the library; on the free plan this frees an active-link slot. Requires an API key.
{ "type": "object", "properties": { "id": { "type": "string", "description": "Doc Link item id." }, "slug": { "type": "string", "description": "Doc Link slug — alternative to id." } }, "additionalProperties": false }arguments 14 linesget_doc_link_stats reads auth-required 7h ago
Reading analytics for one Doc Link of the API key's account, by id or slug. Always returns the summary (total views, unique visitors, last visit). Premium plans additionally get countries, visitor companies (as_org) and per-page views + average dwell time; pass include:["visits"] for the recent visit rows. Requires an API key.
{ "type": "object", "properties": { "id": { "type": "string", "description": "Doc Link item id (from create_doc_link or list_doc_links)." }, "slug": { "type": "string", "description": "Doc Link slug — alternative to id." }, "include": { "type": "array", "items": { "enum": [ "visits" ], "type": "string" }, "description": "Extra sections. \"visits\" adds the recent visit rows (enriched on premium plans)." } }, "additionalProperties": false }arguments 24 lineslist_doc_links reads auth-required 7h ago
List the Doc Links of the API key's account (id, slug, URL, name, disabled/expiry state, total views, last view). Use this to recover links created in earlier sessions before querying stats. Requires an API key.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_chunks reads unknown 1h ago
Split a PDF into semantic chunks ready for embeddings (RAG). Each chunk carries its text, estimated tokens, starting page, section heading and the source element ids for citation.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "http(s) URL of the PDF to chunk." }, "maxTokens": { "type": "integer", "description": "Target chunk size in tokens. Default 512." } }, "additionalProperties": false }arguments 17 lineslist_tables reads unknown 7h ago
Return every table in a PDF as structured JSON (reconstructed rows and columns) with page and bounding box for verifiable citations. Uses the semantic (hybrid) engine.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "http(s) URL of the PDF." } }, "additionalProperties": false }arguments 13 lines
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.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id2d0c2b25096c992d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2d0c2b25096c992d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2d0c2b25096c992d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.