{
  "checker": {
    "details": {
      "hosting": "remote",
      "kind": "mcp_http",
      "protocolVersion": "2025-06-18",
      "scope": "remote hosted MCP initialize + tools/list",
      "serverInfo": {
        "name": "goji",
        "version": "1.0.1"
      },
      "tools": [
        "goji_search",
        "goji_explain_term",
        "goji_browse_glossary",
        "goji_get_service",
        "goji_answer_faq",
        "goji_guide_contents",
        "goji_read_guide_chapter",
        "goji_read_guide",
        "goji_start_enquiry"
      ],
      "transport": "streamable-http",
      "url": "https://mcp.goji.agency/mcp",
      "working": true
    },
    "status": "PASS"
  },
  "deviations": [
    "npx -y mcp-remote https://mcp.goji.agency/mcp failed on Node 18 with ReferenceError: File is not defined; fixed by switching to Node 20.20.2.",
    "npx -y mcp-remote https://mcp.goji.agency/mcp then failed with getaddrinfo EAI_AGAIN mcp.goji.agency: the VM only reaches the internet through HTTPS_PROXY=http://192.0.2.1:3128, which Node fetch does not use. Worked around by exercising the endpoint with curl (which honors the proxy) instead of the bridge. Probe still names the bridge command, so it will fail for the checker unless the proxy is honored.",
    "Python urllib (stdlib) POST to the endpoint returned HTTP 403 from the edge; curl with the same body returned 200. Not investigated further; curl used."
  ],
  "main_blocker": null,
  "operation": "Connected to the hosted GOJI MCP server over Streamable HTTP: initialize, tools/list (9 tools), and tools/call goji_explain_term with term 'AEO', which returned GOJI's glossary definition with a goji.agency citation.",
  "operation_scope": "Hosted service only; no local build exists (repo is README and metadata). Verified over HTTP via curl through the proxy. The README's stdio bridge (npx mcp-remote) cannot reach the host from this VM because Node 20 fetch does not honor https_proxy; the bridge is the one unmet piece. enquiry tool (goji_start_enquiry) deliberately not called since it sends a real email.",
  "outcome": "working",
  "steps": [
    "Read README.md and server.json (no install/build section; endpoint https://mcp.goji.agency/mcp)",
    "curl POST initialize to https://mcp.goji.agency/mcp -> HTTP 200",
    "curl POST notifications/initialized -> 202",
    "curl POST tools/list -> 9 tools",
    "curl POST tools/call goji_explain_term {term:'AEO'} -> glossary text with goji.agency citation",
    "README 'For clients that only speak stdio' section: installed Node (apt nodejs/npm 18), then upgraded to Node 20 via npm i -g n && n 20 because mcp-remote needs File global",
    "npx -y mcp-remote https://mcp.goji.agency/mcp with initialize/tools/list on stdin -> failed (see deviations)"
  ],
  "stuck_step": "npx -y mcp-remote https://mcp.goji.agency/mcp (README: Any MCP client -> stdio bridge)",
  "suggested_fix": "Run the bridge with a proxy-aware Node (Node 24+ with NODE_USE_ENV_PROXY=1), or give the VM direct DNS/egress to mcp.goji.agency, or use a probe kind mcp_http that targets the URL directly."
}