io.github.robertoyanguas-ops/assay
REMOTE · ASSAY-207908449630.US-CENTRAL1.RUN.APP
A2A & MCP Pre-Flight Security: SHA-256 tool schema rug-pull detection and liveness grades.
Available components
Last scanned (4 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 823 tokens (~205/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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “assay_preflight” rewrote its description, which is the text the model reads security
- Tool “assay_probe” rewrote its description, which is the text the model reads security
- Schema quality: 232 → 205 ▲ functional
- Tool “assay_preflight” now declares an output schema ▲ functional
- Tool “assay_probe” now declares an output schema ▲ functional
- Tool “assay_verify_delivery” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- Server version: 0.5.2 → 0.5.3 functional
- New tool “assay_get_ledger_policy” functional
- 17 Oct 26 +9
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “assay_preflight” rewrote its description, which is the text the model reads security
- Tool “assay_probe” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- Server version: 0.4.2 → 0.5.2 functional
- New tool “assay_verify_delivery” functional
- “assay_preflight” reworded the description of “expected_tools_hash” cosmetic
- “assay_preflight” reworded the description of “target” cosmetic
- “assay_probe” reworded the description of “target” cosmetic
- Tool “assay_preflight” changed its title: assay_preflight → Pre-Flight MCP & A2A Security Gate cosmetic
- Tool “assay_probe” changed its title: assay_probe → Record Live Endpoint Conformance Observation cosmetic
- 16 Oct 26 58
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 18 Oct 2026 · Probed https://assay-207908449630.us-central1.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WE2,O=Google Trust Services,C=US | 28 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f744cc9b919363521044a86106657ba7 |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WE2,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 | 7ff32d6b409d15d5965b05873a7c72e0 |
| 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 assay-207908449630.us-central1.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://assay-207908449630.us-central1.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://assay-207908449630.us-central1.run.app/mcp | HTTPS enforced | 302 | https://assay-207908449630.us-central1.run.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 →
assay_get_ledger_policy Query Historical Ledger & Manage Expected Schema Hashes ~185
Query historical conformance observations, rug-pull drift events, and canonical SHA-256 tools/list policy hashes (expected_tools_hash) for a target MCP or A2A endpoint. Returns {verdict, reason, receipt, pinned_tools_hash, observations, dossier}. Use to audit historical ledger data or pin expected_tools_hash in mcp-lock.json; for pre-flight allow/deny gating use assay_preflight.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_tools_hash | string | – | Optional 64-char SHA-256 hex digest of the canonical MCP tools/list schema from mcp-lock.json. If set and the live hash differs, verdict is 'deny'. |
| target | string | yes | Public HTTPS URL of the remote MCP server, A2A agent, or x402 endpoint to inspect (e.g. 'https://tandem.ac/mcp'). Private and loopback IPs are blocked. |
| Name | Type | Req | Description |
|---|---|---|---|
| dossier | object | – | – |
| reason | string | – | – |
| receipt | string | yes | – |
| verdict | string | yes | – |
No examples provided.
assay_preflight Pre-Flight MCP & A2A Security Gate ~213
Evaluate a remote MCP, A2A, or x402 endpoint before calling or paying it. Probes live JSON-RPC reachability, hashes tools/list (SHA-256), checks expected_tools_hash for silent rug-pull drift, and scans for prompt-injection poisoning. Returns {verdict ('allow'|'warn'|'deny'), reason, receipt ('asr_rcpt_...'), dossier}. Use before tool execution or payment; for post-payment disputes use assay_verify_delivery; for raw telemetry indexing use assay_probe. First 5 calls/IP free.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_tools_hash | string | – | Optional 64-char SHA-256 hex digest of the canonical MCP tools/list schema from mcp-lock.json. If set and the live hash differs, verdict is 'deny'. |
| target | string | yes | Public HTTPS URL of the remote MCP server, A2A agent, or x402 endpoint to inspect (e.g. 'https://tandem.ac/mcp'). Private and loopback IPs are blocked. |
| Name | Type | Req | Description |
|---|---|---|---|
| dossier | object | – | – |
| reason | string | – | – |
| receipt | string | yes | – |
| verdict | string | yes | – |
No examples provided.
assay_probe Record Live Endpoint Conformance Observation ~160
Execute a live HTTP, A2A agent-card, and MCP tools/list probe against a target URL and record the observation in the Assay Observatory ledger without pre-flight policy gating. Returns the updated dossier {target, grade ('A+' to 'F'), score (0-100), mcp_tools, tools_hash, rug_pulls, poison_flags, latency_ms, receipt}. Use to index a server or refresh leaderboard telemetry; for allow/deny gating use assay_preflight. First 5 calls/IP free.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Public HTTPS URL of the remote MCP server, A2A agent, or x402 endpoint to inspect (e.g. 'https://tandem.ac/mcp'). Private and loopback IPs are blocked. |
| Name | Type | Req | Description |
|---|---|---|---|
| dossier | object | – | – |
| reason | string | – | – |
| receipt | string | yes | – |
| verdict | string | yes | – |
No examples provided.
assay_verify_delivery Verify Post-Payment x402 Delivery & Mint SLA Receipt ~233
Independently probe a paid x402/A2A provider after payment to verify delivery or confirm an SLA breach. Combines reported status_code with a live probe and binds tx_hash into an HMAC-SHA256 receipt. Returns {verdict ('delivery_verified'|'sla_breach_confirmed'), sla_breach, grade, score, sla_receipt ('asr_sla_...')}. Use only after paying a provider; before payment use assay_preflight. First 5 calls/IP free.
| Name | Type | Req | Description |
|---|---|---|---|
| status_code | string | – | HTTP status code returned by the paid endpoint (e.g. '200', '502', '504'). Codes >= 500 trigger verdict='sla_breach_confirmed'. |
| target | string | yes | Public HTTPS URL of the remote MCP server, A2A agent, or x402 endpoint to inspect (e.g. 'https://tandem.ac/mcp'). Private and loopback IPs are blocked. |
| tx_hash | string | – | On-chain payment transaction hash (0x Base USDC hash or base58 Solana signature) to bind into the signed SLA receipt. |
| Name | Type | Req | Description |
|---|---|---|---|
| dossier | object | – | – |
| reason | string | – | – |
| receipt | string | yes | – |
| verdict | string | yes | – |
No examples provided.
How do I install the io.github.robertoyanguas-ops/assay MCP server?
io.github.robertoyanguas-ops/assay is a hosted endpoint at https://assay-207908449630.us-central1.run.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 · assay-207908449630.us-central1.run.app
claude mcp add --transport http robertoyanguas-ops-assay 'https://assay-207908449630.us-central1.run.app/mcp'
What is the io.github.robertoyanguas-ops/assay MCP server?
io.github.robertoyanguas-ops/assay is an MCP server listed in the public MCP registry as io.github.robertoyanguas-ops/assay. A2A & MCP Pre-Flight Security: SHA-256 tool schema rug-pull detection and liveness grades. This page covers its hosted endpoint (https://assay-207908449630.us-central1.run.app/mcp).
Is the io.github.robertoyanguas-ops/assay MCP server safe to use?
io.github.robertoyanguas-ops/assay scores 68 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 io.github.robertoyanguas-ops/assay MCP server expose?
io.github.robertoyanguas-ops/assay exposes 4 tools: assay_preflight, assay_probe, assay_verify_delivery, assay_get_ledger_policy. Their descriptions and schemas cost roughly 791 tokens of context every time the server is loaded.
Does the io.github.robertoyanguas-ops/assay MCP server require authentication?
No. We connected to io.github.robertoyanguas-ops/assay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.robertoyanguas-ops/assay MCP server still maintained?
io.github.robertoyanguas-ops/assay is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.