io.github.devznsh/throughline

MCPcommunity
v1.0.1io.github.devznshUnknownUpdated 2mo agoGitHub

Give Claude complete understanding of your software project.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.devznsh
LicenseUnknown
Version1.0.1
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface18 tools · 1 privileged
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 27, 2026

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

Tools

18 tools · 1 privileged
Statically extracted from the published packagevHEAD · 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.

list_workspacesNo description published

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

scan_repositoryNo description published

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

refresh_indexNo description published

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

search_codeNo description published

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

find_symbolNo description published

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

find_referencesNo description published

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

explain_fileNo description published

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

explain_symbolNo description published

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

trace_executionNo description published

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

project_overviewNo description published

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

dependency_graphNo description published

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

architecture_diagramNo description published

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

list_entry_pointsNo description published

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

recent_changesNo description published

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

repository_healthNo description published

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

find_dead_codeNo description published

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

draft_documentationNo description published

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

write_documentationprivilegedNo description published

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

0 of 18 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

Give Claude complete understanding of your software project.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.