CONTRI
NPM · CONTRI-MCP
Is this GitHub issue free to take, is the project alive, will maintainers reply? Read-only.
Available components
Last scanned (6 minutes ago)
Scores higher than 50% of npm servers
Category Version Control
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
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1174 tokens (~130/item across 9 items; 9 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +2
- Stability: unverified → 0.10 ▲ functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 56
First indexed and scored.
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 5 Nov 2026 · Analysed npm/contri-mcp@0.2.0
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 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
check_issue Can I take this issue? ~151
Is this issue free to take? One verdict (Looks free, Claimed by @x, Claim went quiet, Open PR #n, Assigned, Closed, Partly checked) from assignees, claim comments and referencing PRs, with evidence links. 1–2 requests signed in, ~4 anonymous.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | brief: verdict + URL (~40 tokens); full: with evidence |
| force | boolean | – | Bypass the cache (costs requests) |
| includeThread | boolean | – | Also return issue text and recent comments (up to ~14k chars) |
| issue | string | yes | https://github.com/owner/name/issues/123 or owner/name#123 |
No output schema declared.
No examples provided.
check_issues Can I take any of these issues? ~74
check_issue for up to 10 issues in one call, verdicts only by default. Same cost per issue.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | brief: verdict + URL (~40 tokens); full: with evidence |
| force | boolean | – | Bypass the cache (costs requests) |
| issues | array | yes | – |
No output schema declared.
No examples provided.
contribution_brief Contribution brief ~95
A source-linked brief for one issue plus links to the project's README, contributing guide, code of conduct and templates. One request more than check_issue.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Bypass the cache (costs requests) |
| issue | string | yes | https://github.com/owner/name/issues/123 or owner/name#123 |
| task | string | – | plan (default), explain, or review (self-review checklist) |
No output schema declared.
No examples provided.
discover_projects Discover projects ~100
Active public projects ranked by recent human merges and open good-first-issues, by language or topic. 1 request per language signed in, ~7 anonymous.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Bypass the cache (costs requests) |
| language | string | – | e.g. TypeScript, Python, Rust |
| personalize | boolean | – | Match the signed-in user's languages |
| query | string | – | Topic words, e.g. cli, accessibility |
No output schema declared.
No examples provided.
find_issues Find issues to take ~141
Open issues in one repository, newest activity first; defaults to beginner labels without an assignee. Comment claims are not checked: confirm with check_issue(s). 3 requests signed in, 2 anonymous.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Bypass the cache (costs requests) |
| label | string | – | default beginner = good first issue or help wanted |
| limit | integer | – | default 10 |
| page | integer | – | – |
| query | string | – | Search words (no qualifiers) |
| repo | string | yes | owner/name or a github.com URL |
| sort | string | – | – |
| unassigned | boolean | – | default true |
No output schema declared.
No examples provided.
repo_health Is this project alive? ~82
Is the project alive? PRs merged in 90 days (bots excluded), human authors, commits, weekly merges, median time to merge, open counts, latest release. 2 requests signed in, ~7 anonymous.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Bypass the cache (costs requests) |
| repo | string | yes | owner/name or a github.com URL |
No output schema declared.
No examples provided.
sign_in Sign in with GitHub ~75
GitHub device-flow sign-in (60 → 5,000 requests an hour, public read-only, no scopes). Ask the user first. Show the returned code and link exactly; CONTRI notices the approval by itself. Call again to check.
| Name | Type | Req | Description |
|---|---|---|---|
| remember | boolean | – | Keep the sign-in on this computer (default true) |
No output schema declared.
No examples provided.
sign_out Sign out of GitHub ~33
Forgets the sign_in credential, including the saved copy. A GITHUB_TOKEN in the MCP config must be removed there.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
team_responsiveness Will a maintainer reply? ~94
Will a maintainer reply? Median first team reply to outside PRs and issues, who is still waiting, and the maintainer roster. Call once per repository before check_issue: it improves claim detection. 2–3 requests signed in, up to ~35 anonymous.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Bypass the cache (costs requests) |
| repo | string | yes | owner/name or a github.com URL |
No output schema declared.
No examples provided.
How do I install the CONTRI MCP server?
CONTRI runs locally as an npm package, launched with npx -y contri-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · contri-mcp
claude mcp add alphasafal-contri -- npx -y contri-mcp
What is the CONTRI MCP server?
CONTRI is an MCP server listed in the public MCP registry as io.github.alphasafal/contri. Is this GitHub issue free to take, is the project alive, will maintainers reply? Read-only. This page covers its npm package (contri-mcp).
Is the CONTRI MCP server safe to use?
CONTRI scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 CONTRI MCP server expose?
CONTRI exposes 9 tools: check_issue, check_issues, repo_health, team_responsiveness, find_issues, and 4 more. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.
Is the CONTRI MCP server still maintained?
CONTRI is still listed as active in the MCP registry. We last reached this channel on 5 November 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 CONTRI MCP server under?
CONTRI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.