Midax402

com.midax402Published by midax402.comOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Lets an assistant query a paid x402 business-intelligence service on Base, get free sample verdicts, and check x402 payment conformance of other services.

What you can do
Exposes five tools: list_tiers shows the paid analysis tiers with live canonical prices; get_sample returns a free, rate-limited calibrated verdict and confidence score for an x402-ecosystem question; get_market_verdict runs a paid analysis tier, first returning HTTP 402 payment requirements and then accepting a signed payment proof. verify probes a target service URL for x402 protocol conformance and price coherence, and verify_before_pay checks whether a signed conformance verdict exists for a URL before paying it.
When to use it
Use it when you want an assistant to obtain x402-ecosystem analysis or verdicts, or to check whether another x402 service is well-formed and fairly priced before paying it. The free sample and verify_before_pay calls are useful for a quick look without spending.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. Paid tools require an x402-capable wallet to sign payment proofs, and the server itself holds no wallet. Network access to the endpoint and to the target URLs being verified.
Before you install
Several tools cost money in USDC on Base: get_market_verdict runs a paid tier and verify costs $0.10 USDC via x402, so calls can spend funds. Payment is made by supplying a signed payment proof (payment_signature) from your own wallet. verify sends a live probe to the target service URL you provide.

Installation

In SourceWeft

  1. Open Midax402 in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.midax402%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

5

list_tiers

List MIDAX402 paid tiers (canonical prices)

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.

Takes no parameters.

get_sample

Free trimmed sample (verdict + confidence only)

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.

Parametersqueryrequired

get_market_verdict

Paid market verdict (x402 payment handled by YOUR wallet)

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.

Parameterstierrequiredqueryrequiredpayment_signature

verify

x402 protocol conformance check for a target service (paid, $0.10)

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.

Parametersurlrequired

verify_before_pay

Verify before you pay (free, one call, reads the signed registry only)

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.

Parametersurlrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.