List your agent

VEYA

MCP server · hosted · v1.2.8 · io.github.veyanet/veya
Online · tested 2h agoNEW · 3h agoSeen in the registry 2h ago

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

Website ↗Source code ↗How to connect ↓

What it does

VEYA is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence) and are not a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.2.8
PriceNot in the registry
First seen21 Oct 2026
Last checked2h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)

Hosted endpoint

  • https://mcp.veyanet.tech/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "veya": {
      "url": "https://mcp.veyanet.tech/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE VEYA answered an MCP connection on 21 Oct 2026 and introduced itself as @veyanet/mcp 1.2.8 (MCP protocol 2025-06-18).

51 tools offered to AI assistants

  • veya_describe · Service info: AES-256-GCM sealed execution and the selected settlement profile
  • veya_ping_chain · Ping Robinhood Chain RPC — chain id, block, contract
  • veya_hash_blake3 · Compute BLAKE3 hex digest (commitment helper)
  • veya_verify_transaction · Verify a Veya.sol commitment from a Robinhood Chain tx hash
  • veya_api_health · Check the VEYA API /health status (api.veyanet.tech), including fleet status
  • veya_prove · Prove text, canonical JSON, or a receipt hash. Anchor writes only when a product API key and a payer key are passed.
  • veya_seal_decision · 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
  • veya_pq_keygen · Generate an ML-DSA-44 post-quantum identity keypair (local, no chain write)
  • veya_pq_sign · Sign UTF-8 text with ML-DSA-44
  • veya_pq_verify · Verify an ML-DSA-44 signature over UTF-8 text
  • veya_run_consensus · 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_execute · 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.
Show 39 more
  • veya_set_tool_policy · Allow or deny a tool for an agent. Requires the API key that owns the environment. Saved on that account.
  • veya_route_message · Check the saved tool rule for this API key before routing. Deny stays deny.
  • veya_route_secure_message · 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_message · Verify ML-DSA signature on a secure routed message envelope
  • veya_store_memory · Store agent memory for the account behind this API key. No key, no write.
  • veya_read_memory · Read one memory row owned by this API key.
  • veya_invalidate_memory · Nullify one memory row owned by this API key.
  • veya_client_run_consensus · Deprecated: use veya_run_consensus. Same server validator list. Needs a product API key.
  • veya_pq_fingerprint · BLAKE3 fingerprint of an ML-DSA public key hex
  • veya_public_stats · Public registry stats from the product API (verified agents / proofs)
  • veya_public_list_agents · List public agent registry rows
  • veya_public_get_agent · Fetch one public agent by id
  • veya_public_list_certificates · List public certificate / attestation rows
  • veya_public_get_certificate · Fetch one public certificate by id
  • veya_public_get_execution · Fetch a public execution proof by id
  • veya_verify_commitment_onchain · Parse Veya.sol events from a tx and eth_call commitments(digest) for each CommitmentStored
  • veya_commitment_exists · eth_call Veya.sol commitments(bytes32) for a digest
  • veya_read_environment_onchain · Read environment record from Veya.sol by 16-byte UUID hex
  • veya_read_agent_onchain · Read agent record from Veya.sol by 16-byte UUID hex
  • veya_guest_login · Create a guest session on the product API (Use listing only). Guest cannot mint API keys or write from MCP.
  • veya_account · Return the wallet bound to a product API key
  • veya_list_environments · List environments for a product API key (guest JWT sees showcase / Use scope only)
  • veya_get_environment · Get one environment by id
  • veya_create_environment · 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 e
  • veya_list_agents · List agents in an environment
  • veya_deploy_agent · 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 coord
  • veya_list_api_memory · List memory entries via product API for an environment
  • veya_list_executions · List executions for an environment via product API
  • veya_run_protected_execution · Run protected execution via product API (Build). Product API key required.
  • veya_boundnet_invoke · Invoke a Boundnet / coordination tool via product API (policy gated)
  • veya_list_proofs · List Use-mode proof anchors for the account
  • veya_anchor_proof · Anchor a content proof on Veya.sol from YOUR wallet (apiKey + payerPrivateKey). Does not use the hosted relayer.
  • veya_verify_proof_api · Check a commitment or anchor transaction through the product API. A registration transaction is not a proof and returns NOT_VEYA_TX.
  • veya_writes_status · Reports how on-chain writes work on this server: your own wallet sends them, the host relayer does not
  • veya_store_commitment · Write a 32-byte commitment to Veya.sol from YOUR wallet (apiKey + payerPrivateKey)
  • veya_attest_execution · attestExecution on Veya.sol from YOUR wallet with ML-DSA bytes
  • veya_register_environment · registerEnvironment on Veya.sol from YOUR wallet. Pass product environmentId to confirm the tx on the product API.
  • veya_register_pq_onchain · Generate ML-DSA identity and register environment + commitment on Veya.sol from YOUR wallet
  • veya_anchor_pq_attestation · Link PQ identity hash to execution hash on Veya.sol from YOUR wallet

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.veyanet.tech/mcpDECLAREDSRC-001 Official MCP Registry2h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry2h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2h ago
Websitehttps://veyanet.tech/docsDECLAREDSRC-001 Official MCP Registry2h ago
Repositoryhttps://github.com/veyanet/veya-mcpDECLAREDSRC-001 Official MCP Registry2h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2h ago
Version1.2.8DECLAREDSRC-001 Official MCP Registry2h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2h ago

Change history

  • NEW21 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Questions about VEYA

How do I connect VEYA?

Use the hosted endpoint https://mcp.veyanet.tech/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does VEYA need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does VEYA offer?

When Electra Index connected on 21 Oct 2026, it listed 51 tools: veya_describe, veya_ping_chain, veya_hash_blake3, veya_verify_transaction, veya_api_health, veya_prove, veya_seal_decision, veya_pq_keygen and more. The full list is in "Live check" above.

Is VEYA online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.