hypathesis

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

使うべきか

品質と安全性

B
説明の品質
100%
スキーマの完全性
68%
命名の品質
95%
ポイズニングのリスク
80%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(2)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainget_variable_relationships 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,072トークン数(ツール定義)
~1.1 KB一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 0.84%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

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

リモートエンドポイント

https://hypathesis.com/mcpstreamable-http

できること

ツール一覧

ツール(4)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢get_analysis_status(file_id, authorization, session_token)

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 }

入力スキーマ

{
  "type": "object",
  "properties": {
    "file_id": {
      "title": "File Id",
      "type": "string"
    },
    "authorization": {
      "default": "",
      "title": "Authorization",
      "type": "string"
    },
    "session_token": {
      "default": "",
      "title": "Session Token",
      "type": "string"
    }
  },
  "required": [
    "file_id"
  ],
  "title": "get_analysis_statusArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "additionalProperties": true,
      "title": "Result",
      "type": "object"
    }
  },
  "required": [
    "result"
  ],
  "title": "get_analysis_statusOutput"
}
🟢get_variable_relationships(file_id, authorization, session_token)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "file_id": {
      "title": "File Id",
      "type": "string"
    },
    "authorization": {
      "default": "",
      "title": "Authorization",
      "type": "string"
    },
    "session_token": {
      "default": "",
      "title": "Session Token",
      "type": "string"
    }
  },
  "required": [
    "file_id"
  ],
  "title": "get_variable_relationshipsArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "additionalProperties": true,
      "title": "Result",
      "type": "object"
    }
  },
  "required": [
    "result"
  ],
  "title": "get_variable_relationshipsOutput"
}
🟢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 }

入力スキーマ

{
  "type": "object",
  "properties": {},
  "title": "initiate_device_authArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "additionalProperties": true,
      "title": "Result",
      "type": "object"
    }
  },
  "required": [
    "result"
  ],
  "title": "initiate_device_authOutput"
}
🟢check_device_auth(user_code)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "user_code": {
      "title": "User Code",
      "type": "string"
    }
  },
  "required": [
    "user_code"
  ],
  "title": "check_device_authArguments"
}

出力スキーマ

{
  "type": "object",
  "properties": {
    "result": {
      "additionalProperties": true,
      "title": "Result",
      "type": "object"
    }
  },
  "required": [
    "result"
  ],
  "title": "check_device_authOutput"
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 4 件
検証済みバージョンは記録されていませんツール 4 件