com.midax402/mcp
REMOTE · MCP.MIDAX402.COM · SCANNED SEP 25
Pay-per-query x402 business intelligence on Base, settled in USDC via the native 402 payment flow.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 754 tokens (~150/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "verify_before_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.midax402/mcp server?
com.midax402/mcp is a hosted endpoint at https://mcp.midax402.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.midax402.com
claude mcp add --transport http com-midax402-mcp 'https://mcp.midax402.com/mcp'
{
"mcpServers": {
"com-midax402-mcp": {
"url": "https://mcp.midax402.com/mcp"
}
}
} {
"servers": {
"com-midax402-mcp": {
"type": "http",
"url": "https://mcp.midax402.com/mcp"
}
}
} [mcp_servers.com-midax402-mcp] url = "https://mcp.midax402.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-midax402-mcp": {
"type": "remote",
"url": "https://mcp.midax402.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-midax402-mcp --url 'https://mcp.midax402.com/mcp' --transport streamable-http
mcp_servers:
com-midax402-mcp:
url: "https://mcp.midax402.com/mcp" {
"McpServers": {
"com-midax402-mcp": {
"Transport": "http",
"Url": "https://mcp.midax402.com/mcp"
}
}
} assistant mcp add com-midax402-mcp -t streamable-http -u 'https://mcp.midax402.com/mcp'
{
"mcpServers": {
"com-midax402-mcp": {
"type": "http",
"url": "https://mcp.midax402.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 2 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 591 → 747 ▼ functional
- Destructive annotations: pass → 0 functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “verify_before_pay” functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Aug 26 0
- Tool “verify” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool “verify” changed its title: x402 protocol conformance check for a target service (free) → x402 protocol conformance check for a target service (paid, $0.10) cosmetic
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.midax402.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.midax402.com | CN=WE1,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b5fa5016a8e8eadf13e140bff4fb1ec6 |
| SANs: mcp.midax402.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.midax402.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| midax402.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.midax402.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.midax402.com/mcp | HTTPS enforced | 301 | https://mcp.midax402.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_market_verdict Paid market verdict (x402 payment handled by YOUR wallet) ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | 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. |
| query | string | yes | x402 ecosystem question for the paid analysis. |
| tier | string | yes | Analysis tier. Canonical USDC prices come from the list_tiers tool (live first-party source) — call it first if you need current prices. |
No output schema declared.
No examples provided.
get_sample Free trimmed sample (verdict + confidence only) ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | x402 ecosystem question (protocols, facilitators, security, agent commerce). |
No output schema declared.
No examples provided.
list_tiers List MIDAX402 paid tiers (canonical prices) ~54
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
verify x402 protocol conformance check for a target service (paid, $0.10) ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The https:// URL of the x402 service resource to check (e.g. a paid endpoint). |
No output schema declared.
No examples provided.
verify_before_pay Verify before you pay (free, one call, reads the signed registry only) ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The https:// URL of the x402 service you are about to pay. |
No output schema declared.
No examples provided.
What is the com.midax402/mcp server?
com.midax402/mcp is listed in the public MCP registry as com.midax402/mcp. Pay-per-query x402 business intelligence on Base, settled in USDC via the native 402 payment flow. This page covers its hosted endpoint (https://mcp.midax402.com/mcp).
Is the com.midax402/mcp server safe to use?
com.midax402/mcp scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.midax402/mcp server expose?
com.midax402/mcp exposes 5 tools: list_tiers, get_sample, get_market_verdict, verify, verify_before_pay. Their descriptions and schemas cost roughly 650 tokens of context every time the server is loaded.
Does the com.midax402/mcp server require authentication?
No. We connected to com.midax402/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.midax402/mcp server still maintained?
com.midax402/mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.