Hypathesis MCP Server

by predme Your server? Claim it

answering

Hypathesis is answering right now. Last checked 11 min ago. It exposes 4 tools.

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

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

389 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 August 2026. No other catalogue keeps this.

30 Aug 2 tool descriptions were rewritten get_analysis_status, get_variable_relationships

30 Aug 2 tools changed the parameters they ask for get_analysis_status, get_variable_relationships

30 Aug a tool changed version

Nothing serious here today

Today is the operative word: we check Hypathesis every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add hypathesis --transport http https://hypathesis.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "hypathesis": {
      "url": "https://hypathesis.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.hypathesis]
url = "https://hypathesis.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "hypathesis": {
      "url": "https://hypathesis.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "hypathesis": {
      "url": "https://hypathesis.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analysis

get_analysis_status

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 }

device

check_device_auth

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": "..."}

initiate

initiate_device_auth

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 }

variable

get_variable_relationships

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).

Endpoints

URL	Transport	State	Latency	Checked
https://hypathesis.com/mcp	streamable-http	answering	420 ms	11 min ago

Alternatives to Hypathesis

same job, measured the same way

CiteNexus

by akougkas

Search scholarly sources, verify references, and export citations with traceable evidence.

local only

drillable

by drillable

Pinned, versioned sources with citable locators: search finds spans, trace reaches the bytes.

3 tools answering

Legend Saju

by sihyeonjeon

Source-traceable Saju, Zi Wei, Qimen, Daliuren, Tieban, naming, and related calculations

13 tools answering

CatchDoms — Expired Domains API

by catchdoms

Search 40K+ expired domains from 12 auction platforms with SEO metrics and scores.

3 tools answering

CLI

by noticedso

Search your developer network and trace connection paths via GitHub & LinkedIn.

46 installs/wk local only

CyberHuaTuo

by jinning6

Gold-first AI-agent traceback diagnosis, exact fixes, verification, and reusable prescriptions.

162 installs/wk local only

Ireland Passport Application Status Tracker

by nero-engine

Irish passport application status from the DFA tracker, with alerts on stage or date changes.

answering

SigParser

by sigparser

Query contacts, companies, relationships, and communication metrics from SigParser.

answering

Hypathesis — questions

Answers built from our own checks of this server.

What can Hypathesis do?

It exposes 4 tools, read directly from the server on our last check. Among them: check_device_auth, get_analysis_status, get_variable_relationships, initiate_device_auth. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Hypathesis working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 389 ms. The bar chart above shows every period we have measured.

How do I connect Hypathesis?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Hypathesis need an API key?

No. Hypathesis completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Hypathesis?

It answers our handshake in 389 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.