Chapa
REMOTE · CHAPA.THECREATIVETOKEN.COM
Read, compare, and verify public developer impact profiles and Chapa badges.
Available components
Last scanned (2 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 338 tokens (~37/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 0
- Server version: 4.10.0 → 4.11.2 functional
- 1 Nov 26 0
- Server version: 4.9.3 → 4.10.0 functional
- 28 Oct 26 0
- Server version: 4.9.2 → 4.9.3 functional
- 26 Oct 26 0
- Server version: 4.9.0 → 4.9.2 functional
- 12 Oct 26 0
- Server version: 4.8.0 → 4.9.0 functional
- 10 Oct 26 +1
- Tool “get_impact_profile” rewrote its description, which is the text the model reads security
- Server version: 4.7.3 → 4.8.0 functional
- 3 Oct 26 0
- Tool “explain_dimension” rewrote its description, which is the text the model reads security
- Tool “get_impact_profile” rewrote its description, which is the text the model reads security
- Server version: 4.3.0 → 4.4.0 functional
- 1 Oct 26 82
- Stability: 0.97 → pass security
- Tool “explain_dimension” rewrote its description, which is the text the model reads security
- Tool “get_impact_history” rewrote its description, which is the text the model reads security
- Tool “get_impact_profile” rewrote its description, which is the text the model reads security
- Schema quality: good → fair functional
- Server version: 4.2.0 → 4.3.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://chapa.thecreativetoken.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chapa.thecreativetoken.com | CN=YR1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 57c8d0ad146ea7e539720464248efb5a47b |
| SANs: chapa.thecreativetoken.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of chapa.thecreativetoken.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| thecreativetoken.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' blob: https://eu-assets.i.posthog.com; worker-src 'self' blob:; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://avatars.githubusercontent.com https://i.ytimg.com; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://eu.i.posthog.com https://eu-assets.i.posthog.com https://api.github.com https://cdn.jsdelivr.net https://va.vercel-scripts.com; frame-src https://www.youtube-nocookie.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chapa.thecreativetoken.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://chapa.thecreativetoken.com/api/mcp | HTTPS enforced | 308 | https://chapa.thecreativetoken.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_profiles ~37
Compare two public Chapa impact profiles by the headline each badge draws.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
| other_handle | string | yes | – |
No output schema declared.
No examples provided.
explain_dimension ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | string | yes | – |
| handle | string | yes | – |
No output schema declared.
No examples provided.
explain_verification ~18
Explain Chapa badge verification guarantees and limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_profile ~29
Resolve a GitHub handle to its Chapa profile and badge URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
No output schema declared.
No examples provided.
get_embed_snippet ~32
Return ready-to-paste Markdown and HTML for a live Chapa badge.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
No output schema declared.
No examples provided.
get_impact_history ~39
Return policy-labelled daily receipt winners and trends for a GitHub handle, including the desired policy and upgrade state.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
No output schema declared.
No examples provided.
get_impact_profile ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
No output schema declared.
No examples provided.
get_site_capabilities ~23
Describe Chapa and list its agent-facing tools and entry points.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_badge ~29
Look up the public verification result for a Chapa badge hash.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Chapa MCP server?
Chapa is a hosted endpoint at https://chapa.thecreativetoken.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · chapa.thecreativetoken.com
claude mcp add --transport http juan294-chapa 'https://chapa.thecreativetoken.com/api/mcp'
What is the Chapa MCP server?
Chapa is an MCP server listed in the public MCP registry as io.github.juan294/chapa. Read, compare, and verify public developer impact profiles and Chapa badges. This page covers its hosted endpoint (https://chapa.thecreativetoken.com/api/mcp).
Is the Chapa MCP server safe to use?
Chapa scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Chapa MCP server expose?
Chapa exposes 9 tools: get_site_capabilities, find_profile, get_impact_profile, get_impact_history, verify_badge, and 4 more. Their descriptions and schemas cost roughly 338 tokens of context every time the server is loaded.
Does the Chapa MCP server require authentication?
No. We connected to Chapa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chapa MCP server still maintained?
Chapa is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.