mcp

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

Should I use this

Quality & Safety

A
Description quality
94%
Schema completeness
86%
Naming quality
100%
Poisoning risk
80%
Permission match
100%
Protocol compliance
100%

Findings (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainin list_tiers
  • LOWTool 'get_sample' description lacks action verbin get_sample

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~801Tokens (tool definitions)
~766 BTypical response size
Moderate attention impact (0.63% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

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

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

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

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools
verifiedversion not recorded5 tools