Skip to content
External endpointresponds

hypathesis

Variable relationships from research papers with causal direction and source traceback.

Endpoint URL
https://hypathesis.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:02 AM UTC
Check
MCP initialize · 8s limit
Latency
254 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.predme/hypathesis

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
hypathesis
Version
1.28.1
Capability keys
experimental, prompts, resources, tools
Tool names
get_analysis_status, get_variable_relationships, initiate_device_auth, check_device_auth
Instructions excerpt

Hypathesis analyzes research papers and extracts structured variable relationships with causal direction. IMPORTANT: In Claude Desktop, use Code mode (not Chat or Cowork). Workflow: (1) upload a PDF via: curl -s -F file=@/path/to/paper.pdf https://hypathesis.com/mcp/upload — this returns a file_id and starts processing automatically, (2) poll get_analysis_status with the file_id until status is 'Ready', (3) call get_variable_relationships with the file_id to retrieve results. No account needed for basic results. With an API key you also get detailed reasoning. To get an API key, call initiate_device_auth — this gives the user a link to sign in with Google, and you get an API key automatically. IMPORTANT: After receiving an API key, save it to a file called .hypathesis-key in the working directory so it persists across sessions. On future sessions, check for .hypathesis-key first — if it exists, use that key instead of initiating device auth again. Pass the API key in the Authoriz

Reported Aug 17, 2026, 05:02 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 82ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 274ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 259ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 254ms