MCP x402 - Evidence-Backed Web Verification
REMOTE · MCP-X402-PRODUCTION.UP.RAILWAY.APP
Evidence-backed pre-purchase checks for offer terms, seller trust and policy compliance.
Available components
Last scanned (18 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Search and Retrieval
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 552 tokens (~138/item across 4 items; 4 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Nov 26 +5
- Authorization: unverified → partial ▲ security
- The server changed its declared name: diogo-ai-service → mcp-x402 security
- Tool “analisar_url” rewrote its description, which is the text the model reads security
- Tool “consultar_ia” rewrote its description, which is the text the model reads security
- Tool “verificar_condicoes” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool “analisar_url” now declares an output schema ▲ functional
- Tool “consultar_ia” now declares an output schema ▲ functional
- Tool “verificar_condicoes” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 1.2.10 → 1.2.12 functional
- Server version: 1.2.9 → 1.2.10 functional
- New tool “preview_verification” functional
- Tool “analisar_url” changed its title: Analisar página web → Analyze a public web page cosmetic
- Tool “consultar_ia” changed its title: Consultar IA → General AI consultation cosmetic
- Tool “verificar_condicoes” changed its title: Verificar condições → Verify conditions with evidence cosmetic
- 28 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
- 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
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 29 Aug 26 0
- Server version: 1.2.8 → 1.2.9 functional
- 27 Aug 26 0
- Server version: 1.2.7 → 1.2.8 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 6 Nov 2026 · Probed https://mcp-x402-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-x402-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| railway.app. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-x402-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-x402-production.up.railway.app/mcp | HTTPS enforced | 301 | https://mcp-x402-production.up.railway.app/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 →
analisar_url Analyze a public web page ~130
Use to fetch one public HTTP or HTTPS page and return a source-bounded report with summary, facts, risks and recommended actions. The optional objective controls focus but is never evidence. It does not consult other sources; use verificar_condicoes for condition-by-condition decisions. PT: Analisa uma página pública sem usar fontes externas.
| Name | Type | Req | Description |
|---|---|---|---|
| objetivo | string | – | Foco opcional do relatório, até 500 caracteres; orienta a análise mas não é tratado como prova. |
| url | string | yes | URL HTTP ou HTTPS pública a extrair. Endereços locais, privados e não públicos são rejeitados. |
| Name | Type | Req | Description |
|---|---|---|---|
| report | string | yes | – |
| source | string | yes | – |
| title | string | yes | – |
No examples provided.
consultar_ia General AI consultation ~98
Use for general questions that do not require live web retrieval. Returns a concise model answer and does not fetch URLs or verify current facts. Use analisar_url for a source-bounded page report and verificar_condicoes for evidence-backed decisions. PT: Use para perguntas gerais sem pesquisa web em tempo real.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | Pergunta ou instrução, entre 1 e 4000 caracteres. Não pressupõe pesquisa web em tempo real. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
No examples provided.
preview_verification Preview an evidence-backed verification for free ~118
Use this free static preview before paying for verificar_condicoes. Choose offer_terms to inspect warranty, returns and availability; seller_trust to inspect seller identity and authorization; or policy_compliance to inspect required policy terms. It performs no web request, OpenAI call or payment and returns a realistic structured example plus the exact paid next step. PT: Pré-visualização gratuita e estática da verificação.
| Name | Type | Req | Description |
|---|---|---|---|
| useCase | string | – | Static example to return: offer_terms, seller_trust or policy_compliance. Defaults to offer_terms. |
| Name | Type | Req | Description |
|---|---|---|---|
| exampleInput | object | yes | – |
| exampleOutput | object | yes | – |
| kind | string | yes | – |
| label | string | yes | – |
| liveRequestPerformed | boolean | yes | – |
| network | string | yes | – |
| nextStep | string | yes | – |
| openAiUsed | boolean | yes | – |
| paidEndpoint | string | yes | – |
| paidTool | string | yes | – |
| paymentRequired | boolean | yes | – |
| preflightEndpoint | string | yes | – |
| price | string | yes | – |
| useCase | string | yes | – |
No examples provided.
verificar_condicoes Verify conditions with evidence ~206
Use before an agent trusts, buys or acts to test 1 to 10 explicit conditions against one public HTTP or HTTPS page. Best fits offer and warranty checks, seller identity or authorization checks, and policy compliance checks. Returns confirmed, rejected or uncertain for every condition with textual evidence when available, plus source, verifiedAt, verificationId and pageHash. Missing evidence produces uncertain, not a false confirmation. Use preview_verification first when the buyer needs a free example. PT: Verifica condições com prova auditável.
| Name | Type | Req | Description |
|---|---|---|---|
| condicoes | array | yes | Lista de 1 a 10 condições concretas e verificáveis; cada condição deve ter entre 3 e 300 caracteres. |
| contexto | string | – | Contexto opcional, até 500 caracteres, usado apenas para interpretar as condições e nunca como prova da página. |
| url | string | yes | URL HTTP ou HTTPS pública onde as condições serão verificadas. Endereços locais, privados e não públicos são rejeitados. |
| Name | Type | Req | Description |
|---|---|---|---|
| decisao | object | yes | – |
| pageHash | string | yes | – |
| source | string | yes | – |
| title | string | yes | – |
| verificationId | string | yes | – |
| verifiedAt | string | yes | – |
No examples provided.
How do I install the MCP x402 - Evidence-Backed Web Verification server?
MCP x402 - Evidence-Backed Web Verification is a hosted endpoint at https://mcp-x402-production.up.railway.app/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-x402-production.up.railway.app
claude mcp add --transport http diogoup26-mcp-x402 'https://mcp-x402-production.up.railway.app/mcp'
What is the MCP x402 - Evidence-Backed Web Verification server?
MCP x402 - Evidence-Backed Web Verification is listed in the public MCP registry as io.github.Diogoup26/mcp-x402. Evidence-backed pre-purchase checks for offer terms, seller trust and policy compliance. This page covers its hosted endpoint (https://mcp-x402-production.up.railway.app/mcp).
Is the MCP x402 - Evidence-Backed Web Verification server safe to use?
MCP x402 - Evidence-Backed Web Verification scores 88 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 MCP x402 - Evidence-Backed Web Verification server expose?
MCP x402 - Evidence-Backed Web Verification exposes 4 tools: preview_verification, consultar_ia, analisar_url, verificar_condicoes. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.
Does the MCP x402 - Evidence-Backed Web Verification server require authentication?
No. We connected to MCP x402 - Evidence-Backed Web Verification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP x402 - Evidence-Backed Web Verification server still maintained?
MCP x402 - Evidence-Backed Web Verification is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MCP x402 - Evidence-Backed Web Verification server?
VerifyMCP ran 13 checks on MCP x402 - Evidence-Backed Web Verification, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.