Developer · Remote MCP server
Chapa
Read, compare, and verify public developer impact profiles and Chapa badges.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.juan294/chapa- Version
- 2.29.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-01
- Updated
- 2026-09-01
- Publisher
- juan294 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/juan294) · how
- Repository
- github.com/juan294/chapa
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://chapa.thecreativetoken.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- chapa 4.5.0 · protocol 2025-06-18
- Tools discovered
- 9:
get_site_capabilities,find_profile,get_impact_profile,get_impact_history,verify_badge,explain_verification,explain_dimension,compare_profiles,get_embed_snippet - Checked on
- 2026-10-05
How to connect Chapa
Chapa is a remote MCP server: there is nothing to install. Its endpoint is https://chapa.thecreativetoken.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ChangeflowAI-powered web monitoring. Track any website, get structured change intelligence. | Local · stdio |
| ChangegamerAgent-first resource directory for AI agents: protocols, security, RAG, memory, evals, and more. | Remote · HTTPLive check: ✓ handshake |
| Changelog Forge MCPGenerate changelogs from git commit history. | Local · stdio |
| changelogaiGenerate changelogs and suggest semver bumps from git history. | Local · stdio |
| ChaprolaServerless API backend: query, JOIN, pivot, batch ops, email, FHIR, programs via HTTP. | Local · stdio |
| chargehandRuns coding-agent workers on a codebase question; every claim in the answer carries evidence. | Local · stdio |
| ChargerDojoOCPI versions, what changed between them, and which modules and journeys ChargerDojo tests. | Remote · HTTPLive check: ✓ handshake |
| ChartwireGenerate chart code (Recharts, Chart.js, ECharts, Plotly) from a prompt. | Remote · HTTPLive check: sign-in required |