Nine read-only tools for Chapa developer Impact Profiles, history, badge verification, dimension explanations, profile comparisons, and embed snippets.
Scored across 9 tools
Most tools target distinct resources/actions, but the profile-related trio (find_profile, get_impact_profile, get_impact_history, compare_profiles) shares the same subject and could be confused at selection time. The explain_dimension/explain_verification/get_site_capabilities meta-tools also overlap slightly in tone, though descriptions clarify each.
All nine tools follow a clean snake_case verb_noun pattern (compare_profiles, find_profile, get_impact_profile, verify_badge, etc.). No mixed conventions or vague single-word names.
Nine tools is a well-scoped count for a badge/impact-profile server, with each operation earning its place (profile lookup, history, comparison, verification, embedding, explanations).
Coverage spans discovery (find_profile), retrieval (get_impact_profile/history), comparison, verification, embedding, and meta-explanation, forming a coherent lifecycle. Minor gaps like no bulk listing or search of profiles, but core workflows are covered.
Compare two public Chapa impact profiles by the headline each badge draws.
Inputs: handle (required), other_handle (required).
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.
Inputs: handle (required), dimension (required).
Explain Chapa badge verification guarantees and limits.
Inputs: no named parameters.
Resolve a GitHub handle to its Chapa profile and badge URLs.
Inputs: handle (required).
Return ready-to-paste Markdown and HTML for a live Chapa badge.
Inputs: handle (required).
Return policy-labelled daily receipt winners and trends for a GitHub handle, including the desired policy and upgrade state.
Inputs: handle (required).
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.
Inputs: handle (required).
Describe Chapa and list its agent-facing tools and entry points.
Inputs: no named parameters.
Look up the public verification result for a Chapa badge hash.
Inputs: hash (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.