hypathesis

endpoint

https://hypathesis.com/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is hypathesis live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is hypathesis free to use?

Yes — the hub reached it with no key and no payment.

What tools does hypathesis have?

4 tools: get_variable_relationships, get_analysis_status, initiate_device_auth, check_device_auth.

Is hypathesis safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_variable_relationships reads unknown 19h ago

  Retrieve analyzed variable relationships for a completed paper. Only returns results when get_analysis_status reports status='Ready'. Without an API key (anonymous): returns the relationship list with source, target, and direction — but detailed reasoning is available only with an API key. Sign up at https://hypathesis.com to get one. Args: file_id: The file_id returned by the /upload endpoint. authorization: Optional. API key as 'Bearer hk_...' or 'hk_...'. session_token: Optional. The session_token returned by /upload for anonymous uploads. Returns: Authenticated: full details (source, target, directed, reason per relationship; name, measure per variable). Anonymous: gated (source, target, directed per relationship; name per variable; sign_up_url for full access).

  mcp-tool

  1234567891011121314151617181920212223

  {
    "type": "object",
    "title": "get_variable_relationshipsArguments",
    "required": [
      "file_id"
    ],
    "properties": {
      "file_id": {
        "type": "string",
        "title": "File Id"
      },
      "authorization": {
        "type": "string",
        "title": "Authorization",
        "default": ""
      },
      "session_token": {
        "type": "string",
        "title": "Session Token",
        "default": ""
      }
    }
  }

  arguments 23 lines copy
• get_analysis_status reads unknown 19h ago

  Check the processing status of an uploaded paper. Poll this tool after uploading a PDF until status is 'Ready' before calling get_variable_relationships. Args: file_id: The file_id returned by the /upload endpoint. authorization: Optional. API key as 'Bearer hk_...' or 'hk_...'. session_token: Optional. The session_token returned by /upload for anonymous uploads. Returns: { "status": "Processing" | "Ready" | "Empty" | "Ineligible" | "Pending", "edges_count": int, "variables_count": int }

  mcp-tool

  1234567891011121314151617181920212223

  {
    "type": "object",
    "title": "get_analysis_statusArguments",
    "required": [
      "file_id"
    ],
    "properties": {
      "file_id": {
        "type": "string",
        "title": "File Id"
      },
      "authorization": {
        "type": "string",
        "title": "Authorization",
        "default": ""
      },
      "session_token": {
        "type": "string",
        "title": "Session Token",
        "default": ""
      }
    }
  }

  arguments 23 lines copy
• initiate_device_auth changes data unknown never probed

  Start a browser-based sign-in flow to get an API key for full access. Call this when you need detailed analysis results (reasoning, measurements) that require authentication. Returns a verification URL to show to the user. After the user signs in, poll check_device_auth with the returned user_code to get the API key. Returns: { "verification_url": str, "user_code": str, "expires_in": 600, "message": str }

  mcp-tool

  12345

  {
    "type": "object",
    "title": "initiate_device_authArguments",
    "properties": {}
  }

  arguments 5 lines copy
• check_device_auth reads unknown 19h ago

  Check if the user has completed browser sign-in for a device auth request. Poll this after calling initiate_device_auth. Returns status 'pending' while waiting, or 'complete' with an api_key when the user has signed in. Use the returned api_key as the authorization parameter in other tools. Args: user_code: The user_code returned by initiate_device_auth. Returns: Pending: {"status": "pending"} Complete: {"status": "complete", "api_key": "hk_..."} Error: {"error": "..."}

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "check_device_authArguments",
    "required": [
      "user_code"
    ],
    "properties": {
      "user_code": {
        "type": "string",
        "title": "User Code"
      }
    }
  }

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.