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

Reprise — un-flatten any flat AI design (bit-perfect)

https://tepesama-reprise-mcp.hf.space

Registry code: 1a381369eaf183ed

api record

Un-flatten any flat AI design into editable layers, reproduce it bit-perfect, from your agent.

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

endpoint
https://tepesama-reprise-mcp.hf.space/gradio_api/mcp/http
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 Reprise — un-flatten any flat AI design (bit-perfect) live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Reprise — un-flatten any flat AI design (bit-perfect) free to use?
Not measured yet.
What tools does Reprise — un-flatten any flat AI design (bit-perfect) have?
3 tools: autodetect, reproduce, diagnose.
Is Reprise — un-flatten any flat AI design (bit-perfect) 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
313ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 288 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
media generation images
used for
  • split a flat design image into editable layers
  • detect elements in a design image
  • score a reproduction against an original
takes → gives
images → images, data
tools
3 reads
_ 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
3 never probed 0 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.

  • autodetect reads unknown never probed

    Auto-detect the elements (subjects and text) in a design image as relative bounding boxes. Returns: A JSON string with the detected elements (relative bboxes) and their count.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "image": {
      "type": "string",
      "description": "The design image as an http(s) URL or a base64 data URL."
    }
  }
}
    arguments 9 lines
  • reproduce reads unknown never probed

    Un-flatten a flat design image into editable layers and reproduce it bit-perfect, returning the fidelity score. Returns: A JSON string with a bit_perfect flag and fidelity metrics (mae, psnr, exact-match %, stray px).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "image": {
      "type": "string",
      "description": "The source design image as an http(s) URL or a base64 data URL."
    }
  }
}
    arguments 9 lines
  • diagnose reads unknown never probed

    Score how faithfully a reproduction matches an original (MAE / PSNR / exact-match % / stray px). Returns: A JSON string with the fidelity metrics.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "original": {
      "type": "string",
      "description": "The original image as an http(s) URL or a base64 data URL."
    },
    "reproduction": {
      "type": "string",
      "description": "The reproduced image to compare, as an http(s) URL or a base64 data URL."
    }
  }
}
    arguments 13 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 1a381369eaf183ed.

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