site_status

2 registry entries were observed exposing a tool named site_status — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 11,987 of 38,128 scannable entries (31%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. @tengence/geo-mcpMCPcommunitytrust 60/100 · B
    v0.1.2
    ↓ 305/wk

    GEO content engine MCP server: 56 tools across content, publishing, search-inclusion and AI-monitoring domains; stdio + Streamable HTTP transports, Bearer-token auth (the MCP bridge layer of @tengence/geo-sdk)

    ClaudeCursorCopilotGemini
    Tengence TeamMIT6d agonpmGitHubobserved · static extraction
    geoseomcpmodel-context-protocolagentwordpress
  2. now.shiply/shiplyMCPcommunitylivetrust 60/100 · B
    v1.1.0

    Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price.

    ClaudeCursorCopilotChatGPTGemini
    now.shiplyUnknown2mo agoobserved · live tools/list
    mcp

All indexed toolsSearch the registry for site_status