io.github.looptech-ai/understand-quickly

MCPattested
v0.1.1io.github.looptech-aiUnknownUpdated 4mo agonpmGitHub

Public registry of code-knowledge graphs for AI agents with schema validation and drift detection.

A thin Model Context Protocol server that exposes the understand-quickly registry to any MCP client (Claude Desktop, Codex, Cursor, etc.). Status: stub-quality. It works end-to-end but is intentionally minimal — no streaming, no embeddings, no auth. It wraps the public and exposes four tools: Tool | Params | Returns | | (at least one required) | Single registry entry's graphurl + drift metadata,…

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.
47GitHub stars
2Forks
4mo agoLast update
Package
Authorio.github.looptech-ai
LicenseUnknown
Version0.1.1
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 · d88b53e
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
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

4 tools · none privileged
Statically extracted from the published packagev0.1.2 · 3mo 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.

find_graph_for_repoNo description published

This tool published no description. Forge does not invent one.

get_graphNo description published

This tool published no description. Forge does not invent one.

list_reposNo description published

This tool published no description. Forge does not invent one.

search_conceptsNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A thin Model Context Protocol server that exposes the understand-quickly registry to any MCP client (Claude Desktop, Codex, Cursor, etc.). Status: stub-quality. It works end-to-end but is intentionally minimal — no streaming, no embeddings, no auth. It wraps the public and exposes four tools: Tool | Params | Returns | | (at least one required) | Single registry entry's graph_url + drift metadata, or with up to 5 fuzzy-matched ids | | | Parsed graph JSON for that entry's | | | Default:…

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.