Variable relationships from research papers with causal direction and source traceback.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://hypathesis.com/mcp4 tools · 1263msget_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_...'.
Returns:
{
"status": "Processing" | "Ready" | "Empty" | "Ineligible" | "Pending",
"edges_count": int,
"variables_count": int
}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_...'. Returns: { "status": "Processing" | "Ready" | "Empty" | "Ineligible" | "Pending", "edges_count": int, "variables_count": int }
No input schema was published for this tool.
get_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 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_...'.
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).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_...'. 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).
No input schema was published for this tool.
initiate_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
to get the API key.
Returns:
{
"verification_url": str,
"user_code": str,
"expires_in": 600,
"message": str
}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 }
No input schema was published for this tool.
check_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:
user_code: The user_code returned by initiate_device_auth.
Returns:
Pending: {"status": "pending"}
Complete: {"status": "complete", "api_key": "hk_..."}
Error: {"error": "..."}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": "..."}
No input schema was published for this tool.
4 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Variable relationships from research papers with causal direction and source traceback.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.