x402 Compatibility Intelligence
REMOTE · INTELLIGENCE.INVERSOLABS.US · SCANNED SEP 20
Preflight x402 payment compatibility with structured risk evidence and remediation guidance.
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 Security46
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the x402 Compatibility Intelligence MCP server?
x402 Compatibility Intelligence is a hosted endpoint at https://intelligence.inversolabs.us/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 · intelligence.inversolabs.us
claude mcp add --transport http us-inversolabs-x402-compatibility-intelligence 'https://intelligence.inversolabs.us/mcp'
{
"mcpServers": {
"us-inversolabs-x402-compatibility-intelligence": {
"url": "https://intelligence.inversolabs.us/mcp"
}
}
} {
"servers": {
"us-inversolabs-x402-compatibility-intelligence": {
"type": "http",
"url": "https://intelligence.inversolabs.us/mcp"
}
}
} [mcp_servers.us-inversolabs-x402-compatibility-intelligence] url = "https://intelligence.inversolabs.us/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"us-inversolabs-x402-compatibility-intelligence": {
"type": "remote",
"url": "https://intelligence.inversolabs.us/mcp",
"enabled": true
}
}
} openclaw mcp add us-inversolabs-x402-compatibility-intelligence --url 'https://intelligence.inversolabs.us/mcp' --transport streamable-http
mcp_servers:
us-inversolabs-x402-compatibility-intelligence:
url: "https://intelligence.inversolabs.us/mcp" {
"McpServers": {
"us-inversolabs-x402-compatibility-intelligence": {
"Transport": "http",
"Url": "https://intelligence.inversolabs.us/mcp"
}
}
} assistant mcp add us-inversolabs-x402-compatibility-intelligence -t streamable-http -u 'https://intelligence.inversolabs.us/mcp'
{
"mcpServers": {
"us-inversolabs-x402-compatibility-intelligence": {
"type": "http",
"url": "https://intelligence.inversolabs.us/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.
- 18 Sept 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Sept 26 +45
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.70 ▲ functional
- 11 Sept 26 −42
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +41
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.43 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 27 Aug 26 −35
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 53
First indexed and scored.
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 20 Sept 2026 · Probed https://intelligence.inversolabs.us/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=inversolabs.us | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 92d682f4614ee88e13e8cba8a2d22a74 |
| SANs: inversolabs.us, *.inversolabs.us | ||||||
| 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 intelligence.inversolabs.us. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| us. | present | 59017 | 8 | Verified |
| inversolabs.us. | 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 | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://intelligence.inversolabs.us/mcp | HTTP error | 530 | |
| http (plaintext) | http://intelligence.inversolabs.us/mcp | Inconclusive | 530 |
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 →
x402_compatibility_intelligence x402 Payment Pre-Sign Validation, Facilitator Compatibility, Protocol Diagnostics & Settlement Risk ~76
Validate an x402 payment before signing: check facilitator compatibility, payment-protocol diagnostics, network and asset support, replay risk, and settlement risk from maintained compatibility evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| discovery_mode | string | – | – |
| facilitator_url | string | yes | – |
| offer | object | yes | – |
| policy | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assessed_at | string | yes | – |
| evidence | array | yes | – |
| limitations | array | yes | – |
| reasons | array | yes | – |
| recovery | object|null | – | – |
| safe_to_sign | boolean | yes | – |
| selected | object|null | yes | – |
| verdict | string | yes | – |
No examples provided.
What is the x402 Compatibility Intelligence MCP server?
x402 Compatibility Intelligence is an MCP server listed in the public MCP registry as us.inversolabs/x402-compatibility-intelligence. Preflight x402 payment compatibility with structured risk evidence and remediation guidance. This page covers its hosted endpoint (https://intelligence.inversolabs.us/mcp).
Is the x402 Compatibility Intelligence MCP server safe to use?
x402 Compatibility Intelligence scores 18 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 x402 Compatibility Intelligence MCP server expose?
x402 Compatibility Intelligence exposes 1 tool: x402_compatibility_intelligence. Their descriptions and schemas cost roughly 76 tokens of context every time the server is loaded.
Does the x402 Compatibility Intelligence MCP server require authentication?
No. We connected to x402 Compatibility Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the x402 Compatibility Intelligence MCP server still maintained?
x402 Compatibility Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.