io.github.Cranot/agentskb

MCPcommunity
v0.1.1io.github.CranotUnknownUpdated 10mo agonpmGitHub

Researched knowledge for AI agents. Canonical answers from official sources.

Verified knowledge that stops AI coding assistant hallucinations. Your AI coding assistant (Cursor, Claude Code, Cline) is great at common tasks. But ask about specific details and it often guesses wrong: Wrong default values ("PostgreSQL maxconnections is 200" - actually 100) Outdated version info ("Use getInitialProps" - deprecated in Next.js App Router) Incorrect specifications ("JWT should…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). 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 →
9GitHub stars
3Forks
10mo agoLast update
Package
Authorio.github.Cranot
LicenseUnknown
Version0.1.1
Sourcemcp-registry
Trust Status
B
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 surface—
Security scan✓ Cleanv0.1.0-beta.8 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

No tool declarations found in the source3mo ago

Forge read 34 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Verified knowledge that stops AI coding assistant hallucinations. Your AI coding assistant (Cursor, Claude Code, Cline) is great at common tasks. But ask about specific details and it often guesses wrong: Wrong default values ("PostgreSQL max_connections is 200" - actually 100) Outdated version info ("Use getInitialProps" - deprecated in Next.js App Router) Incorrect specifications ("JWT should expire in 1 hour" - OWASP says 15 minutes) The result: You waste 30+ minutes in retry loops,…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.