_ registry / mcp streamable-http · checked 4h ago

siteprint-examples

https://siteprint.app

Registry code: 3fccbe36846a0676

api record

Siteprint turns a website into an exact prompt or DESIGN.md. Siteprint Web runs in any browser (inspect free; Pro $9 a month or $49 a year); Siteprint for Safari is a separate Mac extension (Pro a one-time $19.99). Call about_siteprint for what each does. Without a key this server has four example DESIGN.md exports and setup steps; with a Siteprint Web key it serves the person's own prints.

endpoint
https://siteprint.app/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 it live, free and safe measured by this hub
Is siteprint-examples live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is siteprint-examples free to use?
Yes — the hub reached it with no key and no payment.
What tools does siteprint-examples have?
4 tools: get_setup, list_example_designs, get_example_design, about_siteprint.
Is siteprint-examples 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
100%

90 days 100%· all time 100%

latency
257ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 155 checks · signed record
  • unknown → live
_ 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 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.

  • about_siteprint open 13h ago

    Siteprint's two products (the web app in any browser and the Safari extension for Mac), what each does, and their pricing.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_setup unknown never probed

    How to connect the person's own Siteprint designs to Claude Code, Cursor, Codex or another client: the web app's remote server with a key, or the Safari extension's local server.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "agent": {
          "enum": [
            "claude-code",
            "cursor",
            "codex",
            "other"
          ],
          "type": "string",
          "default": "claude-code"
        }
      }
    }
    arguments 15 lines
  • list_example_designs unknown never probed

    Real Siteprint scans of four public sites, each with the original page a coding agent built from it. Returns ids for get_example_design.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_example_design unknown never probed

    The DESIGN.md Siteprint exported from one example scan: exact colours, type, spacing, corners and layout as a design direction for new UI.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "enum": [
            "linear",
            "stripe",
            "ramp",
            "cal"
          ],
          "type": "string"
        }
      }
    }
    arguments 17 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 3fccbe36846a0676.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3fccbe36846a0676/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/3fccbe36846a0676/badge.svg)](https://brick.blue/agent/3fccbe36846a0676?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
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.