# io.github.mrkeyoor/should-i-use (remote · mrkeyoor.com)

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

- Trust score: 88/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 (this document), [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, [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

- Endpoint: `https://mrkeyoor.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **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**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 is a hosted endpoint at https://mrkeyoor.com/mcp, so there is nothing to install locally. 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 --transport http mrkeyoor-should-i-use 'https://mrkeyoor.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mrkeyoor-should-i-use": {
      "url": "https://mrkeyoor.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrkeyoor-should-i-use": {
      "type": "http",
      "url": "https://mrkeyoor.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mrkeyoor-should-i-use]
url = "https://mrkeyoor.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrkeyoor-should-i-use": {
      "type": "remote",
      "url": "https://mrkeyoor.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrkeyoor-should-i-use --url 'https://mrkeyoor.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mrkeyoor-should-i-use:
    url: "https://mrkeyoor.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mrkeyoor-should-i-use": {
      "Transport": "http",
      "Url": "https://mrkeyoor.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrkeyoor-should-i-use -t streamable-http -u 'https://mrkeyoor.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mrkeyoor-should-i-use": {
      "type": "http",
      "url": "https://mrkeyoor.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-16 (score 88, 0)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Stability: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-15 (score 88, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-09 (score 88, 0)

- [security] Stability: 0.97 → pass

### 2026-09-08 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 87, +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-03 (score 86, +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.

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

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-30 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `pick_library` (~76 tokens)

Pick a library

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"

Output parameters:

- `answer` (string): The clamped text answer (hard limit ~500 tokens)

### `should_i_use` (~54 tokens)

Should I use this library?

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

Output parameters:

- `answer` (string): The clamped text answer (hard limit ~500 tokens)

### `alternatives` (~50 tokens)

Library alternatives

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

Output parameters:

- `answer` (string): The clamped text answer (hard limit ~500 tokens)

### `how_do_i` (~87 tokens)

How do I do this?

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"

Output parameters:

- `answer` (string): The clamped text answer (hard limit ~500 tokens)

### `audit_dependencies` (~111 tokens)

Audit dependencies

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

Output parameters:

- `answer` (string): The clamped text answer (hard limit ~500 tokens)

### `docs_link` (~64 tokens)

Docs link

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

Output parameters:

- `answer` (string): The clamped text answer (hard limit ~500 tokens)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mrkeyoor-should-i-use/mrkeyoor#diagnostics

## Score history

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

## 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 hosted endpoint (https://mrkeyoor.com/mcp).

### Is the io.github.mrkeyoor/should-i-use MCP server safe to use?

io.github.mrkeyoor/should-i-use scores 88 out of 100 on VerifyMCP. 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.

### Does the io.github.mrkeyoor/should-i-use MCP server require authentication?

No. We connected to io.github.mrkeyoor/should-i-use without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

## Links

- Remote endpoint: https://mrkeyoor.com/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/mrkeyoor.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrkeyoor-should-i-use/mrkeyoor.json
- HTML version of this page: https://verifymcp.io/servers/mrkeyoor-should-i-use/mrkeyoor