io.github.mrkeyoor/should-i-use
NPM · SHOULD-I-USE-MCP · 2 COMPONENTS
Honest library picks for coding agents in 25-360 tokens. Tells your agent what NOT to install.
Available components
Last scanned (15 hours ago)
Scores higher than 87% of npm servers
Category Developer Tools
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 80 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 442 tokens (~73/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
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/should-i-use-mcp@0.3.2
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
alternatives ~50
Curated alternatives to a library, each with a one-line "prefer it when" and a verdict if the alternative is also indexed.
| Name | Type | Req | Description |
|---|---|---|---|
| library | string | yes | Library name as published on npm or PyPI |
No output schema declared.
No examples provided.
audit_dependencies ~111
Audit a project's dependencies for unmaintained packages, unstable APIs, and documented reasons to switch. Pass the contents of package.json, requirements.txt, or pyproject.toml. Returns only the dependencies worth a decision, not a report on every line. Run this before working in an unfamiliar codebase.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Optional hint when the manifest format is ambiguous |
| manifest | string | yes | Contents of package.json, requirements.txt, pyproject.toml, or a newline-separated list of package names |
No output schema declared.
No examples provided.
docs_link ~64
Official docs URL and GitHub repo for a library, one line each. Use when the clamped answers are not enough.
| Name | Type | Req | Description |
|---|---|---|---|
| library | string | yes | Library name as published on npm or PyPI |
| topic | string | – | Optional topic to look up in the docs |
No output schema declared.
No examples provided.
how_do_i ~87
Return the 1-2 best code snippets for a task with a library, plus the gotcha for each. Snippets are correct for the indexed version. Far cheaper in tokens than a docs dump.
| Name | Type | Req | Description |
|---|---|---|---|
| library | string | yes | Library name as published on npm or PyPI |
| task | string | yes | What you want to do, e.g. "retry a failed request" |
No output schema declared.
No examples provided.
pick_library ~76
Given a coding task, recommend 1-3 libraries from the should-i-use index with one-line reasoning and an honest warning about the top pick. Use before installing anything.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Optional registry filter |
| task | string | yes | What you are trying to do, e.g. "parse CSV files in node" |
No output schema declared.
No examples provided.
should_i_use ~54
Honest verdict on a specific library: 4-axis scores with reasons, when to skip it, and maintenance signals (last push, weekly downloads).
| Name | Type | Req | Description |
|---|---|---|---|
| library | string | yes | Library name as published on npm or PyPI |
No output schema declared.
No examples provided.
How do I install the io.github.mrkeyoor/should-i-use MCP server?
io.github.mrkeyoor/should-i-use runs locally as an npm package, launched with npx -y should-i-use-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 · should-i-use-mcp
claude mcp add mrkeyoor-should-i-use -- npx -y should-i-use-mcp
What is the io.github.mrkeyoor/should-i-use MCP server?
io.github.mrkeyoor/should-i-use is an MCP server listed in the public MCP registry as io.github.mrkeyoor/should-i-use. Honest library picks for coding agents in 25-360 tokens. Tells your agent what NOT to install. This page covers its npm package (should-i-use-mcp).
Is the io.github.mrkeyoor/should-i-use MCP server safe to use?
io.github.mrkeyoor/should-i-use scores 85 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 io.github.mrkeyoor/should-i-use MCP server expose?
io.github.mrkeyoor/should-i-use exposes 6 tools: pick_library, should_i_use, alternatives, how_do_i, audit_dependencies, docs_link. Their descriptions and schemas cost roughly 442 tokens of context every time the server is loaded.
Is the io.github.mrkeyoor/should-i-use MCP server still maintained?
io.github.mrkeyoor/should-i-use 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 io.github.mrkeyoor/should-i-use MCP server under?
io.github.mrkeyoor/should-i-use declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.mrkeyoor/should-i-use MCP server?
VerifyMCP ran 16 checks on io.github.mrkeyoor/should-i-use, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.