Agents Index

VEYA

OnlineNew

Check, limit, record and prove AI agent actions with 2-of-3 validators and onchain proofs.

Visit publisherConnectJSON

What it can do: 55 tools

  • veya_describeService info: AES-256-GCM sealed execution and the selected settlement profile
  • veya_ping_chainPing Robinhood Chain RPC — block, contract
  • veya_hash_blake3Compute BLAKE3 hex digest (commitment helper)
  • veya_verify_transactionVerify a Veya.sol commitment from a Robinhood Chain tx hash
  • veya_api_healthCheck the VEYA API /health status (api.veyanet.tech), including fleet status
  • veya_proveProve text, canonical JSON, or a receipt hash. Anchor writes only when a product API key and a payer key are passed.
  • veya_seal_decisionSeal 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
  • veya_pq_keygenGenerate an ML-DSA-44 post-quantum identity keypair (local, no chain write)
  • veya_pq_signSign UTF-8 text with ML-DSA-44
  • veya_pq_verifyVerify an ML-DSA-44 signature over UTF-8 text
  • veya_run_consensusRun 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_executeAES-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_policyAllow or deny a tool for an agent. Requires the API key that owns the environment. Saved on that account.
  • veya_route_messageCheck the saved tool rule for this API key before routing. Deny stays deny.
  • veya_route_secure_messageCheck 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_messageVerify ML-DSA signature on a secure routed message envelope
  • veya_store_memoryStore agent memory for the account behind this API key. No key, no write.
  • veya_read_memoryRead one memory row owned by this API key.
  • veya_invalidate_memoryNullify one memory row owned by this API key.
  • veya_client_run_consensusDeprecated: use veya_run_consensus. Same server validator list. Needs a product API key.
  • veya_pq_fingerprintBLAKE3 fingerprint of an ML-DSA public key hex
  • veya_public_statsPublic registry stats from the product API (verified agents / proofs)
  • veya_public_list_agentsList public agent registry rows
  • veya_public_get_agentFetch one public agent by id
  • veya_public_list_certificatesList public certificate / attestation rows
  • veya_public_get_certificateFetch one public certificate by id
  • veya_public_get_executionFetch a public execution proof by id
  • veya_verify_commitment_onchainParse Veya.sol events from a tx and eth_call commitments(digest) for each CommitmentStored
  • veya_commitment_existseth_call Veya.sol commitments(bytes32) for a digest
  • veya_read_environment_onchainRead environment record from Veya.sol by 16-byte UUID hex
  • veya_read_agent_onchainRead agent record from Veya.sol by 16-byte UUID hex
  • veya_guest_loginCreate a guest session on the product API (Use listing only). Guest cannot mint API keys or write from MCP.
  • veya_accountReturn the wallet bound to a product API key
  • veya_tierYour $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 w
  • veya_list_environmentsList environments for a product API key (guest JWT sees showcase / Use scope only)
  • veya_get_environmentGet one environment by id
  • veya_create_environmentCreate 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
  • veya_list_agentsList agents in an environment
  • veya_deploy_agentCreate 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 a
  • veya_list_api_memoryList memory entries via product API for an environment

…and 15 more.

Connect it

Claude Code
claude mcp add --transport http veya https://mcp.veyanet.tech/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.veyanet.tech/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "veya": {
      "url": "https://mcp.veyanet.tech/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "veya": {
      "type": "http",
      "url": "https://mcp.veyanet.tech/mcp"
    }
  }
}

Questions

What does VEYA do?

Check, limit, record and prove AI agent actions with 2-of-3 validators and onchain proofs. It exposes 55 tools to AI assistants.

What tools does VEYA provide?

55 tools, including 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….

How do I connect VEYA to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.veyanet.tech/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does VEYA require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is VEYA online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes VEYA?

@veyanet on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Crypto & Web3