VEYA
Check, limit, record and prove AI agent actions with 2-of-3 validators and onchain proofs.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://mcp.veyanet.tech/mcp | registry |
|---|---|---|
| Handshake | Answers the MCP handshake and lists its tools (503 ms) | our check, 2026-10-26 |
| Protocol version | 2025-11-25 | our check, 2026-10-26 |
| Tools (54) | veya_describe, veya_ping_chain, veya_hash_blake3, veya_verify_transaction, veya_api_health, veya_prove, veya_seal_decision, veya_pq_keygen, veya_pq_sign, veya_pq_verify, veya_run_consensus, veya_sealed_execute, veya_set_tool_policy, veya_route_message, veya_route_secure_message, veya_verify_secure_message, veya_store_memory, veya_read_memory, veya_invalidate_memory, veya_client_run_consensus, veya_pq_fingerprint, veya_public_stats, veya_public_list_agents, veya_public_get_agent, veya_public_list_certificates, veya_public_get_certificate, veya_public_get_execution, veya_verify_commitment_onchain, veya_commitment_exists, veya_read_environment_onchain, veya_read_agent_onchain, veya_guest_login, veya_account, veya_list_environments, veya_get_environment, veya_create_environment, veya_list_agents, veya_deploy_agent, veya_list_api_memory, veya_list_executions, veya_run_protected_execution, veya_boundnet_invoke, veya_list_proofs, veya_anchor_proof, veya_verify_proof_api, veya_writes_status, veya_store_commitment, veya_attest_execution, veya_register_environment, veya_register_pq_onchain, veya_anchor_pq_attestation, veya_paid_discover, veya_paid_call, veya_paid_run | tools/list, 2026-10-26 |
| GitHub stars | 0 | github.com/veyanet/veya-mcp |
| Last push | 2026-10-25 | GitHub API |
| Licence | MIT | GitHub API |
| Registry version | 1.2.8 · active · updated 2026-10-21 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http veya https://mcp.veyanet.tech/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- site Conveyancing Fees Australia: the site's own MCP server — enquiry (enquiry = a human…
- site Conveyancing Fees Ireland: the site's own MCP server — enquiry (enquiry = a human handoff…
- Quinn's Conveyance — Paid ComfyUI Knowledge MCP Paid ComfyUI knowledge tools. 5 tools $0.005 USDC/call on Base via x402; ping, list_topics…
- site Conveyancing Fees NZ: the site's own MCP server — enquiry (enquiry = a human handoff, not…
- site Compare My Conveyancing: the site's own MCP server — compare, enquiry (enquiry = a…
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/io.github.veyanet/veya)<a href="https://openforallofus.com/tools/io.github.veyanet/veya"><img src="https://openforallofus.com/badge/io.github.veyanet/veya.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.veyanet/veya.