Developer · Remote MCP server
Should I Use
Honest library picks for coding agents in 25-360 tokens. Tells your agent what NOT to install.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mrkeyoor/should-i-use- Version
- 0.3.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-10
- Updated
- 2026-08-10
- Publisher
- mrkeyoor (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mrkeyoor) · how
- Website
- mrkeyoor.com/libs/
- Repository
- github.com/mrkeyoor/should-i-use
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mrkeyoor.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- should-i-use 0.3.3 · protocol 2025-06-18
- Tools discovered
- 6:
pick_library,should_i_use,alternatives,how_do_i,audit_dependencies,docs_link - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | should-i-use-mcp | 0.3.2 | stdio |
How to connect Should I Use
Should I Use is a remote MCP server: there is nothing to install. Its endpoint is https://mrkeyoor.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: should-i-use-mcp version 0.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y should-i-use-mcp@0.3.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"should-i-use": {
"command": "npx",
"args": [
"-y",
"should-i-use-mcp@0.3.2"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Shipswiftcomponents MCPA paid remote MCP for ShipSwift, built to return verdicts, receipts, usage logs, and audit-ready JSO. | Remote · HTTPLive check: ✗ no handshake |
| ShodanMCP server for Shodan API - device search, IP lookup, DNS, and CVE/CPE queries. | Local · stdio |
| Shoon A2A Trust Services (pilot)Five trust services for agents: claim checks, citation audits, extraction, tripwires, work audits. | Remote · HTTPLive check: ✓ handshake |
| ShotPulledEspresso dialing: log a shot, say how it tasted, get one change in your grinder's own clicks. | Remote · HTTPLive check: ✓ handshake |
| showagentSearch, resume and convert AI coding sessions (Claude Code, Codex, Gemini, OpenCode, Pi) over MCP. | Local · stdio |
| SHPBL: Repository Audit & RepairAudit and repair any public GitHub repo. Free survey; paid source, unified diffs and a pull request. | Remote · HTTPLive check: ✓ handshake |
| ShrikeGoverns what AI agents do: tool calls, SQL, commands, files checked against policy before they run. | Local · stdio |
| ShuttleAndroid framework and solution that prevents TransactionTooLargeException crashes by design. | Local · stdio |