VEYA MCP Server

by veyanet Your server? Claim it

answering

VEYA is answering right now. Last checked 2 min ago. It exposes 55 tools. Last commit 30 Oct 2026.

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

Uptime history 13 days of history · worst day 99%

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

462 ms

Response time

average over 24h

Stars

last commit 30 Oct 2026

What changed 25

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 October 2026. No other catalogue keeps this.

1 Nov a tool appeared veya_tier

1 Nov a tool changed version

30 Oct 5 tool descriptions were rewritten veya_anchor_proof, veya_paid_call, veya_ping_chain and 2 more

30 Oct a tool changed the parameters it asks for veya_paid_call

25 Oct 3 tool descriptions were rewritten8 times that day veya_paid_call, veya_paid_discover, veya_paid_run

25 Oct 3 tools changed the parameters they ask for5 times that day veya_paid_call, veya_paid_discover, veya_paid_run

25 Oct a tool changed version

24 Oct 3 tools appeared veya_paid_call, veya_paid_discover, veya_paid_run

and 7 more, back to 24 October 2026

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Long encoded blob in source src/brandAssets.ts:6

export const LOGO_PNG = Buffer.from("iVBORw0KGgoAAAANSUhEUgAAAoAAAAFACAYAAAAszc0KAABOeUlEQVR42u3dd4BlWVUu8G+tfc4Nlaurc09ghiHY5CRpiCLJpyhSDQ9UUGRIgkqQoG+qaxiSgMojCBgQQeR1ISiITyUJiAg+JDkDCDMwwMzQsbrijXut98c+595b1T2pZ6anu/r7wZmqvrnuvWefddbee22AiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIi…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add veya --transport http https://mcp.veyanet.tech/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.veyanet.tech/mcp

~/.codex/config.toml

[mcp_servers.veya]
url = "https://mcp.veyanet.tech/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "veya": {
      "url": "https://mcp.veyanet.tech/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "veya": {
      "type": "http",
      "url": "https://mcp.veyanet.tech/mcp"
    }
  }
}

Available tools 55

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

veya

veya_account

Return the wallet bound to a product API key

veya_anchor_pq_attestation

Link PQ identity hash to execution hash on Veya.sol from YOUR wallet

veya_anchor_proof

Anchor a content proof on Veya.sol from YOUR wallet (apiKey + payerPrivateKey). Does not use the hosted signer.

veya_api_health

Check the VEYA API /health status (api.veyanet.tech), including fleet status

veya_attest_execution

attestExecution on Veya.sol from YOUR wallet with ML-DSA bytes

veya_boundnet_invoke

Invoke a Boundnet / coordination tool via product API (policy gated)

veya_client_run_consensus

Deprecated: use veya_run_consensus. Same server validator list. Needs a product API key.

veya_commitment_exists

eth_call Veya.sol commitments(bytes32) for a digest

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 e2e are refused. Use a real workspace name of at least 6 characters, or a name that starts with VEYA.

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 coordination when omitted.

veya_describe

Service info: AES-256-GCM sealed execution and the selected settlement profile

veya_get_environment

Get one environment by id

veya_guest_login

Create a guest session on the product API (Use listing only). Guest cannot mint API keys or write from MCP.

veya_hash_blake3

Compute BLAKE3 hex digest (commitment helper)

veya_invalidate_memory

Nullify one memory row owned by this API key.

veya_list_agents

List agents in an environment

veya_list_api_memory

List memory entries via product API for an environment

veya_list_environments

List environments for a product API key (guest JWT sees showcase / Use scope only)

veya_list_executions

List executions for an environment via product API

veya_list_proofs

List Use-mode proof anchors for the account

veya_paid_call

Run one metered 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_discover

Read-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_run

Read 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_chain

Ping Robinhood Chain RPC — block, contract

veya_pq_fingerprint

BLAKE3 fingerprint of an ML-DSA public key hex

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_prove

Prove text, canonical JSON, or a receipt hash. Anchor writes only when a product API key and a payer key are passed.

veya_public_get_agent

Fetch one public agent by id

veya_public_get_certificate

Fetch one public certificate by id

veya_public_get_execution

Fetch a public execution proof by id

veya_public_list_agents

List public agent registry rows

veya_public_list_certificates

List public certificate / attestation rows

veya_public_stats

Public registry stats from the product API (verified agents / proofs)

veya_read_agent_onchain

Read agent record from Veya.sol by 16-byte UUID hex

veya_read_environment_onchain

Read environment record from Veya.sol by 16-byte UUID hex

veya_read_memory

Read one memory row owned by this API key.

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_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_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_run_protected_execution

Run protected execution via product API (Build). Product API key required.

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 host-signer 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_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.

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_store_commitment

Write a 32-byte commitment to Veya.sol from YOUR wallet (apiKey + payerPrivateKey)

veya_store_memory

Store agent memory for the account behind this API key. No key, no write.

veya_tier

Your $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 wallet plus up to 3 linked wallets on Robinhood Chain mainnet. Without a key, returns the public tier table.

veya_verify_commitment_onchain

Parse Veya.sol events from a tx and eth_call commitments(digest) for each CommitmentStored

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_verify_secure_message

Verify ML-DSA signature on a secure routed message envelope

veya_verify_transaction

Verify a Veya.sol commitment from a Robinhood Chain tx hash

veya_writes_status

Reports how on-chain writes work on this server: your own wallet sends them, the host signer does not

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.veyanet.tech/mcp	streamable-http	answering	421 ms	2 min ago

Alternatives to VEYA

same job, measured the same way

Dokimo MCP

by ypratap11

Verify AI-agent revenue: recompute a Merkle proof and check it against an on-chain anchor.

3 tools answering

AgentaOS

by agentaos

Merchant of record: payment links, checkouts, subscriptions and invoices, with VAT handled.

answering

three.ws Provenance

by nirholas

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

79 installs/wk local only

Fabric Verify

by augmentev

Signed, publicly logged records of what your AI agent did, with proofs anyone can check offline.

411 installs/wk answering

AI Proof of Us

by 0xddneto

Private signed AI task receipts with replay checks and optional validated AIPOU claims.

114 installs/wk local only

Purser

by ahmad-codex

Wallet for AI agents with on-chain spending limits and owner approval over the limit

local only

Vulnify

by vulnify

Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.

132 installs/wk answering

Limitguard Lead Verification

by limitguard-api

Lead validation over MCP: KVK/KBO register, EU VAT, sanctions and email checks with sources.

10 tools answering

VEYA — questions

Answers built from our own checks of this server.

What can VEYA do?

It exposes 55 tools, read directly from the server on our last check. Among them: veya_account, veya_anchor_pq_attestation, veya_anchor_proof, veya_api_health, veya_attest_execution, veya_boundnet_invoke and 49 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is VEYA working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 462 ms. The bar chart above shows every period we have measured.

How do I connect VEYA?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does VEYA need an API key?

No. VEYA completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 55 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is VEYA?

It answers our handshake in 462 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is VEYA open source?

The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.veyanet.tech, which runs on its operator's own terms.