VEYA
REMOTE · MCP.VEYANET.TECH
Check, limit, record and prove AI agent actions with 2-of-3 validators and onchain proofs.
Available components
Last scanned (3 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 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 Security57
- 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 55 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 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 Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 4414 tokens (~80/item across 55 items; 55 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 31% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "veya_sealed_execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Server version: 1.2.11 → 1.2.12 functional
- New tool “veya_tier” functional
- 31 Oct 26 +1
- Tool “veya_anchor_proof” rewrote its description, which is the text the model reads security
- Tool “veya_paid_call” rewrote its description, which is the text the model reads security
- Tool “veya_ping_chain” rewrote its description, which is the text the model reads security
- Tool “veya_seal_decision” rewrote its description, which is the text the model reads security
- Tool “veya_writes_status” rewrote its description, which is the text the model reads security
- Server version: 1.2.10 → 1.2.11 functional
- “veya_paid_call” reworded the description of “environmentUuid” cosmetic
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Tool “veya_paid_call” rewrote its description, which is the text the model reads security
- Tool “veya_paid_discover” rewrote its description, which is the text the model reads security
- Tool “veya_paid_run” rewrote its description, which is the text the model reads security
- Schema quality: 66 → 79 ▼ functional
- “veya_paid_call” added a required parameter “apiKey”, so existing callers break ▼ functional
- “veya_paid_run” added a required parameter “apiKey”, so existing callers break ▼ functional
- Tool coverage: 22% → 30% ▲ functional
- Server version: 1.2.9 → 1.2.10 functional
- “veya_paid_call” added an optional parameter “environmentUuid” cosmetic
- “veya_paid_call” added an optional parameter “robinhoodPrivateKey” cosmetic
- “veya_paid_call” added an optional parameter “solanaPrivateKey” cosmetic
- “veya_paid_run” added an optional parameter “robinhoodPrivateKey” cosmetic
- “veya_paid_call” reworded the description of “idempotencyKey” cosmetic
- “veya_paid_call” reworded the description of “input” cosmetic
- “veya_paid_call” reworded the description of “resourceId” cosmetic
- “veya_paid_call” reworded the description of “taskBudgetAtomic” cosmetic
- “veya_paid_call” reworded the description of “taskId” cosmetic
- “veya_paid_call” reworded the description of “url” cosmetic
- “veya_paid_run” reworded the description of “resume” cosmetic
- “veya_paid_run” reworded the description of “runId” cosmetic
- “veya_paid_run” made “runId” optional cosmetic
- 25 Oct 26 0
- Server version: 1.2.8 → 1.2.9 functional
- New tool “veya_paid_call” functional
- New tool “veya_paid_discover” functional
- New tool “veya_paid_run” 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 5 Nov 2026 · Probed https://mcp.veyanet.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=veyanet.tech | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a99e9528dc6bc2c513602fb971abd987 |
| SANs: veyanet.tech, *.veyanet.tech | ||||||
| CN=WE1,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 | 7ff31977972c224a76155d13b6d685e3 |
| 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 mcp.veyanet.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| veyanet.tech. | 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://mcp.veyanet.tech/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.veyanet.tech/mcp | HTTPS enforced | 301 | https://mcp.veyanet.tech/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 →
veya_verify_commitment_onchain ~40
Parse Veya.sol events from a tx and eth_call commitments(digest) for each CommitmentStored
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | – |
No output schema declared.
No examples provided.
veya_verify_proof_api ~44
Check a commitment or anchor transaction through the product API. A registration transaction is not a proof and returns NOT_VEYA_TX.
| Name | Type | Req | Description |
|---|---|---|---|
| signature | string | yes | – |
No output schema declared.
No examples provided.
veya_verify_secure_message ~40
Verify ML-DSA signature on a secure routed message envelope
| Name | Type | Req | Description |
|---|---|---|---|
| message | object | yes | – |
| senderPublicKeyHex | string | yes | – |
No output schema declared.
No examples provided.
veya_verify_transaction ~31
Verify a Veya.sol commitment from a Robinhood Chain tx hash
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | – |
No output schema declared.
No examples provided.
veya_writes_status ~32
Reports how on-chain writes work on this server: your own wallet sends them, the host signer does not
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the VEYA MCP server?
VEYA is a hosted endpoint at https://mcp.veyanet.tech/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.veyanet.tech
claude mcp add --transport http veyanet-veya 'https://mcp.veyanet.tech/mcp'
What is the VEYA MCP server?
VEYA is an MCP server listed in the public MCP registry as io.github.veyanet/veya. Check, limit, record and prove AI agent actions with 2-of-3 validators and onchain proofs. This page covers its hosted endpoint (https://mcp.veyanet.tech/mcp).
Is the VEYA MCP server safe to use?
VEYA scores 65 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 VEYA MCP server expose?
VEYA exposes 55 tools: veya_describe, veya_ping_chain, veya_hash_blake3, veya_verify_transaction, veya_api_health, and 50 more. Their descriptions and schemas cost roughly 4,414 tokens of context every time the server is loaded.
Does the VEYA MCP server require authentication?
No. We connected to VEYA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VEYA MCP server still maintained?
VEYA is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.