# io.github.mrkeyoor/should-i-use (npm · should-i-use-mcp)

Honest library picks for coding agents in 25-360 tokens. Tells your agent what NOT to install.

- Trust score: 84/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mrkeyoor.com`: 88/100, [markdown](https://verifymcp.io/servers/mrkeyoor-should-i-use/mrkeyoor.md), [page](https://verifymcp.io/servers/mrkeyoor-should-i-use/mrkeyoor)
- npm · `should-i-use-mcp`: 84/100 (this document), [markdown](https://verifymcp.io/servers/mrkeyoor-should-i-use/should-i-use-mcp.md), [page](https://verifymcp.io/servers/mrkeyoor-should-i-use/should-i-use-mcp)

## Channel facts

- Registry: `npm`
- Package: `should-i-use-mcp`
- Version: `0.3.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 35 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 442 tokens (~73/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add mrkeyoor-should-i-use -- npx -y should-i-use-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrkeyoor-should-i-use": {
      "command": "npx",
      "args": [
        "-y",
        "should-i-use-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrkeyoor-should-i-use": {
      "command": "npx",
      "args": [
        "-y",
        "should-i-use-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrkeyoor-should-i-use -- npx -y should-i-use-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrkeyoor-should-i-use": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "should-i-use-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrkeyoor-should-i-use --command npx --arg -y --arg should-i-use-mcp
```

### Hermes

```yaml
mcp_servers:
  mrkeyoor-should-i-use:
    command: "npx"
    args: ["-y", "should-i-use-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrkeyoor-should-i-use": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "should-i-use-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrkeyoor-should-i-use -t stdio -c npx -a -y should-i-use-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrkeyoor-should-i-use": {
      "command": "npx",
      "args": [
        "-y",
        "should-i-use-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 84, +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.

### 2026-09-19 (score 83, +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.

### 2026-09-17 (score 82, −3)

- [functional] Stability: pass → 0.80

### 2026-09-16 (score 85, +1)

- [security] Stability: 0.97 → pass

### 2026-09-14 (score 84, +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.

### 2026-09-12 (score 83, +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.

### 2026-09-10 (score 82, −3)

- [functional] Stability: pass → 0.80

### 2026-09-09 (score 85, +1)

- [security] Stability: 0.97 → pass

## MCP tools (6)

### `pick_library` (~76 tokens)

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.

Input parameters:

- `ecosystem` (string): Optional registry filter
- `task` (string, required): What you are trying to do, e.g. "parse CSV files in node"

### `should_i_use` (~54 tokens)

Honest verdict on a specific library: 4-axis scores with reasons, when to skip it, and maintenance signals (last push, weekly downloads).

Input parameters:

- `library` (string, required): Library name as published on npm or PyPI

### `alternatives` (~50 tokens)

Curated alternatives to a library, each with a one-line "prefer it when" and a verdict if the alternative is also indexed.

Input parameters:

- `library` (string, required): Library name as published on npm or PyPI

### `how_do_i` (~87 tokens)

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.

Input parameters:

- `library` (string, required): Library name as published on npm or PyPI
- `task` (string, required): What you want to do, e.g. "retry a failed request"

### `audit_dependencies` (~111 tokens)

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.

Input parameters:

- `ecosystem` (string): Optional hint when the manifest format is ambiguous
- `manifest` (string, required): Contents of package.json, requirements.txt, pyproject.toml, or a newline-separated list of package names

### `docs_link` (~64 tokens)

Official docs URL and GitHub repo for a library, one line each. Use when the clamped answers are not enough.

Input parameters:

- `library` (string, required): Library name as published on npm or PyPI
- `topic` (string): Optional topic to look up in the docs

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrkeyoor-should-i-use/should-i-use-mcp#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 82
- 2026-09-10: 82
- 2026-09-09: 85
- 2026-09-08: 84
- 2026-09-07: 84
- 2026-09-06: 83
- 2026-09-05: 83
- 2026-09-04: 82
- 2026-09-03: 82
- 2026-09-02: 82
- 2026-09-01: 81
- 2026-08-31: 81
- 2026-08-30: 80
- 2026-08-29: 80
- 2026-08-28: 79
- 2026-08-27: 79
- 2026-08-26: 78
- 2026-08-25: 77
- 2026-08-24: 76
- 2026-08-23: 76

## Common questions

### 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 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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.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 21 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.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.

## Links

- npm package: https://www.npmjs.com/package/should-i-use-mcp
- Socket report: https://socket.dev/npm/package/should-i-use-mcp
- Repository: https://github.com/mrkeyoor/should-i-use
- Website: https://mrkeyoor.com/libs/
- Changelog RSS feed: https://verifymcp.io/servers/mrkeyoor-should-i-use/should-i-use-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrkeyoor-should-i-use/should-i-use-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrkeyoor-should-i-use/should-i-use-mcp