mcp

Pay-per-query x402 business intelligence on Base, settled in USDC via the native 402 payment flow.

我該用這個嗎

品質與安全性

A
說明品質
94%
結構描述完整度
86%
命名品質
100%
汙染風險
80%
權限相符程度
100%
協定合規性
100%

發現項目(3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domain在 list_tiers 中
  • LOWTool 'get_sample' description lacks action verb在 get_sample 中

根據工具定義與協定合規性的自動化分析。

上下文成本

~801Token(工具定義)
~766 B典型回應大小
中等的注意力影響(128k 上下文的 0.63%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

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

遠端端點

https://mcp.midax402.com/mcpstreamable-http

它能做什麼

工具清單

工具(5)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢list_tiers

Lists the paid analysis tiers with their CANONICAL prices, fetched live from https://midax402.com/.well-known/x402 (resource_details) — the same first-party source directories crawl, so it can never drift.

輸入結構描述

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_sample(query)

Free sample of MIDAX402's analysis: returns ONLY the calibrated verdict and confidence score for an x402-ecosystem question, plus pointers to the paid tiers that serve the full analysis. Rate-limited; the full analysis is the paid product.

輸入結構描述

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "x402 ecosystem question (protocols, facilitators, security, agent commerce)."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
🟢get_market_verdict(tier, query, payment_signature)

Runs a paid MIDAX402 analysis tier. Payment is x402-native: called WITHOUT payment_signature it returns the HTTP 402 payment requirements (decoded + raw PAYMENT-REQUIRED header) for your x402-capable wallet to sign; call again WITH payment_signature (the signed payment proof, as sent in the PAYMENT-SIGNATURE header) to receive the full analysis. This server NEVER holds keys and never signs — your wallet does.

輸入結構描述

{
  "type": "object",
  "properties": {
    "tier": {
      "type": "string",
      "enum": [
        "basic",
        "standard",
        "premium",
        "market_brief"
      ],
      "description": "Analysis tier. Canonical USDC prices come from the list_tiers tool (live first-party source) — call it first if you need current prices."
    },
    "query": {
      "type": "string",
      "description": "x402 ecosystem question for the paid analysis."
    },
    "payment_signature": {
      "type": "string",
      "description": "Optional: the x402 payment proof produced by your wallet (the exact value for the PAYMENT-SIGNATURE header). Omit on the first call to receive the 402 payment requirements."
    }
  },
  "required": [
    "tier",
    "query"
  ],
  "additionalProperties": false
}
🟢verify(url)

Checks x402 protocol conformance for a target service URL: a live 402 probe (well-formed challenge, non-empty accepts, atomic-unit amounts) plus price coherence against the target's own well-known. PAID ($0.10 USDC via x402). This MCP server holds no wallet, so calling this tool returns the upstream payment requirements rather than a result — pay them with your own x402 client, or call the endpoint directly. A signed, permanently published attestation of the same check is available at /midas-ops/attest ($0.50). Does NOT measure output quality, uptime history, or on-chain transaction volume — see the returned scope_note.

輸入結構描述

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The https:// URL of the x402 service resource to check (e.g. a paid endpoint)."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}
⚪verify_before_pay(url)

The question to ask BEFORE paying any x402 service: does MIDAX have a signed conformance verdict for this URL? FREE, ONE call. Returns the verdict with its age and freshness if one exists in MIDAX's signed registry, plus the authenticity verdict when that feature ships (always present in the payload, null with a note until then). If nothing exists yet, says so plainly and returns the exact price and route for the next paid step -- never a vague 'contact us'. Reads MIDAX's own registry only: it never probes the target live, so it adds minimal latency to your payment decision.

輸入結構描述

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The https:// URL of the x402 service you are about to pay."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本5 個工具
已驗證未記錄版本5 個工具