Grants and public-goods MCP: discovery, ranking, grounded drafting, open-source first.
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.
statusOpenGOS page health.OpenGOS page health.
No input schema was published for this tool.
list_programsList demo grant program buckets.List demo grant program buckets.
No input schema was published for this tool.
match_needRank demo programs against a need. Local heuristic.Rank demo programs against a need. Local heuristic.
No input schema was published for this tool.
draft_outlineOutline stub only. Does not submit. Requires confirmation.Outline stub only. Does not submit. Requires confirmation.
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.
Grants and public-goods MCP: discovery, ranking, grounded drafting, open-source first.
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.