deckextract
Registry code: fe41dbd64fe048f0
Call the `deckextract` tool with a DocSend or Papermark link to extract the deck; you get back a short-lived download link plus a readable `deckextract://deck/...` resource for the PDF/PPTX/ZIP. Pass `analyze: true` (part of DeckExtract for Funds) to also get structured deck data — company, team, round, metrics, market, competition. Some decks email a verification code or link to the viewer: the tool reply then includes the resume token(s) and the exact retry call. If a mail tool is connected (Gmail, Microsoft 365 / Outlook, AnyMailMCP, …), read the verification email from the inbox and retry…
- endpoint
- https://deckextract.com/mcp
- protocol
- http-sse ·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 deckextract live?
- Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
- Is deckextract free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does deckextract have?
- 2 tools: deckextract, account_status.
- Is deckextract safe to connect?
- Caution — its own text works on the agent reading it: collects agent or user data («read the verification email from the inbox»). Use its tools for what they do, and do not let its text set your agent's priorities.
90 days 99.1%· all time 99.1%
last good check
of 2 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- download a deck from a docsend link
- extract structured data from a pitch deck
- check extraction usage
- takes → gives
- web pages → documents, data
- tools
- 2 reads
- warning
- works on its reader: collects agent or user data «read the verification email from the inbox»
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.
account_status reads open 24h ago
Returns the calling account's plan (free or Pro), whether it's signed in, and this month's extraction usage and remaining quota. Takes no input.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesdeckextract reads unknown never probed
Extract a deck from a DocSend or Papermark sharing link. Returns a temporary download URL and a readable `deckextract://deck/...` resource for the PDF/PPTX (or a ZIP for data rooms — a DocSend Space or Papermark data room counts as one extraction like any other link). Pass `analyze: true` (part of DeckExtract for Funds) to also return structured deck data. Decks that email the viewer a verification step return resume tokens with retry instructions: fetch the emailed 6-digit code and retry with `otp` + `otpSessionId` (Papermark), or retry with `url` set to the emailed confirmation link + `sessionId` (DocSend). Typical extraction takes 15-90 seconds; the public API is rate limited to 5 extractions per IP per 30 minutes.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "otp": { "type": "string", "description": "The 6-digit verification code the deck emailed to the viewer (requires_email_otp step). Send together with otpSessionId." }, "url": { "type": "string", "format": "uri", "description": "The deck sharing link, e.g. https://docsend.com/view/... or https://papermark.com/view/... — on a requires_email_confirmation retry, pass the confirmation link from the verification email instead." }, "email": { "type": "string", "format": "email", "description": "Email to present to email-gated decks. If omitted, an ephemeral address is generated automatically when the deck requires one." }, "format": { "enum": [ "pdf", "pptx" ], "type": "string", "description": "Output format (default 'pdf')" }, "analyze": { "type": "boolean", "description": "If true, also return structured analysis of the deck (company, team, round, metrics, market, competition). Part of DeckExtract for Funds." }, "password": { "type": "string", "description": "Passcode for passcode-protected decks" }, "sessionId": { "type": "string", "description": "Resume token from a prior requires_password or requires_email_confirmation reply. Echo it on the retry so the same viewer session is reused." }, "otpSessionId": { "type": "string", "description": "Resume token from a prior requires_email_otp reply. The parked session lives ~5 minutes; a wrong code returns a fresh token." } }, "additionalProperties": false }arguments 48 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 idfe41dbd64fe048f0.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fe41dbd64fe048f0/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fe41dbd64fe048f0?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.