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 (19 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 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 Management47
- Stability observed for 14 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 4 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_account ~72
Return the wallet bound to a product API key
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_anchor_pq_attestation ~111
Link PQ identity hash to execution hash on Veya.sol from YOUR wallet
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Required for on-chain writes. |
| environmentUuidHex | string | yes | – |
| executionHashHex | string | yes | – |
| identityHashHex | string | yes | – |
| payerPrivateKey | string | – | User wallet private key that pays gas. Prefer VEYA_PAYER_PRIVATE_KEY on a self-hosted MCP. |
No output schema declared.
No examples provided.
veya_anchor_proof ~142
Anchor a content proof on Veya.sol from YOUR wallet (apiKey + payerPrivateKey). Does not use the hosted signer.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| content | string | yes | – |
| environmentId | string | – | – |
| label | string | yes | – |
| payerPrivateKey | string | – | User wallet private key that pays gas. Prefer VEYA_PAYER_PRIVATE_KEY on a self-hosted MCP. |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_api_health ~28
Check the VEYA API /health status (api.veyanet.tech), including fleet status
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
veya_attest_execution ~114
attestExecution on Veya.sol from YOUR wallet with ML-DSA bytes
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Required for on-chain writes. |
| blake3HashHex | string | yes | – |
| environmentUuidHex | string | yes | – |
| mldsaSigHex | string | yes | – |
| payerPrivateKey | string | – | User wallet private key that pays gas. Prefer VEYA_PAYER_PRIVATE_KEY on a self-hosted MCP. |
No output schema declared.
No examples provided.
veya_boundnet_invoke ~110
Invoke a Boundnet / coordination tool via product API (policy gated)
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| arguments | object | – | – |
| environmentId | string | yes | – |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
| toolName | string | yes | – |
No output schema declared.
No examples provided.
veya_client_run_consensus ~53
Deprecated: use veya_run_consensus. Same server validator list. Needs a product API key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| payload | object | – | – |
| taskId | string | yes | – |
No output schema declared.
No examples provided.
veya_commitment_exists ~31
eth_call Veya.sol commitments(bytes32) for a digest
| Name | Type | Req | Description |
|---|---|---|---|
| digestHex | string | yes | – |
No output schema declared.
No examples provided.
veya_create_environment ~156
Create a workspace in the product API. This does not spend gas and sends no transaction. Guests and non-keys are refused. type is stored for the API and defaults to research when omitted. Names that start with test, demo, tmp, sandbox, or e2e are refused. Use a real workspace name of at least 6 characters, or a name that starts with VEYA.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| name | string | yes | – |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
| type | string | – | – |
No output schema declared.
No examples provided.
veya_deploy_agent ~147
Create an agent in a workspace. This does not spend gas and sends no transaction. Limit the agent with permissionConfig.allowedTools. If allowedTools is omitted, the agent cannot call a tool. type is stored for the API and defaults to coordination when omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| agentKind | string | – | – |
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| environmentId | string | yes | – |
| permissionConfig | object | – | – |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
| type | string | – | – |
No output schema declared.
No examples provided.
veya_describe ~25
Service info: AES-256-GCM sealed execution and the selected settlement profile
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
veya_get_environment ~77
Get one environment by id
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| environmentId | string | yes | – |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_guest_login ~32
Create a guest session on the product API (Use listing only). Guest cannot mint API keys or write from MCP.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
veya_hash_blake3 ~30
Compute BLAKE3 hex digest (commitment helper)
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | – |
No output schema declared.
No examples provided.
veya_invalidate_memory ~44
Nullify one memory row owned by this API key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| environmentId | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
veya_list_agents ~77
List agents in an environment
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| environmentId | string | yes | – |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_list_api_memory ~89
List memory entries via product API for an environment
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| environmentId | string | yes | – |
| scope | string | – | – |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_list_environments ~81
List environments for a product API key (guest JWT sees showcase / Use scope only)
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_list_executions ~82
List executions for an environment via product API
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| environmentId | string | yes | – |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_list_proofs ~73
List Use-mode proof anchors for the account
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_paid_call ~610
Run one metered x402 resource call through the VEYA policy gate. Needs your VEYA apiKey, your Solana key (solanaPrivateKey, pays the USDC) and your Robinhood Chain key (robinhoodPrivateKey, signs the VEYA record and pays its ETH gas). Keys are used in memory for this call only and never stored. Before anything is signed VEYA checks the apiKey, both keys, your USDC and ETH balances, and the policy (tool, host, resource, network, asset, payee, per-call cap, task budget, input). It then pays, verifies the Solana payment at finalized, runs a 2-of-3 validator check, records a commitment on Robinhood Chain from your address and saves the run to your VEYA account. Every refusal returns decision blocked, a stable code and payment: null. The kill switch is operator-only; callers cannot change it. Allow at least 120 s for the tool call timeout.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your VEYA product API key (veya_dev_... or veya_live_...) from https://app.veyanet.tech (System -> API Keys). Every run is saved to this key's VEYA account. |
| environmentUuid | string | – | Optional VEYA environment on Veya.sol to record under (yours, from veya_register_environment). Defaults to the VEYA metered-call environment shown by veya_paid_discover. |
| idempotencyKey | string | yes | Unique per intended payment (per VEYA account). Repeating it returns the same run and never pays again; use a new key for a new payment. |
| input | object | yes | Input fields for the resource, exactly as listed by veya_paid_discover (string values only). |
| resourceId | string | – | A resource id from veya_paid_discover, e.g. tokens.asset-risk-summary. |
| robinhoodPrivateKey | string | – | Your own Robinhood Chain wallet private key (0x + 64 hex). It signs the VEYA record (storeCommitment on Veya.sol) and pays its small ETH gas, so the record comes from your address. Used in memory onl… |
| solanaPrivateKey | string | – | Your own Solana wallet secret key (base58, or a JSON array of 64 numbers). It pays the USDC for this one call from your wallet. Used in memory only, never stored, logged or returned. |
| taskBudgetAtomic | string | – | Optional task budget in USDC atomic units (6 decimals, 10000 = 0.01 USDC). Defaults to the policy budget; cannot exceed the policy maximum. |
| taskId | string | yes | Your task id. Calls with the same taskId share one task budget (per VEYA account). |
| url | string | – | Optional. Normally omit it and use resourceId; any URL outside the allowlist is blocked before payment. |
No output schema declared.
No examples provided.
veya_paid_discover ~68
Read-only. List the resources this VEYA policy allows, with their input fields, a live quote (nothing is sent), the provider quote and total charged to your task budget for each resource, the per-call cap, task budget maximum and default, and a policy preview. Cannot pay.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
veya_paid_run ~261
Read your VEYA runs. Private to the account of the apiKey you pass; another key cannot read them. With runId: one run (state, payment, validators, Robinhood record, receipt). Without runId: the runs saved to your VEYA account. With resume=true: retries Solana verification, the 2-of-3 validator check or the Robinhood record for an unfinished run; pass robinhoodPrivateKey to sign the record. Never pays.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your VEYA product API key (veya_dev_... or veya_live_...) from https://app.veyanet.tech (System -> API Keys). Every run is saved to this key's VEYA account. |
| resume | boolean | – | Retry the unfinished steps of this run. Never pays again. |
| robinhoodPrivateKey | string | – | Your own Robinhood Chain wallet private key (0x + 64 hex). It signs the VEYA record (storeCommitment on Veya.sol) and pays its small ETH gas, so the record comes from your address. Used in memory onl… |
| runId | string | – | Run id returned by veya_paid_call. Omit to list your runs. |
No output schema declared.
No examples provided.
veya_ping_chain ~19
Ping Robinhood Chain RPC — block, contract
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
veya_pq_fingerprint ~35
BLAKE3 fingerprint of an ML-DSA public key hex
| Name | Type | Req | Description |
|---|---|---|---|
| publicKeyHex | string | yes | – |
No output schema declared.
No examples provided.
veya_pq_keygen ~33
Generate an ML-DSA-44 post-quantum identity keypair (local, no chain write)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
veya_pq_sign ~39
Sign UTF-8 text with ML-DSA-44
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| privateKeyHex | string | yes | – |
No output schema declared.
No examples provided.
veya_pq_verify ~49
Verify an ML-DSA-44 signature over UTF-8 text
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| publicKeyHex | string | yes | – |
| signatureHex | string | yes | – |
No output schema declared.
No examples provided.
veya_prove ~90
Prove text, canonical JSON, or a receipt hash. Anchor writes only when a product API key and a payer key are passed.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | boolean | – | – |
| apiKey | string | – | – |
| environmentId | string | – | – |
| json | string | – | – |
| payerPrivateKey | string | – | – |
| text | string | – | – |
| txHash | string | – | – |
No output schema declared.
No examples provided.
veya_public_get_agent ~24
Fetch one public agent by id
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
veya_public_get_certificate ~24
Fetch one public certificate by id
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
veya_public_get_execution ~25
Fetch a public execution proof by id
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
veya_public_list_agents ~30
List public agent registry rows
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
veya_public_list_certificates ~33
List public certificate / attestation rows
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
veya_public_stats ~22
Public registry stats from the product API (verified agents / proofs)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
veya_read_agent_onchain ~34
Read agent record from Veya.sol by 16-byte UUID hex
| Name | Type | Req | Description |
|---|---|---|---|
| agentUuidHex | string | yes | – |
No output schema declared.
No examples provided.
veya_read_environment_onchain ~34
Read environment record from Veya.sol by 16-byte UUID hex
| Name | Type | Req | Description |
|---|---|---|---|
| environmentUuidHex | string | yes | – |
No output schema declared.
No examples provided.
veya_read_memory ~42
Read one memory row owned by this API key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| environmentId | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
veya_register_environment ~125
registerEnvironment on Veya.sol from YOUR wallet. Pass product environmentId to confirm the tx on the product API.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Required for on-chain writes. |
| envType | integer | – | – |
| environmentId | string | – | – |
| environmentUuidHex | string | – | – |
| payerPrivateKey | string | – | User wallet private key that pays gas. Prefer VEYA_PAYER_PRIVATE_KEY on a self-hosted MCP. |
| pqPubkeyHashHex | string | – | – |
No output schema declared.
No examples provided.
veya_register_pq_onchain ~96
Generate ML-DSA identity and register environment + commitment on Veya.sol from YOUR wallet
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Required for on-chain writes. |
| envType | integer | – | – |
| payerPrivateKey | string | – | User wallet private key that pays gas. Prefer VEYA_PAYER_PRIVATE_KEY on a self-hosted MCP. |
No output schema declared.
No examples provided.
veya_route_message ~77
Check the saved tool rule for this API key before routing. Deny stays deny.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| environmentId | string | yes | – |
| fromAgent | string | yes | – |
| id | string | yes | – |
| payload | – | – | – |
| toAgent | string | yes | – |
| tool | string | yes | – |
No output schema declared.
No examples provided.
veya_route_secure_message ~113
Check the saved tool rule for this API key, then wrap an allowed message in a Kyber-768 session and an ML-DSA-44 signature.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| environmentId | string | yes | – |
| fromAgent | string | yes | – |
| id | string | yes | – |
| payload | – | – | – |
| senderPrivateKeyHex | string | yes | – |
| senderPublicKeyHex | string | yes | – |
| toAgent | string | yes | – |
| tool | string | yes | – |
No output schema declared.
No examples provided.
veya_run_consensus ~68
Run 2-of-3 BLAKE3 consensus on this server's validator list. Needs a product API key. Returns consensus_reached: false if validators are unreachable.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| payload | object | – | – |
| taskId | string | yes | – |
No output schema declared.
No examples provided.
veya_run_protected_execution ~124
Run protected execution via product API (Build). Product API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| disclose | array | – | – |
| environmentId | string | yes | – |
| eventType | string | yes | – |
| payload | object | yes | – |
| seal | array | – | – |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
No output schema declared.
No examples provided.
veya_seal_decision ~120
Seal an evidence id and a decision. attestExecution is sent only when a payer key is passed, or when this host's seal-decision host-signer switch is on. On Mainnet pass environmentId or set VEYA_SEAL_DECISION_ENVIRONMENT_ID. Without either, the result is SEAL_ENVIRONMENT_REQUIRED and nothing is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| decision | string | yes | – |
| environmentId | string | – | – |
| evidenceId | string | yes | – |
| payerPrivateKey | string | – | – |
No output schema declared.
No examples provided.
veya_sealed_execute ~88
AES-256-GCM protected execution on this server's sealed node. Needs a product API key. The call fails closed when that capacity is unreachable.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| apiKey | string | – | – |
| environmentId | string | yes | – |
| eventType | string | yes | – |
| payload | object | yes | – |
| sessionEntropyHex | string | yes | – |
No output schema declared.
No examples provided.
veya_set_tool_policy ~71
Allow or deny a tool for an agent. Requires the API key that owns the environment. Saved on that account.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| allowed | boolean | yes | – |
| apiKey | string | – | – |
| environmentId | string | yes | – |
| tool | string | yes | – |
No output schema declared.
No examples provided.
veya_store_commitment ~105
Write a 32-byte commitment to Veya.sol from YOUR wallet (apiKey + payerPrivateKey)
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Required for on-chain writes. |
| commitmentHex | string | yes | – |
| environmentUuidHex | string | yes | – |
| payerPrivateKey | string | – | User wallet private key that pays gas. Prefer VEYA_PAYER_PRIVATE_KEY on a self-hosted MCP. |
No output schema declared.
No examples provided.
veya_store_memory ~57
Store agent memory for the account behind this API key. No key, no write.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| apiKey | string | – | – |
| data | string | yes | – |
| environmentId | string | yes | – |
No output schema declared.
No examples provided.
veya_tier ~137
Your $VEYA account tier and the limits it sets on the product API: daily actions, daily receipts, receipt history window and API key rate per minute, plus today's use. The tier comes from the $VEYA held by your sign-in wallet plus up to 3 linked wallets on Robinhood Chain mainnet. Without a key, returns the public tier table.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Product API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential. |
| sessionToken | string | – | Optional guest JWT for Use listing only. Prefer apiKey. |
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.