Gmail Postmaster Tools v2 — domains, traffic metrics, and compliance via your own Google OAuth.
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.
gpt_authenticateNo description publishedThis tool published no description. Forge does not invent one.
gpt_auth_statusNo description publishedThis tool published no description. Forge does not invent one.
gpt_sign_outNo description publishedThis tool published no description. Forge does not invent one.
list_domainsNo description publishedThis tool published no description. Forge does not invent one.
get_domainNo description publishedThis tool published no description. Forge does not invent one.
get_compliance_statusNo description publishedThis tool published no description. Forge does not invent one.
query_domain_statsNo description publishedThis tool published no description. Forge does not invent one.
0 of 7 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.
Gmail Postmaster Tools v2 — domains, traffic metrics, and compliance via your own Google OAuth.
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.