Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.predme/hypathesis

REMOTE · HYPATHESIS.COM · SCANNED SEP 22

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

Available components

0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 914 tokens (~228/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the com.predme/hypathesis MCP server?

com.predme/hypathesis is a hosted endpoint at https://hypathesis.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · hypathesis.com

# add to Claude Code
claude mcp add --transport http com-predme-hypathesis 'https://hypathesis.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-predme-hypathesis": {
      "url": "https://hypathesis.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-predme-hypathesis": {
      "type": "http",
      "url": "https://hypathesis.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-predme-hypathesis]
url = "https://hypathesis.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-predme-hypathesis": {
      "type": "remote",
      "url": "https://hypathesis.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-predme-hypathesis --url 'https://hypathesis.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-predme-hypathesis:
    url: "https://hypathesis.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-predme-hypathesis": {
      "Transport": "http",
      "Url": "https://hypathesis.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-predme-hypathesis -t streamable-http -u 'https://hypathesis.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-predme-hypathesis": {
      "type": "http",
      "url": "https://hypathesis.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 31 Aug 26 −1
    • Tool “get_analysis_status” rewrote its description, which is the text the model reads security
    • Tool “get_variable_relationships” rewrote its description, which is the text the model reads security
    • Server version: 1.28.1 → 1.29.1 functional
    • “get_analysis_status” added an optional parameter “session_token” cosmetic
    • “get_variable_relationships” added an optional parameter “session_token” cosmetic
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Probed https://hypathesis.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hypathesis.com CN=YE2,O=Let's Encrypt,C=US 20 Aug 2026 18 Nov 2026 ECDSA 256 ECDSA-SHA384 60e376ceb58ce79b4db7a55be0835727b7a
SANs: hypathesis.com, www.hypathesis.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of hypathesis.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
hypathesis.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hypathesis.com/mcp Verified 200
http (plaintext) http://hypathesis.com/mcp HTTPS enforced 301 https://hypathesis.com/mcp
MCP tools · 4 exposed · ~630 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_device_auth ~136

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

NameTypeReqDescription
user_codestringyes
NameTypeReqDescription
resultobjectyes

No examples provided.

get_analysis_status ~165

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 }

NameTypeReqDescription
authorizationstring
file_idstringyes
session_tokenstring
NameTypeReqDescription
resultobjectyes

No examples provided.

get_variable_relationships ~212

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

NameTypeReqDescription
authorizationstring
file_idstringyes
session_tokenstring
NameTypeReqDescription
resultobjectyes

No examples provided.

initiate_device_auth ~117

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 }

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes

No examples provided.

Common questions

What is the com.predme/hypathesis MCP server?

com.predme/hypathesis is an MCP server listed in the public MCP registry as com.predme/hypathesis. Variable relationships from research papers with causal direction and source traceback. This page covers its hosted endpoint (https://hypathesis.com/mcp).

Is the com.predme/hypathesis MCP server safe to use?

com.predme/hypathesis scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.predme/hypathesis MCP server expose?

com.predme/hypathesis exposes 4 tools: get_analysis_status, get_variable_relationships, initiate_device_auth, check_device_auth. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.

Does the com.predme/hypathesis MCP server require authentication?

No. We connected to com.predme/hypathesis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.predme/hypathesis MCP server still maintained?

com.predme/hypathesis is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.