reverseport

MCPcommunity
v1.0.0io.github.laaielichterMITUpdated 7d agonpmGitHub

Reverse engineer anything. Port it anywhere. One MCP server for coding agents.

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 →
2GitHub stars
7d agoLast update
Package
Authorio.github.laaielichter
LicenseMIT
Version1.0.0
Sourcenpm+mcp-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 surface6 tools · none privileged
Security scan✓ Cleanv1.0.0 · 6d agoHow well does this scan work?
EvalsNone
IndexedOct 13, 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 packagev1.0.0 · 6d 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.

investigate_featureTrace a feature through relevant artifact, symbol, and function evidence while distinguishing observations, inferences, and residual unknowns.

Trace a feature through relevant artifact, symbol, and function evidence while distinguishing observations, inferences, and residual unknowns.

No input schema was published for this tool.

compare_application_versionsCompare two shipped application artifacts through complete inventory and optional static or runtime evidence without equating missing data with unchanged behavior.

Compare two shipped application artifacts through complete inventory and optional static or runtime evidence without equating missing data with unchanged behavior.

No input schema was published for this tool.

verify_reconstructionEvaluate a finite reconstruction specification against retained Evidence comparisons without broadening pass results into global equivalence claims.

Evaluate a finite reconstruction specification against retained Evidence comparisons without broadening pass results into global equivalence claims.

No input schema was published for this tool.

trace_crashCorrelate a crash symptom with static call and reference evidence plus optional process capture observations.

Correlate a crash symptom with static call and reference evidence plus optional process capture observations.

No input schema was published for this tool.

audit_residual_unknownsReview current residual-unknown heads against retained evidence, revision integrity, and declared authority without silently closing unanswered questions.

Review current residual-unknown heads against retained evidence, revision integrity, and declared authority without silently closing unanswered questions.

No input schema was published for this tool.

prepare_bounded_process_captureChoose a command, inputs, observations, and stopping conditions for a process capture that answers the behavioral question.

Choose a command, inputs, observations, and stopping conditions for a process capture that answers the behavioral question.

No input schema was published for this tool.

6 of 6 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

Reverse engineer anything. Port it anywhere. One MCP server for coding agents.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-13 — observed resolution, not a publisher declaration.

60 packages resolved · 36 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

41 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+29 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.