
VEYA MCP server
online · 100% uptimeio.github.veyanet/veya·v1.2.8Check, limit, record and prove AI agent actions with 2-of-3 validators and onchain proofs.
0 stars
Reviews
Write oneNobody has reviewed VEYA yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
VEYA tools (54, 10 write)
write = sends, deletes, buys or postsveya_accountFreeReturn the wallet bound to a product API key
veya_anchor_pq_attestationFreeLink PQ identity hash to execution hash on Veya.sol from YOUR wallet
veya_anchor_proofFreeAnchor a content proof on Veya.sol from YOUR wallet (apiKey + payerPrivateKey). Does not use the hosted relayer.
veya_api_healthFreeCheck the VEYA API /health status (api.veyanet.tech), including fleet status
veya_attest_executionFreeattestExecution on Veya.sol from YOUR wallet with ML-DSA bytes
veya_boundnet_invokeFreeInvoke a Boundnet / coordination tool via product API (policy gated)
veya_client_run_consensuswrite actionFreeDeprecated: use veya_run_consensus. Same server validator list. Needs a product API key.
veya_commitment_existsFreeeth_call Veya.sol commitments(bytes32) for a digest
veya_create_environmentwrite actionFreeCreate 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.
veya_deploy_agentwrite actionFreeCreate 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.
veya_describeFreeService info: AES-256-GCM sealed execution and the selected settlement profile
veya_get_environmentFreeGet one environment by id
veya_guest_loginwrite actionFreeCreate a guest session on the product API (Use listing only). Guest cannot mint API keys or write from MCP.
veya_hash_blake3FreeCompute BLAKE3 hex digest (commitment helper)
veya_invalidate_memoryFreeNullify one memory row owned by this API key.
veya_list_agentsFreeList agents in an environment
veya_list_api_memoryFreeList memory entries via product API for an environment
veya_list_environmentsFreeList environments for a product API key (guest JWT sees showcase / Use scope only)
veya_list_executionsFreeList executions for an environment via product API
veya_list_proofsFreeList Use-mode proof anchors for the account
veya_paid_callwrite actionFreeRun one paid 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.
veya_paid_discoverFreeRead-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.
veya_paid_runwrite actionFreeRead 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.
veya_ping_chainFreePing Robinhood Chain RPC — chain id, block, contract
veya_pq_fingerprintFreeBLAKE3 fingerprint of an ML-DSA public key hex
veya_pq_keygenFreeGenerate an ML-DSA-44 post-quantum identity keypair (local, no chain write)
veya_pq_signFreeSign UTF-8 text with ML-DSA-44
veya_pq_verifyFreeVerify an ML-DSA-44 signature over UTF-8 text
veya_proveFreeProve text, canonical JSON, or a receipt hash. Anchor writes only when a product API key and a payer key are passed.
veya_public_get_agentFreeFetch one public agent by id
veya_public_get_certificateFreeFetch one public certificate by id
veya_public_get_executionFreeFetch a public execution proof by id
veya_public_list_agentsFreeList public agent registry rows
veya_public_list_certificatesFreeList public certificate / attestation rows
veya_public_statsFreePublic registry stats from the product API (verified agents / proofs)
veya_read_agent_onchainFreeRead agent record from Veya.sol by 16-byte UUID hex
veya_read_environment_onchainFreeRead environment record from Veya.sol by 16-byte UUID hex
veya_read_memoryFreeRead one memory row owned by this API key.
veya_register_environmentFreeregisterEnvironment on Veya.sol from YOUR wallet. Pass product environmentId to confirm the tx on the product API.
veya_register_pq_onchainFreeGenerate ML-DSA identity and register environment + commitment on Veya.sol from YOUR wallet
veya_route_messageFreeCheck the saved tool rule for this API key before routing. Deny stays deny.
veya_route_secure_messageFreeCheck the saved tool rule for this API key, then wrap an allowed message in a Kyber-768 session and an ML-DSA-44 signature.
veya_run_consensuswrite actionFreeRun 2-of-3 BLAKE3 consensus on this server's validator list. Needs a product API key. Returns consensus_reached: false if validators are unreachable.
veya_run_protected_executionwrite actionFreeRun protected execution via product API (Build). Product API key required.
veya_seal_decisionFreeSeal an evidence id and a decision. attestExecution is sent only when a payer key is passed, or when this host's seal-decision relayer 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.
veya_sealed_executewrite actionFreeAES-256-GCM protected execution on this server's sealed node. Needs a product API key. The call fails closed when that capacity is unreachable.
veya_set_tool_policyFreeAllow or deny a tool for an agent. Requires the API key that owns the environment. Saved on that account.
veya_store_commitmentwrite actionFreeWrite a 32-byte commitment to Veya.sol from YOUR wallet (apiKey + payerPrivateKey)
veya_store_memoryFreeStore agent memory for the account behind this API key. No key, no write.
veya_verify_commitment_onchainFreeParse Veya.sol events from a tx and eth_call commitments(digest) for each CommitmentStored
veya_verify_proof_apiFreeCheck a commitment or anchor transaction through the product API. A registration transaction is not a proof and returns NOT_VEYA_TX.
veya_verify_secure_messageFreeVerify ML-DSA signature on a secure routed message envelope
veya_verify_transactionFreeVerify a Veya.sol commitment from a Robinhood Chain tx hash
veya_writes_statusFreeReports how on-chain writes work on this server: your own wallet sends them, the host relayer does not
Public scan report
scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1278ms20/20
- Tool poisoning54 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How VEYA compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 80% of 4,460 AI and agents servers
- Tools
- 54
- the typical AI and agents server has 6
- Tools that change things
- 19%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote AI and agents server answers 100%
- Response time
- 766 ms
- faster than 15% of 2,331 AI and agents servers
What its tools let an agent do: 44 read · 10 change
Install VEYA in Claude Code, Cursor or VS Code
claude mcp add --transport http veya https://mcp.veyanet.tech/mcp
What the publisher says
From the VEYA repository's README, as published. We do not edit it. Read it on GitHub
# VEYA MCP
The official Model Context Protocol server for post-quantum agent tools, chain verification, sealed-execution service info, and protocol settlement on Robinhood Chain.
Official Website • X (Twitter) • Public MCP URL • Documentation Index • Network Specifications • Security Policy
💡 Information: What is VEYA?
The VEYA Protocol is a decentralized, cryptographically shielded execution layer engineered for post-quantum resilient autonomous agent fleets on Robinhood Chain. Traditional LLM agent frameworks suffer from severe structural vulnerabilities: because agents require private execution contexts—such as API integration credentials, proprietary system prompts, treasury authority, and policy rules—running them in standard host runtimes exposes sensitive state in plaintext to host operators, database administrators, and network intermediaries.
VEYA solves this security gap by establishing client-side cryptographic boundaries and post-quantum attestation primitives. Sensitive agent workloads are protected through local post-quantum key generation (ML-DSA-44), quantum-resistant session negotiation (Kyber-768), high-throughput cryptographic digests (BLAKE3-256), sealed execution with AES-256-GCM, and 2-of-3 multi-node consensus. This tree defaults to Mainnet. Veya.sol there is the protocol contract 0x87dC582eEA544A434a5C1e30Ca3d12c1e548a674. ROBINHOODNETWORK=testnet keeps Testnet**.
The VEYA MCP Server
The @veyanet/mcp package is the canonical Model Context Protocol surface for VEYA — the full agent-facing tool set. It speaks Streamable HTTP so Claude, Cursor, and other MCP clients can paste a single URL and invoke crypto, fleet, registry, product API, and own-wallet on-chain write tools without cloning @veyanet/sdk. Cryptography, chain-id guards, and receipt parsing are delegated to @veyanet/sdk; this package owns the HTTP transport, tool registration, product apiKey forwarding, and the public service info.
By connecting an MCP client to @veyanet/mcp, you enable the following core capabilities:
- Paste-URL Access: Connect via https://mcp.veyanet.tech/mcp (Streamable HTTP).
- Public Tools: Describe the stack, ping Robinhood Chain, BLAKE3, verify Veya.sol txs, PQ crypto, registry, product sessions via https://api.veyanet.tech.
- Own-wallet writes: On-chain tools need a product API key (veyadev / veyalive) and your funded wallet. The hosted relayer is not the gas payer.
- SDK-Backed Settlement: Chain calls use @veyanet/sdk. The default profile is Mainnet. Testnet is ROBINHOOD_NETWORK=testnet.
- Backend-owned fleet: Consensus validators and sealed capacity belong to the product API (https://api.veyanet.tech).
📖 Table of Contents
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
VEYA: common questions
- Is VEYA MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the VEYA safety report
- How do I install VEYA?
- It runs remotely at mcp.veyanet.tech. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does VEYA need an API key?
- Yes. The registry entry asks for
Authorization. - Is VEYA maintained?
- The last commit was 10 days ago (2026-10-25). The latest release is v1.2.8.
- Is VEYA up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of VEYA?
- Servers from other publishers that do the same job: three.ws Provenance MCP server, Decionis MCP server and Agent-Native Chat MCP server.
- How does VEYA compare with other AI and agents MCP servers?
- safety score 88/100 (higher than 80% of 4,460 AI and agents servers); tools 54 (the typical AI and agents server has 6); tools that change things 19% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to VEYA
Same job from other publishers: the closest match first, then the best rated.
- three.ws ProvenanceAppend-only, signed, on-chain-verifiable agent action log — record and audit what agents did.not reviewedEstablishedB
- DecionisAuthorize consequential AI agent actions before executionnot reviewedEstablishedA
- Agent-Native ChatMinimal chat-first app with durable threads, actions, and the app-agent loopnot reviewedEstablishedA
- Emilia ProtocolExact-action approval for consequential agent actions: request, track, and verify signed receipts.not reviewedEstablishedB
- MockserverMock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.not reviewedEstablishedA