io.github.Valyay/nanostores-mcp

MCPattested
v0.1.2io.github.ValyayUnknownUpdated 5mo agonpmGitHub

Debug and analyze Nanostores apps with AI: scan stores, monitor runtime events, and search docs.

Model Context Protocol server for Nanostores — analyze, debug and monitor your nanostores in AI assistants like Claude Desktop. 📊 Static Analysis: AST-based project scanning, dependency graphs, store inspection 🔥 Runtime Monitoring: Live events from , performance metrics, activity tracking 📚 Documentation: Search and browse Nanostores docs by topic or store kind 🎯 Zero Config: Works out of…

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
1GitHub stars
5mo agoLast update
Package
Authorio.github.Valyay
LicenseUnknown
Version0.1.2
Sourcemcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—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)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 9a48a35
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv0.1.2 · 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 116 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

Model Context Protocol server for Nanostores — analyze, debug and monitor your nanostores in AI assistants like Claude Desktop. 📊 Static Analysis: AST-based project scanning, dependency graphs, store inspection 🔥 Runtime Monitoring: Live events from , performance metrics, activity tracking 📚 Documentation: Search and browse Nanostores docs by topic or store kind 🎯 Zero Config: Works out of the box — auto-detects project roots and nanostores docs 🌐 Framework-Agnostic: Works with React, Vue,…

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.