Cross-project knowledge graph for MCP — map features across mobile, backend, and admin codebases.
A cross-project knowledge graph for the Model Context Protocol (MCP). Map features across mobile, backend, and admin codebases so your AI agent has full-stack context when testing, writing code, debugging, or adding features. Then add to your MCP settings: Installation & Configuration Knowledge File Management When working on a project with multiple codebases — for example, a React Native mobile…
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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.
register_projectNo description publishedThis tool published no description. Forge does not invent one.
remove_projectprivilegedNo description publishedThis tool published no description. Forge does not invent one.
scan_projectNo description publishedThis tool published no description. Forge does not invent one.
register_featureNo description publishedThis tool published no description. Forge does not invent one.
remove_featureprivilegedNo description publishedThis tool published no description. Forge does not invent one.
get_featureNo description publishedThis tool published no description. Forge does not invent one.
searchNo description publishedThis tool published no description. Forge does not invent one.
reverse_lookupNo description publishedThis tool published no description. Forge does not invent one.
get_contextNo description publishedThis tool published no description. Forge does not invent one.
register_type_mappingsNo description publishedThis tool published no description. Forge does not invent one.
check_type_mappingNo description publishedThis tool published no description. Forge does not invent one.
get_architectureNo description publishedThis tool published no description. Forge does not invent one.
export_knowledgeNo description publishedThis tool published no description. Forge does not invent one.
import_knowledgeNo description publishedThis tool published no description. Forge does not invent one.
validate_knowledgeNo description publishedThis tool published no description. Forge does not invent one.
suggest_type_mappingsNo description publishedThis tool published no description. Forge does not invent one.
0 of 16 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.
A cross-project knowledge graph for the Model Context Protocol (MCP). Map features across mobile, backend, and admin codebases so your AI agent has full-stack context when testing, writing code, debugging, or adding features. Then add to your MCP settings: Installation & Configuration Knowledge File Management When working on a project with multiple codebases — for example, a React Native mobile app, a NestJS backend, and a Next.js admin panel — the AI agent has no awareness of how a single…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.