Portamora API Verified

MCP server at https://portamora.app (endpoint source: benchmark_guide)

0/2 tests passed

{
  "overall": 32,
  "dimensions": {
    "doc_quality": 1.0,
    "auth_simplicity": 2.0,
    "latency": 9.5
  },
  "pricing_normalized": {},
  "issues": [
    "Endpoint came from a benchmark guide (declared), but every request returns 403 from a CDN edge (CloudFront-style 'distribution is not configured to allow the HTTP request method') with an HTML error page, not a JSON-RPC body.",
    "No WWW-Authenticate header or JSON-RPC error envelope is present, so this does not behave like an MCP server enforcing auth — it looks like an unconfigured/wrong CDN distribution rejecting the method entirely.",
    "Because the 403 is a CDN method rejection rather than an MCP-level auth challenge, we could not observe tool discovery, tool calls, response shapes, or token cost. first_try_success, response_parseability, consistency, and token_efficiency are intentionally omitted.",
    "No MCP manifest or tool schema documentation is reachable at the declared endpoint."
  ],
  "recommendations": [
    "Ensure the declared MCP endpoint routes POST JSON-RPC requests to the MCP server rather than being caught by a CDN cache-only distribution.",
    "Return a proper MCP-level 401/403 with a JSON-RPC error and WWW-Authenticate header when credentials are required, instead of an HTML CDN error page.",
    "Publish a reachable MCP manifest/tool schema so agents can discover tools without probing.",
    "Confirm the benchmark guide's declared URL is actually the MCP server origin, not a site root behind a static CDN."
  ]
}