Yakumo Verification Gate: conformance and disclosure checker for MCP servers
REMOTE · HS-VERIFY-GATE.OGA-SURF-PROJECT.WORKERS.DEV · SCANNED AUG 8
Conformance and disclosure checker for MCP servers. Free, no key, verdicts you can recompute.
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 →
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 call this server, and 3 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 315 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · hs-verify-gate.oga-surf-project.workers.dev
claude mcp add --transport http ogasurfproject-jpg-hs-verify-gate https://hs-verify-gate.oga-surf-project.workers.dev/mcp
[mcp_servers.ogasurfproject-jpg-hs-verify-gate] url = "https://hs-verify-gate.oga-surf-project.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ogasurfproject-jpg-hs-verify-gate": {
"type": "remote",
"url": "https://hs-verify-gate.oga-surf-project.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add ogasurfproject-jpg-hs-verify-gate --url https://hs-verify-gate.oga-surf-project.workers.dev/mcp --transport streamable-http
mcp_servers:
ogasurfproject-jpg-hs-verify-gate:
url: "https://hs-verify-gate.oga-surf-project.workers.dev/mcp" {
"mcpServers": {
"ogasurfproject-jpg-hs-verify-gate": {
"type": "http",
"url": "https://hs-verify-gate.oga-surf-project.workers.dev/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.
- 8 Aug 26 59
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 8 Aug 2026 · Probed https://hs-verify-gate.oga-surf-project.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oga-surf-project.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 22 Jul 2026 | 20 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5e61ad03e102b9cefc1c279dfad3b36af04 |
| SANs: *.oga-surf-project.workers.dev, oga-surf-project.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
DNSSEC insecure
Validation of hs-verify-gate.oga-surf-project.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hs-verify-gate.oga-surf-project.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://hs-verify-gate.oga-surf-project.workers.dev/mcp | Served over HTTP | 200 |
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.
check_conformance Check an MCP server for conformance and disclosure ~165
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. Set allow_tool_call true only for a server you control.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_tool_call | boolean | – | Consent to executing one tool on the checked server, twice, with empty arguments. Only set this for a server you own. Default false. |
| endpoint | string | yes | https URL of the MCP endpoint to measure |
No output schema declared.
No examples provided.
get_conditions Get the conformance conditions ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_verdict Recompute a verdict hash without trusting the issuer ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | The full verdict object as returned by check_conformance or GET /self |
No output schema declared.
No examples provided.