Self-hosted AI gateway that governs MCP servers, LLM traffic, and A2A agents behind one endpoint
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.
get_weatherweather lookupweather lookup
No input schema was published for this tool.
get_timeGet the current timeGet the current time
No input schema was published for this tool.
apply_patchprivilegedEdit a fileEdit a file
No input schema was published for this tool.
shellprivilegedrun a shell commandrun a shell command
No input schema was published for this tool.
4 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.
Self-hosted AI gateway that governs MCP servers, LLM traffic, and A2A agents behind one endpoint
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
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.