_ registry / mcp http-sse · checked 2h ago

presio

https://presio.xyz

Registry code: d66dd8bd95951886

api record

Present PDFs from the browser: upload to start a slideshow or validate Presio sidecars. No auth.

from a public catalogue that lists it, not from the operator

endpoint
https://presio.ch/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 it live, free and safe measured by this hub
Is presio live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is presio free to use?
Yes — the hub reached it with no key and no payment.
What tools does presio have?
3 tools: check_pdf, present_pdf, plugin_guide.
Is presio 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.
reachable
live
uptime, 30 days
98.4%

90 days 98.7%· all time 98.7%

latency
212ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 371 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • start a slideshow from a pdf
  • validate pdf presentation attachments
takes → gives
documents → data
tools
1 reads1 changes data
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 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.

  • plugin_guide open 16h ago

    The guide to building a Presio plugin: the workflow (a presio-<name> GitHub repo from the template, the checker, a tag, and a ?plugins= link that loads it), the manifest, and the full window.presio API. Read it before writing a plugin. Same as GET /plugins.md.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • check_pdf reads unknown 9h ago

    Validate Presio notes/media sidecar attachments in a PDF. Same as POST /api/check.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "pdf_base64"
      ],
      "properties": {
        "pdf_base64": {
          "type": "string",
          "description": "PDF file contents, base64-encoded"
        }
      }
    }
    arguments 13 lines
  • present_pdf changes data unknown never probed

    Upload a PDF to start a local Presio presentation. Returns a url — open it in a browser to finish handoff (skips share). To replace an existing presentation's deck instead of creating one, pass its session_id plus controller_token (the t= parameter of the url from the original create call) and the same link keeps working. Same as POST /api/present.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "pdf_base64"
      ],
      "properties": {
        "filename": {
          "type": "string",
          "description": "Original filename, e.g. deck.pdf"
        },
        "pdf_base64": {
          "type": "string",
          "description": "PDF file contents, base64-encoded"
        },
        "session_id": {
          "type": "string",
          "description": "Id of an existing presentation to update in place (from an earlier present response) instead of creating a new one"
        },
        "controller_token": {
          "type": "string",
          "description": "Controller token for that presentation — the t= query parameter of the url returned when it was created. Required whenever session_id is given."
        }
      }
    }
    arguments 25 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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d66dd8bd95951886.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d66dd8bd95951886/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d66dd8bd95951886/badge.svg)](https://brick.blue/agent/d66dd8bd95951886?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.

_ how we know
card completeness
70%

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.