io.github.mrkeyoor/should-i-use
REMOTE · MRKEYOOR.COM · 2 COMPONENTS
Honest library picks for coding agents in 25-360 tokens. Tells your agent what NOT to install.
Available components
Last scanned (11 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
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.
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → partial ▲ security
- TLS certificate: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 15 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 · Probed https://mrkeyoor.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mrkeyoor.com | CN=YE2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 63194b7d51e7fa9bbd9b20c94985836eb79 |
| SANs: mrkeyoor.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mrkeyoor.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mrkeyoor.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15768000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mrkeyoor.com/mcp | Verified | 200 | |
| http (plaintext) | http://mrkeyoor.com/mcp | HTTPS enforced | 301 | https://mrkeyoor.com/mcp |
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 Library 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The clamped text answer (hard limit ~500 tokens) |
No examples provided.
audit_dependencies 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The clamped text answer (hard limit ~500 tokens) |
No examples provided.
docs_link 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The clamped text answer (hard limit ~500 tokens) |
No examples provided.
how_do_i How do I do this? ~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" |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The clamped text answer (hard limit ~500 tokens) |
No examples provided.
pick_library Pick a 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" |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The clamped text answer (hard limit ~500 tokens) |
No examples provided.
should_i_use Should I use this library? ~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 |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The clamped text answer (hard limit ~500 tokens) |
No examples provided.
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.
remote · mrkeyoor.com
claude mcp add --transport http mrkeyoor-should-i-use 'https://mrkeyoor.com/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 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.