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

Panderr

https://panderr.com

Registry code: 28078e16a46f83d1

api record

Move your website without rebuilding it — by URL, or upload a ZIP of your site.

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

endpoint
https://panderr.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 it live, free and safe measured by this hub
Is Panderr live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is Panderr free to use?
Yes — the hub reached it with no key and no payment.
What tools does Panderr have?
2 tools: start_zip_import, start_website_migration.
Is Panderr 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
559ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

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

  • start_zip_import unknown never probed

    Use when the customer has generated or downloaded a static website ZIP with ChatGPT, Claude, or another AI tool and wants visual editing and publishing in Panderr Studio. Returns a link to Panderr's existing ZIP uploader. The customer must download the ZIP and select it in Panderr; this tool does not transfer, import, save, or publish files. Supported static website exports only, not arbitrary application source archives, backend projects, or projects requiring a build. No prior website hosting is required.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • start_website_migration unknown 59m ago

    Prepare an existing public website for migration into Panderr. Returns a Panderr link where the user can begin the migration process. Project creation and editing happen later in Panderr.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "websiteUrl"
  ],
  "properties": {
    "mode": {
      "enum": [
        "preserve",
        "improve",
        "redesign"
      ],
      "type": "string",
      "description": "Migration approach. Preserve keeps the existing website presentation as faithfully as possible. Improve preserves the source as an editable baseline for deliberate improvements. Panderr Redesign creates a new design direction using the existing website content, business information, and assets as its source."
    },
    "websiteUrl": {
      "type": "string",
      "minLength": 1,
      "description": "The public website address to migrate."
    }
  }
}
    arguments 23 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 28078e16a46f83d1.

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

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.