designcheck
https://designcheck.allthepossibles.com
Registry code: 714ebbe90bcc3f40
Scores whether a page reads as AI-generated and names the tells to fix.
from a public catalogue that lists it, not from the operator
- endpoint
- https://designcheck.allthepossibles.com/mcp
- protocol
- streamable-http ·2026-03-26
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is designcheck live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is designcheck free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does designcheck have?
- 3 tools: check_copy, check_code, check_design.
- Is designcheck 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.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
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
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
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.
check_copy unknown 2h ago
Check marketing or outreach copy (an email, a landing-page draft, a pitch, a social post) for the tells that make it read as AI-generated: cliché vocabulary (delve, unlock, empower, seamlessly integrate, etc.), negative-parallel framing ("not just X, but Y"), hedge words, heavy em-dash use, and diagnosing a problem with no fix in the same breath. No page or markup needed, just the text. Call this before sending copy to a human.
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string", "description": "The raw copy to check" } } }arguments 12 linescheck_code unknown 2h ago
Check a source file or diff for AI 'tells' left in comments: narrating fulfilling a request instead of describing the code ("as requested," "I've added," "here's the updated version") and hedge words. These reveal there was a conversation behind the change that a later reader has no access to. Call this before committing or shipping code an agent wrote.
{ "type": "object", "required": [ "code" ], "properties": { "code": { "type": "string", "description": "The source file or diff to check" } } }arguments 12 linescheck_design unknown never probed
Check a page's HTML/CSS/copy/interaction for the patterns that make AI-generated work read as generic: default fonts, soft tech gradients, pill+arrow buttons, eyebrow labels, a composition with no real width/background variation across sections, uniform card grids, copy tells (AI vocabulary, negative-parallel framing, hedge words, heavy em-dash use), and experience gaps (a diagnosis with no next step, dead-end links). Every finding includes a concrete fix. Call this before presenting UI to a human.
{ "type": "object", "properties": { "url": { "type": "string", "description": "Page to fetch and check" }, "html": { "type": "string", "description": "Raw HTML/CSS to check directly, if not fetching a URL" } } }arguments 13 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 id714ebbe90bcc3f40.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/714ebbe90bcc3f40/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/714ebbe90bcc3f40?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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- verdict.allthepossibles.com verdict
- preflight.allthepossibles.com preflight
- pulse.allthepossibles.com pulse