MCP Verification Gate: check an MCP server or an A2A agent before you connect or…
io.github.ogasurfproject-jpg/hs-verify-gateogasurfproject-jpgstreamable-httpv0.4.24Scanned
Check an A2A agent before you delegate, or an MCP server's measured conduct. Free, no key.
6 tools: 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 3
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
4 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 Verification Gate: check an MCP server or an A2A agent before you connect or… can do
The MCP Verification Gate: check an MCP server or an A2A agent before you connect or… is published by the GitHub account ogasurfproject-jpg. It has 6 tools. It can create or change data (4 tools: check_conformance, verify_verdict, is_verified and preflight_agent), but cannot delete data. 2 tools only read.
3 tools bring in text other people can write (check_conformance, lookup_server and preflight_agent); 3 tools can send data out of your system (check_conformance, lookup_server and is_verified).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.4.24.
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.
6 tools
Changes things 4Claude Code: ask
check_conformanceMeasure a public MCP endpoint against five conditions: it speaks MCP, it publishes an A2A agent card, it declares who pays it, identical input returns identical output, and the ver…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.endpoint): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Measure a public MCP endpoint against five conditions: it speaks MCP, it publishes an A2A agent card, it declares who pays it, identical input returns identical output, and the verdict itself can be recomputed by anyone. Free, no key. Conformance and disclosure only; this says nothing about whether any figure the checked server returns is correct. By default no tool on the checked server is called, so determinism comes back as not measured rather than guessed. It is measured when the owner has published /.well-known/mcp-conduct.json with allow_tool_call true.
Annotations the server declares
- title: Check an MCP server for conformance and disclosure
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
is_verifiedA single machine-first answer for an agent deciding whether to trust an MCP endpoint BEFORE it connects.Can 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
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it A single machine-first answer for an agent deciding whether to trust an MCP endpoint BEFORE it connects. Returns verified (true only when the latest scheduled measurement passed every measured condition; null otherwise, never false), a state enum saying which case it is, measured_at, and a record_sha256 with a recompute_url so you can check the verdict without trusting this gate. Reads the stored register only: it contacts nothing and measures nothing. Absent and pending are reported honestly and are NOT negative verdicts. For a fresh measurement rather than the stored one, use check_conformance.
Annotations the server declares
- title: One glance: is this MCP server verified, with proof
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
preflight_agentCall this before handing work to an A2A agent you have not used before.Reads text others write1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- 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.
Findings
- Warn
The server marks "preflight_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.
Description, as the server wrote it Call this before handing work to an A2A agent you have not used before. Fetches the agent's public card (https://<agent>/.well-known/agent-card.json, one request), reports whether it declares the A2A Conduct Extension, who it says pays it (the compensation declaration, as declared and not verified), whether the card carries a signature, the endpoints it asks to be measured on, and this register's stored reading for each (verified is true only when the latest scheduled measurement passed; null otherwise, never false), plus where to file your own witness walk. Measures nothing new and returns counts and pointers, never a score. An agent that does not declare the extension is reported as such, which is not a negative verdict.
Annotations the server declares
- title: Before delegating: check an A2A agent's card, who pays it, and its register reading
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_verdictTake a verdict this gate issued and recompute its record_sha256 independently.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 Take a verdict this gate issued and recompute its record_sha256 independently. Removes record_sha256 and recompute_note, serialises the remainder in key order, and hashes it. Returns whether the verdict was altered after it was issued. You do not have to trust the party that issued the verdict, including this one.
Annotations the server declares
- title: Recompute a verdict hash without trusting the issuer
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_conditionsReturn the five conditions this gate measures, what it explicitly does not verify, and the tier definitions.No findings
Why it is in this group
- The name "get_conditions" says "get": a word for reading.
Description, as the server wrote it Return the five conditions this gate measures, what it explicitly does not verify, and the tier definitions. Takes no arguments and returns identical output every time. Read this before running a check so you know what a verdict does and does not claim.
Annotations the server declares
- title: Get the conformance conditions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_serverReturns one record (not a list).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "lookup_server" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): 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 Returns one record (not a list). Look up what this register already holds about an MCP endpoint: whether it is watched, how often it is re-measured, how many measurements exist, when the first and latest were taken, and the latest verdict with the record_sha256 you can recompute yourself. Reads stored measurements only. It contacts nothing and measures nothing, so use check_conformance for a fresh reading. An endpoint that is absent is reported as absent and that is NOT a negative verdict: it means nobody has measured it here, not that it failed.
Annotations the server declares
- title: Look up an MCP server on this register
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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 write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- 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, 19:26 UTC, unchanged since Oct 22, 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
- 4
- 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 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://gate.horizonshield.dev/mcp: tools/list returned 6 tools to an anonymous client, including check_conformance (write), verify_verdict (write), is_verified (write), preflight_agent (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnpreflight_agent
The server marks "preflight_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.4.24. Values in angle brackets are yours to fill in.
claude mcp add --transport http hs-verify-gate https://gate.horizonshield.dev/mcpclaude mcp add --transport http hs-verify-gate https://gate.horizonshield.dev/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__hs-verify-gate__get_conditions"
],
"ask": [
"mcp__hs-verify-gate__check_conformance",
"mcp__hs-verify-gate__verify_verdict",
"mcp__hs-verify-gate__lookup_server",
"mcp__hs-verify-gate__is_verified",
"mcp__hs-verify-gate__preflight_agent"
],
"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 hs-verify-gate. Review it before you use it.
Capability tags behind 4 rules
- mcp__hs-verify-gate__check_conformance untrusted-input, outbound
- mcp__hs-verify-gate__lookup_server untrusted-input, outbound
- mcp__hs-verify-gate__is_verified outbound
- mcp__hs-verify-gate__preflight_agent untrusted-input
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.ogasurfproject-jpg/hs-verify-gate/verify?hash=00517ca214701e282615285dc3a426d3440b555d614e8850f01fa22613fcb552" | jq -e '.changed == false'Pinned hash 00517ca21470, from Nov 20, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ogasurfproject-jpg/hs-verify-gate/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ogasurfproject-jpg/hs-verify-gate)Source: MCP Registry · repository. Synced Nov 6, 2026, 13:18 UTC.
MCP Verification Gate: check an MCP server or an A2A agent before you connect or…: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MCP Verification Gate: check an MCP server or an A2A agent before you connect or… safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding 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 Verification Gate: check an MCP server or an A2A agent before you connect or… delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MCP Verification Gate: check an MCP server or an A2A agent before you connect or… 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 Verification Gate: check an MCP server or an A2A agent before you connect or… have?
- 6 tools: 4 write, 2 read. check_conformance, verify_verdict, is_verified, preflight_agent, get_conditions and lookup_server.
Does the MCP Verification Gate: check an MCP server or an A2A agent before you connect or… need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MCP Verification Gate: check an MCP server or an A2A agent before you connect or… send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_conformance, lookup_server and is_verified.
Has the MCP Verification Gate: check an MCP server or an A2A agent before you connect or… changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.