MCP x402 - Evidence-Backed Web Verification
io.github.Diogoup26/mcp-x402Diogoup26streamable-httpv1.2.12Scanned
Evidence-backed pre-purchase checks for offer terms, seller trust and policy compliance.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MCP x402 - Evidence-Backed Web Verification can do
The MCP x402 - Evidence-Backed Web Verification is published by the GitHub account Diogoup26. It has 4 tools. It can create or change data (2 tools: consultar_ia and verificar_condicoes), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (analisar_url and verificar_condicoes); 2 tools can send data out of your system (analisar_url and verificar_condicoes).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 1.2.12.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
consultar_iaUse for general questions that do not require live web retrieval.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
verificar_condicoesUse before an agent trusts, buys or acts to test 1 to 10 explicit conditions against one public HTTP or HTTPS page.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
analisar_urlUse to fetch one public HTTP or HTTPS page and return a source-bounded report with summary, facts, risks and recommended actions.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "analisar_url" says "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "fetch" and "http": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
preview_verificationUse this free static preview before paying for verificar_condicoes.No findings
Why it is in this group
- The name "preview_verification" says "preview": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp-x402-production.up.railway.app/mcp: tools/list returned 4 tools to an anonymous client, including consultar_ia (write), verificar_condicoes (write)
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 3 to 2
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 2.View diff
- Tools that change things, listed without credentials: 3 to 2
Tools1 added, 3 changed.+1 added~3 changedView diff
- Added:preview_verificationOnly reads
- Changed:analisar_urlOnly readstitledescriptionannotations
- Changed:consultar_iaChanges thingstitledescriptionannotations
- Changed:verificar_condicoesChanges thingstitledescriptionannotations
Install
Pinned to version 1.2.12. Values in angle brackets are yours to fill in.
claude mcp add --transport http x402 https://mcp-x402-production.up.railway.app/mcpclaude mcp add --transport http x402 https://mcp-x402-production.up.railway.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__x402__preview_verification"
],
"ask": [
"mcp__x402__consultar_ia",
"mcp__x402__analisar_url",
"mcp__x402__verificar_condicoes"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as x402. Review it before you use it.
Capability tags behind 2 rules
- mcp__x402__analisar_url untrusted-input, outbound
- mcp__x402__verificar_condicoes untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Diogoup26/mcp-x402/verify?hash=c6d49ca58037165ab1ec432ca741d8137b667f3a2f92c280cc9cf874d88b8155" | jq -e '.changed == false'Pinned hash c6d49ca58037, from Nov 14, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Diogoup26/mcp-x402/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Diogoup26/mcp-x402)Source: MCP Registry · repository. Synced Nov 1, 2026, 17:17 UTC.
MCP x402 - Evidence-Backed Web Verification: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MCP x402 - Evidence-Backed Web Verification safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MCP x402 - Evidence-Backed Web Verification delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MCP x402 - Evidence-Backed Web Verification do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MCP x402 - Evidence-Backed Web Verification have?
- 4 tools: 2 write, 2 read. consultar_ia, verificar_condicoes, preview_verification and analisar_url.
Does the MCP x402 - Evidence-Backed Web Verification need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MCP x402 - Evidence-Backed Web Verification send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): analisar_url and verificar_condicoes.
Has the MCP x402 - Evidence-Backed Web Verification changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 1, 2026. Every change is on this page and in its Atom feed.