All servers · Research & knowledge
com.predme/hypathesis
com.predme/hypathesis · v0.16.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | experimental, prompts, resources, tools |
| Tool definitions | 4 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Variable relationships from research papers with causal direction and source traceback.
Connect
streamable-http · https://hypathesis.com/mcp
claude mcp add --transport http hypathesis https://hypathesis.com/mcp{
"mcpServers": {
"hypathesis": {
"url": "https://hypathesis.com/mcp"
}
}
}Tools as reported by the server
get_analysis_statusCheck 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: Optioget_variable_relationshipsRetrieve 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 ainitiate_device_authStart 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 tcheck_device_authCheck 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: us
JSON · Text for agents · Registry updated 2026-06-06