hypathesis MCP server
com.predme/hypathesispredme.comstreamable-httpv0.16.0Scanned
Variable relationships from research papers with causal direction and source traceback.
4 tools: 2 change things and 2 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the hypathesis MCP server can do
The hypathesis MCP server is published by predme.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: initiate_device_auth and check_device_auth), but cannot delete data. 2 tools only read.
2 tools read private data (get_analysis_status and get_variable_relationships).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 0.16.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
check_device_authCheck if the user has completed browser sign-in for a device auth request.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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": "..."}
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
initiate_device_authStart a browser-based sign-in flow to get an API key for full access.No findings
Why it is in this group
- The description's first verb is "start": a word for a change.
Description, as the server wrote it 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 }
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
Only reads 2Show 2 read-only tools
get_analysis_statusCheck the processing status of an uploaded paper.Reads private dataNo findings
Why it is in this group
- The name "get_analysis_status" says "get": a word for reading.
What it can reach
- private-dataThe input names a file (input.file_id), and the tool reads: it reads files.
Description, as the server wrote it 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 }
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
get_variable_relationshipsRetrieve analyzed variable relationships for a completed paper.Reads private dataNo findings
Why it is in this group
- The name "get_variable_relationships" says "get": a word for reading.
What it can reach
- private-dataThe input names a file (input.file_id), and the tool reads: it reads files.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://hypathesis.com/mcp: tools/list returned 4 tools to an anonymous client, including initiate_device_auth (write), check_device_auth (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.16.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http hypathesis https://hypathesis.com/mcpclaude mcp add --transport http hypathesis https://hypathesis.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__hypathesis__get_analysis_status",
"mcp__hypathesis__get_variable_relationships"
],
"ask": [
"mcp__hypathesis__initiate_device_auth",
"mcp__hypathesis__check_device_auth"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hypathesis. Review it before you use it.
Capability tags behind 2 rules
- mcp__hypathesis__get_analysis_status private-data
- mcp__hypathesis__get_variable_relationships private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.predme/hypathesis/verify?hash=99a5946161c0c41011902141b4549112769b9e0d530a17e7fdbf1e870cb08d19" | jq -e '.changed == false'Pinned hash 99a5946161c0, from Nov 14, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.predme/hypathesis/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.predme/hypathesis)Source: MCP Registry. Synced Oct 21, 2026, 18:00 UTC.
hypathesis MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the hypathesis MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the hypathesis MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the hypathesis MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the hypathesis MCP server have?
- 4 tools: 2 write, 2 read. initiate_device_auth, check_device_auth, get_analysis_status and get_variable_relationships.
Does the hypathesis MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the hypathesis MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the hypathesis MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.