com.repofuse/repofuse

MCPcommunitylive
v0.3.0com.repofuseUnknownUpdated todayGitHub

Discover and scaffold new apps by reusing code from your GitHub repositories.

Endpoint healthlive
checked 6h ago · 171ms · auth required
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). 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 →
1GitHub stars
todayLast update
Package
Authorcom.repofuse
LicenseUnknown
Version0.3.0
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 surface6 tools · none privileged
Security scan✓ CleanvHEAD · todayHow well does this scan work?
EvalsNone
IndexedSep 27, 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 packagevHEAD · 6h 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.

report_blueprintsReport the discovered app blueprints based on repository file analysis

Report the discovered app blueprints based on repository file analysis

No input schema was published for this tool.

list_github_repositoriesList GitHub repositories connected to the user’s RepoFuse account. Suggest this when the user needs to discover or choose repositories before asking RepoFuse to analyze reusable code.

List GitHub repositories connected to the user’s RepoFuse account. Suggest this when the user needs to discover or choose repositories before asking RepoFuse to analyze reusable code.

No input schema was published for this tool.

analyze_repositoriesRead code trees from selected GitHub repositories and identify practical new apps that can reuse the existing code. On Free, a call uses one monthly analysis allowance; on paid plans it costs 100 RepoFuse credits. Suggest it only after the user approves the charge or quota use, and do not auto-run…

Read code trees from selected GitHub repositories and identify practical new apps that can reuse the existing code. On Free, a call uses one monthly analysis allowance; on paid plans it costs 100 RepoFuse credits. Suggest it only after the user approves the charge or quota use, and do not auto-run…

No input schema was published for this tool.

generate_scaffoldGenerate a scaffold plan and starter-file contents for a chosen app blueprint without creating a repository. This Pro tool costs 150 RepoFuse credits per approved invocation. Suggest it only after the user approves the charge, and do not auto-run or retry it.

Generate a scaffold plan and starter-file contents for a chosen app blueprint without creating a repository. This Pro tool costs 150 RepoFuse credits per approved invocation. Suggest it only after the user approves the charge, and do not auto-run or retry it.

No input schema was published for this tool.

create_repo_from_blueprintCreate a new GitHub repository and seed it with starter files from a selected RepoFuse blueprint. Suggest this only after the user explicitly asks to create the repository and confirms its name and visibility.

Create a new GitHub repository and seed it with starter files from a selected RepoFuse blueprint. Suggest this only after the user explicitly asks to create the repository and confirms its name and visibility.

No input schema was published for this tool.

get_blueprint_gapsRead the reusable files, missing files, and technology stack for a saved RepoFuse blueprint. Suggest this when the user wants to assess what is already present versus what remains to build before generating a scaffold.

Read the reusable files, missing files, and technology stack for a saved RepoFuse blueprint. Suggest this when the user wants to assess what is already present versus what remains to build before generating a scaffold.

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

Discover and scaffold new apps by reusing code from your GitHub repositories.

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.