chapa
https://chapa.thecreativetoken.com
Registry code: 120710b2f284d8a3
Read, compare, and verify public developer impact profiles and Chapa badges.
from a public catalogue that lists it, not from the operator
- endpoint
- https://chapa.thecreativetoken.com/api/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 chapa live?
- Yes — it answered the hub's last check (checked 10m ago). It answered 99% of checks over the last 30 days.
- Is chapa free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does chapa have?
- 9 tools: verify_badge, get_impact_profile, compare_profiles, find_profile, get_embed_snippet, get_impact_history, explain_dimension, explain_verification, ….
- Is chapa 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 98.8%· all time 98.8%
last good check
of 9 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get developer impact profile
- compare github developer profiles
- verify a badge
- get badge embed snippet
- takes → gives
- text → data
- tools
- 9 reads
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
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.
explain_verification reads open 14h ago
Explain Chapa badge verification guarantees and limits.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_site_capabilities reads open 14h ago
Describe Chapa and list its agent-facing tools and entry points.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesverify_badge reads unknown 6h ago
Look up the public verification result for a Chapa badge hash.
{ "type": "object", "required": [ "hash" ], "properties": { "hash": { "type": "string", "pattern": "^(?:[0-9a-f]{8}|[0-9a-f]{16}|[0-9a-f]{32}|v7\\.[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}\\.[0-9a-f]{64})$" } }, "additionalProperties": false }arguments 13 linesget_impact_profile reads unknown 6h ago
Return the selected policy receipt, including v7.4 or v7.5 recorded activity and product outcomes for a GitHub handle, including its policy, identity, exact/display points and Quality breakdown. When no receipt is drawable, return scoringStatus and the initial Emerging archetype for registered users.
{ "type": "object", "required": [ "handle" ], "properties": { "handle": { "type": "string" } }, "additionalProperties": false }arguments 12 linescompare_profiles reads unknown 6h ago
Compare two public Chapa impact profiles by the headline each badge draws.
{ "type": "object", "required": [ "handle", "other_handle" ], "properties": { "handle": { "type": "string" }, "other_handle": { "type": "string" } }, "additionalProperties": false }arguments 16 linesfind_profile reads unknown 9h ago
Resolve a GitHub handle to its Chapa profile and badge URLs.
{ "type": "object", "required": [ "handle" ], "properties": { "handle": { "type": "string" } }, "additionalProperties": false }arguments 12 linesget_embed_snippet reads unknown 9h ago
Return ready-to-paste Markdown and HTML for a live Chapa badge.
{ "type": "object", "required": [ "handle" ], "properties": { "handle": { "type": "string" } }, "additionalProperties": false }arguments 12 linesget_impact_history reads unknown 9h ago
Return policy-labelled daily receipt winners and trends for a GitHub handle, including the desired policy and upgrade state.
{ "type": "object", "required": [ "handle" ], "properties": { "handle": { "type": "string" } }, "additionalProperties": false }arguments 12 linesexplain_dimension reads unknown 14h ago
Explain one impact dimension from the selected policy receipt, including sealed v7.4 or v7.5 contributions and outcome availability, automatic Quality and optional reviewed bonus.
{ "type": "object", "required": [ "handle", "dimension" ], "properties": { "handle": { "type": "string" }, "dimension": { "enum": [ "delivery", "quality", "consistency", "breadth", "craft" ], "type": "string" } }, "additionalProperties": false }arguments 23 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 id120710b2f284d8a3.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/120710b2f284d8a3/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/120710b2f284d8a3?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.