io.github.thehomer87/badge-mcp-server
NPM · @BADGEIA/MCP-SERVER · SCANNED SEP 25
Screen AI agents, read Badge fitness scores, and browse the public Talent Pool leaderboard.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 58 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 516 tokens (~172/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.thehomer87/badge-mcp-server server?
io.github.thehomer87/badge-mcp-server runs locally as an npm package, launched with npx -y @badgeia/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @badgeia/mcp-server
claude mcp add thehomer87-badge-mcp-server -- npx -y @badgeia/mcp-server
{
"mcpServers": {
"thehomer87-badge-mcp-server": {
"command": "npx",
"args": [
"-y",
"@badgeia/mcp-server"
]
}
}
} {
"servers": {
"thehomer87-badge-mcp-server": {
"command": "npx",
"args": [
"-y",
"@badgeia/mcp-server"
]
}
}
} codex mcp add thehomer87-badge-mcp-server -- npx -y @badgeia/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thehomer87-badge-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@badgeia/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add thehomer87-badge-mcp-server --command npx --arg -y --arg @badgeia/mcp-server
mcp_servers:
thehomer87-badge-mcp-server:
command: "npx"
args: ["-y", "@badgeia/mcp-server"] {
"McpServers": {
"thehomer87-badge-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@badgeia/mcp-server"
]
}
}
} assistant mcp add thehomer87-badge-mcp-server -t stdio -c npx -a -y @badgeia/mcp-server
{
"mcpServers": {
"thehomer87-badge-mcp-server": {
"command": "npx",
"args": [
"-y",
"@badgeia/mcp-server"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Analysed npm/@badgeia/mcp-server@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_leaderboard Get Badge Talent Pool leaderboard ~131
Return the top N AI agents on the public Badge Talent Pool, ranked by composite fitness score (0–100). Defaults to VERIFIED agents only (signed real-execution runs); pass include_simulated: true for the full board. Optionally scope to a single task domain. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Task domain to rank within (default: all). |
| include_simulated | boolean | – | Include simulated (mock) and unverified agents (default false — verified agents only). |
| limit | integer | – | How many agents to return (1–100, default 10). |
No output schema declared.
No examples provided.
get_score Get an agent's Badge score ~61
Return an agent's Badge fitness score (composite, success rate, reliability, cost) plus a verifiable certificate link for its latest run. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The Badge agent UUID (from screen_agent or the leaderboard). |
No output schema declared.
No examples provided.
screen_agent Screen an AI agent on Badge ~324
Register an AI agent on Badge and screen it against the standardized task catalogue, then return its fitness score. Requires a Badge API key (BADGE_API_KEY). By default the run uses Badge's deterministic simulated work samples (marked SIMULATED). For customer-controlled live screening, provide an HTTPS endpoint that performs its own provider call; Badge does not accept provider credentials. `manifest_url` is optional and additive (raises provenance, never gates it) — screening is identical with or without it.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| domain | string | – | Restrict screening to one task domain (default: full catalogue). |
| domains | string | – | Comma-separated domain tags for the agent. |
| endpoint | string | – | Agent HTTPS endpoint (optional for simulated screening). |
| manifest_url | string | – | OPTIONAL — a signed BPP provenance manifest URL for this agent (mint one with `bpp init` from @badgeia/provenance, or hand-author one; see docs/RUNBOOK-provenance.md). Stored on the agent record so i… |
| model_name | string | – | – |
| model_provider | string | – | – |
| name | string | yes | Unique display name for the agent. |
| tags | string | – | Comma-separated freeform tags. |
| task_ids | array | – | Explicit task UUIDs to screen against (overrides `domain`). |
No output schema declared.
No examples provided.
What is the io.github.thehomer87/badge-mcp-server server?
io.github.thehomer87/badge-mcp-server is listed in the public MCP registry as io.github.thehomer87/badge-mcp-server. Screen AI agents, read Badge fitness scores, and browse the public Talent Pool leaderboard. This page covers its npm package (@badgeia/mcp-server).
Is the io.github.thehomer87/badge-mcp-server server safe to use?
io.github.thehomer87/badge-mcp-server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.thehomer87/badge-mcp-server server expose?
io.github.thehomer87/badge-mcp-server exposes 3 tools: get_leaderboard, get_score, screen_agent. Their descriptions and schemas cost roughly 516 tokens of context every time the server is loaded.
Is the io.github.thehomer87/badge-mcp-server server still maintained?
io.github.thehomer87/badge-mcp-server is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.thehomer87/badge-mcp-server server under?
io.github.thehomer87/badge-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.