VEYA MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address | 0.0.0.0 |
| PORT | No | Listen port | 8788 |
| NODE_ENV | No | Runtime mode | development |
| CORS_ORIGIN | No | Comma-separated Origin allowlist | empty = reject credentialed browser Origin |
| MCP_API_KEY | No | Operator relayer path only | unset on the public host |
| VEYA_API_URL | No | Product API (health, registry, sessions, fleet capacity) | https://api.veyanet.tech |
| PUBLIC_MCP_URL | No | Public paste URL advertised in landing + health | https://mcp.veyanet.tech/mcp |
| ROBINHOOD_RPC_URL | No | Network JSON-RPC endpoint | Public testnet RPC |
| ROBINHOOD_CHAIN_ID | No | Network chain ID | 46630 |
| VEYA_SEALED_NODE_URL | No | Sealed capacity URL (backend-owned) | configured per host |
| VEYA_VALIDATOR_NODES | No | Backend fleet URLs (server-side; not stranger loopback) | configured per host |
| VEYA_CONTRACT_ADDRESS | No | Veya.sol protocol contract | Testnet deploy address |
| ROBINHOOD_EXPLORER_URL | No | Block explorer base URL | Public testnet explorer |
| VEYA_PAYER_PRIVATE_KEY | No | Self-hosted payer for product write tools. veya_prove does not read this. Pass payerPrivateKey on an anchor call. | |
| VEYA_RELAYER_PRIVATE_KEY | No | Unused by veya_prove | unset on the public host |
| VEYA_DEPLOYER_PRIVATE_KEY | No | SDK payer when VeyaClient is constructed without payerPrivateKey | unset on the public host |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| veya_describeC | Service info: AES-256-GCM sealed execution and the selected settlement profile |
| veya_ping_chainB | Ping Robinhood Chain RPC — chain id, block, contract |
| veya_hash_blake3C | Compute BLAKE3 hex digest (commitment helper) |
| veya_verify_transactionC | Verify a Veya.sol commitment from a Robinhood Chain tx hash |
| veya_api_healthA | Check the VEYA API /health status (api.veyanet.tech), including fleet status |
| veya_proveB | Prove text, canonical JSON, or a receipt hash. Anchor writes only when a product API key and a payer key are passed. |
| veya_seal_decisionA | Seal 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_pq_keygenA | Generate an ML-DSA-44 post-quantum identity keypair (local, no chain write) |
| veya_pq_signC | Sign UTF-8 text with ML-DSA-44 |
| veya_pq_verifyC | Verify an ML-DSA-44 signature over UTF-8 text |
| veya_run_consensusC | 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. |
| veya_sealed_executeC | 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. |
| veya_set_tool_policyA | Allow or deny a tool for an agent. Requires the API key that owns the environment. Saved on that account. |
| veya_route_messageD | Check the saved tool rule for this API key before routing. Deny stays deny. |
| veya_route_secure_messageC | 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. |
| veya_verify_secure_messageC | Verify ML-DSA signature on a secure routed message envelope |
| veya_store_memoryB | Store agent memory for the account behind this API key. No key, no write. |
| veya_read_memoryC | Read one memory row owned by this API key. |
| veya_invalidate_memoryC | Nullify one memory row owned by this API key. |
| veya_client_run_consensusB | Deprecated: use veya_run_consensus. Same server validator list. Needs a product API key. |
| veya_pq_fingerprintC | BLAKE3 fingerprint of an ML-DSA public key hex |
| veya_public_statsC | Public registry stats from the product API (verified agents / proofs) |
| veya_public_list_agentsC | List public agent registry rows |
| veya_public_get_agentB | Fetch one public agent by id |
| veya_public_list_certificatesC | List public certificate / attestation rows |
| veya_public_get_certificateC | Fetch one public certificate by id |
| veya_public_get_executionC | Fetch a public execution proof by id |
| veya_verify_commitment_onchainC | Parse Veya.sol events from a tx and eth_call commitments(digest) for each CommitmentStored |
| veya_commitment_existsC | eth_call Veya.sol commitments(bytes32) for a digest |
| veya_read_environment_onchainB | Read environment record from Veya.sol by 16-byte UUID hex |
| veya_read_agent_onchainB | Read agent record from Veya.sol by 16-byte UUID hex |
| veya_guest_loginA | Create a guest session on the product API (Use listing only). Guest cannot mint API keys or write from MCP. |
| veya_accountB | Return the wallet bound to a product API key |
| veya_list_environmentsB | List environments for a product API key (guest JWT sees showcase / Use scope only) |
| veya_get_environmentC | Get one environment by id |
| veya_create_environmentA | 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. |
| veya_list_agentsC | List agents in an environment |
| veya_deploy_agentB | 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. |
| veya_list_api_memoryC | List memory entries via product API for an environment |
| veya_list_executionsB | List executions for an environment via product API |
| veya_run_protected_executionC | Run protected execution via product API (Build). Product API key required. |
| veya_boundnet_invokeC | Invoke a Boundnet / coordination tool via product API (policy gated) |
| veya_list_proofsC | List Use-mode proof anchors for the account |
| veya_anchor_proofA | Anchor a content proof on Veya.sol from YOUR wallet (apiKey + payerPrivateKey). Does not use the hosted relayer. |
| veya_verify_proof_apiB | Check a commitment or anchor transaction through the product API. A registration transaction is not a proof and returns NOT_VEYA_TX. |
| veya_writes_statusB | Reports how on-chain writes work on this server: your own wallet sends them, the host relayer does not |
| veya_store_commitmentB | Write a 32-byte commitment to Veya.sol from YOUR wallet (apiKey + payerPrivateKey) |
| veya_attest_executionC | attestExecution on Veya.sol from YOUR wallet with ML-DSA bytes |
| veya_register_environmentC | registerEnvironment on Veya.sol from YOUR wallet. Pass product environmentId to confirm the tx on the product API. |
| veya_register_pq_onchainC | Generate ML-DSA identity and register environment + commitment on Veya.sol from YOUR wallet |
| veya_anchor_pq_attestationC | Link PQ identity hash to execution hash on Veya.sol from YOUR wallet |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 51 tools
Many tools are clearly distinct, but several clusters overlap heavily: four verification tools (verify_transaction, verify_commitment_onchain, commitment_exists, verify_proof_api), multiple proof/commitment writers (prove, anchor_proof, store_commitment, attest_execution), and duplicate consensus tools. Descriptions clarify contexts like public API, on-chain, and wallet-signed, but misselection risk remains.
All 51 tools use the veya_ prefix and snake_case, with predictable verb_noun patterns such as list/get/create/register/verify. Even the deprecated client_run_consensus follows the same convention, so naming is highly consistent.
51 tools far exceeds the 3-15 sweet spot and the 25+ 'too many' threshold. Deprecated, redundant, and niche operations inflate the surface, making this an extreme tool count for an MCP server even given the broad protocol scope.
The surface covers public registry, on-chain reads/writes, PQ crypto, environments, agents, memory, proofs, and policy routing. Some lifecycle gaps exist (no update/delete for agents or environments, no memory update, limited API key management), but most workflows have a path.