io.github.eliottreich/taskbounty-check
NPM · TASKBOUNTY-CHECK · SCANNED SEP 20
Local GitHub Actions/CI maintenance check (action pinning, token perms). Not a full security audit.
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to eliottreich/taskbounty-check). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 90 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 225 tokens (~75/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.eliottreich/taskbounty-check MCP server?
io.github.eliottreich/taskbounty-check runs locally as an npm package, launched with npx -y taskbounty-check. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · taskbounty-check
claude mcp add eliottreich-taskbounty-check -- npx -y taskbounty-check
{
"mcpServers": {
"eliottreich-taskbounty-check": {
"command": "npx",
"args": [
"-y",
"taskbounty-check"
]
}
}
} {
"servers": {
"eliottreich-taskbounty-check": {
"command": "npx",
"args": [
"-y",
"taskbounty-check"
]
}
}
} codex mcp add eliottreich-taskbounty-check -- npx -y taskbounty-check
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"eliottreich-taskbounty-check": {
"type": "local",
"command": [
"npx",
"-y",
"taskbounty-check"
],
"enabled": true
}
}
} openclaw mcp add eliottreich-taskbounty-check --command npx --arg -y --arg taskbounty-check
mcp_servers:
eliottreich-taskbounty-check:
command: "npx"
args: ["-y", "taskbounty-check"] {
"McpServers": {
"eliottreich-taskbounty-check": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"taskbounty-check"
]
}
}
} assistant mcp add eliottreich-taskbounty-check -t stdio -c npx -a -y taskbounty-check
{
"mcpServers": {
"eliottreich-taskbounty-check": {
"command": "npx",
"args": [
"-y",
"taskbounty-check"
]
}
}
} 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.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 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.
- 15 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −4
- Stability: pass → 0.77 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 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 20 Sept 2026 · Analysed npm/taskbounty-check@0.1.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | eliottreich/taskbounty-check |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/eliottreich/taskbounty-check/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 1897507117 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:78e638a7482987a4c5d7cca0ea1a5701dc0eb30c5eb0e189ac18987275c3438b723b350aaaa35aa3b12a6b2c4de1b88acb59f68815bdec1d1429ae8f6 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
explain_finding ~77
Explain what a finding means and why it matters, in plain language. Pass the rule id (e.g. unpinned-action) or a category. No network, no file access.
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | Rule id, e.g. unpinned-action, broad-permissions, no-permissions-block, script-injection. |
No output schema declared.
No examples provided.
generate_fix_plan ~73
Return a step-by-step fix plan as TEXT for a given rule (and optionally a local repo path for context). It NEVER modifies files; the user applies changes explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Optional local repo path for context (read-only). |
| rule | string | – | Rule id to plan a fix for. |
No output schema declared.
No examples provided.
scan_repo ~75
Scan a LOCAL repository for GitHub Actions + CI maintenance hygiene. Reads only workflow files on disk; makes no network requests and uploads nothing. Returns a text summary of findings by category with file/line and suggested fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Local path to a repo or a directory of repos. Defaults to the current directory. |
No output schema declared.
No examples provided.
What is the io.github.eliottreich/taskbounty-check MCP server?
io.github.eliottreich/taskbounty-check is an MCP server listed in the public MCP registry as io.github.eliottreich/taskbounty-check. Local GitHub Actions/CI maintenance check (action pinning, token perms). Not a full security audit. This page covers its npm package (taskbounty-check).
Is the io.github.eliottreich/taskbounty-check MCP server safe to use?
io.github.eliottreich/taskbounty-check scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.eliottreich/taskbounty-check MCP server expose?
io.github.eliottreich/taskbounty-check exposes 3 tools: scan_repo, explain_finding, generate_fix_plan. Their descriptions and schemas cost roughly 225 tokens of context every time the server is loaded.
Is the io.github.eliottreich/taskbounty-check MCP server still maintained?
io.github.eliottreich/taskbounty-check is still listed as active in the MCP registry. We last reached this channel on 20 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.eliottreich/taskbounty-check MCP server under?
io.github.eliottreich/taskbounty-check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.