Chapa MCP server
io.github.juan294/chapajuan294streamable-httpv2.29.1Scanned
Read, compare, and verify public developer impact profiles and Chapa badges.
9 tools: 1 change things and 8 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Chapa MCP server can do
The Chapa MCP server is published by the GitHub account juan294. It has 9 tools. It can create or change data (1 tool: verify_badge), but cannot delete data. 8 tools only read.
1 tool brings in text other people can write (get_embed_snippet).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 2.29.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 1Claude Code: ask
verify_badgeLook up the public verification result for a Chapa badge hash.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Look up the public verification result for a Chapa badge hash.
Annotations the server declares
- readOnlyHint: true
- untrustedContentHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 8Show 8 read-only tools
compare_profilesCompare two public Chapa impact profiles by the headline each badge draws.No findings
Why it is in this group
- The name "compare_profiles" says "compare": a word for reading.
Description, as the server wrote it Compare two public Chapa impact profiles by the headline each badge draws.
Annotations the server declares
- readOnlyHint: true
- untrustedContentHint: true
- destructiveHint: false
- openWorldHint: false
explain_dimensionExplain 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.No findings
Why it is in this group
- The name "explain_dimension" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- untrustedContentHint: true
- destructiveHint: false
- openWorldHint: false
explain_verificationExplain Chapa badge verification guarantees and limits.No findings
Why it is in this group
- The name "explain_verification" says "explain": a word for reading.
Description, as the server wrote it Explain Chapa badge verification guarantees and limits.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
find_profileResolve a GitHub handle to its Chapa profile and badge URLs.No findings
Why it is in this group
- The name "find_profile" says "find": a word for reading.
Description, as the server wrote it Resolve a GitHub handle to its Chapa profile and badge URLs.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_embed_snippetReturn ready-to-paste Markdown and HTML for a live Chapa badge.Reads text others writeNo findings
Why it is in this group
- The name "get_embed_snippet" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "html": it reads web pages, which anyone can write.
Description, as the server wrote it Return ready-to-paste Markdown and HTML for a live Chapa badge.
Annotations the server declares
- readOnlyHint: true
- untrustedContentHint: true
- destructiveHint: false
- openWorldHint: false
get_impact_historyReturn policy-labelled daily receipt winners and trends for a GitHub handle, including the desired policy and upgrade state.No findings
Why it is in this group
- The name "get_impact_history" says "get": a word for reading.
Description, as the server wrote it Return policy-labelled daily receipt winners and trends for a GitHub handle, including the desired policy and upgrade state.
Annotations the server declares
- readOnlyHint: true
- untrustedContentHint: true
- destructiveHint: false
- openWorldHint: false
get_impact_profileReturn 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 Qual…No findings
Why it is in this group
- The name "get_impact_profile" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- untrustedContentHint: true
- destructiveHint: false
- openWorldHint: false
get_site_capabilitiesDescribe Chapa and list its agent-facing tools and entry points.No findings
Why it is in this group
- The name "get_site_capabilities" says "get": a word for reading.
Description, as the server wrote it Describe Chapa and list its agent-facing tools and entry points.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://chapa.thecreativetoken.com/api/mcp: tools/list returned 9 tools to an anonymous client, including verify_badge (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 2.29.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http chapa https://chapa.thecreativetoken.com/api/mcpclaude mcp add --transport http chapa https://chapa.thecreativetoken.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__chapa__get_site_capabilities",
"mcp__chapa__find_profile",
"mcp__chapa__get_impact_profile",
"mcp__chapa__get_impact_history",
"mcp__chapa__explain_verification",
"mcp__chapa__explain_dimension",
"mcp__chapa__compare_profiles",
"mcp__chapa__get_embed_snippet"
],
"ask": [
"mcp__chapa__verify_badge"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as chapa. Review it before you use it.
Capability tags behind 1 rule
- mcp__chapa__get_embed_snippet untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.juan294/chapa/verify?hash=0de5e028302e1c2adb5b0c28965021d112e89c0a90131193c8575abe250234f6" | jq -e '.changed == false'Pinned hash 0de5e028302e, from Nov 19, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.juan294/chapa/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.juan294/chapa)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.
Chapa MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Chapa MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Chapa MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Chapa MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Chapa MCP server have?
- 9 tools: 1 write, 8 read. verify_badge, get_site_capabilities, find_profile, get_impact_profile, get_impact_history, explain_verification, explain_dimension, compare_profiles and 1 more.
Does the Chapa MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Chapa MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Chapa MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.