should-i-use-mcp

Name: should-i-use-mcp
Author: io.github.mrkeyoor

MCPcommunitylive

v0.3.2io.github.mrkeyoorUnknownUpdated 1mo agonpm GitHub

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

Endpoint healthlive

checked 5 days ago · 1378ms

100% of the last 4 checks reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1mo agoLast update

Package

Authorio.github.mrkeyoor

LicenseUnknown

Version0.3.2

Sourcenpm+mcp-registry

npmshould-i-use-mcp

GitHubmrkeyoor/should-i-use

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface6 tools · none privileged

Security scan✓ Cleanv0.3.3 · 1mo agoHow well does this scan work?

EvalsNone

IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged

Statically extracted from the published packagev0.3.3 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

pick_libraryNo description published