Skip to content

VEYA MCP server

io.github.veyanet/veyaveyanetstreamable-httpv1.2.8Scanned

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

55 tools: 37 change things and 18 only read.

Tools: 0 delete, 0 irreversible, 37 write, 18 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 13 findings

Tools listed without sign-in. Remote posture

With Anlyon

37 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the VEYA MCP server can do

The VEYA MCP server is published by the GitHub account veyanet. It has 55 tools. It can create or change data (37 tools: veya_hash_blake3, veya_verify_transaction, veya_api_health, veya_prove and 33 more), but cannot delete data. 18 tools only read.

1 tool can send data out of your system (veya_paid_call).

The fixed checks matched 13 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.2.8.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

55 tools

Changes things 37Claude Code: ask
  • veya_anchor_pq_attestationLink PQ identity hash to execution hash on Veya.sol from YOUR walletNo findings

    Why it is in this group

    • The description's first verb is "link": a word for a change.
    Description, as the server wrote it
    Link PQ identity hash to execution hash on Veya.sol from YOUR wallet
  • veya_anchor_proofAnchor a content proof on Veya.sol from YOUR wallet (apiKey + payerPrivateKey).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    Anchor a content proof on Veya.sol from YOUR wallet (apiKey + payerPrivateKey). Does not use the hosted signer.
  • veya_api_healthCheck the VEYA API /health status (api.veyanet.tech), including fleet statusNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check the VEYA API /health status (api.veyanet.tech), including fleet status
  • veya_attest_executionattestExecution on Veya.sol from YOUR wallet with ML-DSA bytesNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    attestExecution on Veya.sol from YOUR wallet with ML-DSA bytes
  • veya_boundnet_invokeInvoke a Boundnet / coordination tool via product API (policy gated)1 finding

    Why it is in this group

    • The name "veya_boundnet_invoke" says "invoke": a word for a change.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    Invoke a Boundnet / coordination tool via product API (policy gated)
  • veya_client_run_consensusDeprecated: use veya_run_consensus.No findings

    Why it is in this group

    • The name "veya_client_run_consensus" says "run": a word for a change.
    Description, as the server wrote it
    Deprecated: use veya_run_consensus. Same server validator list. Needs a product API key.
  • veya_commitment_existseth_call Veya.sol commitments(bytes32) for a digestNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    eth_call Veya.sol commitments(bytes32) for a digest
  • veya_create_environmentCreate a workspace in the product API.1 finding

    Why it is in this group

    • The name "veya_create_environment" says "create": a word for a change.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    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_agentCreate an agent in a workspace.1 finding

    Why it is in this group

    • The name "veya_deploy_agent" says "deploy": a word for a change.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    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_guest_loginCreate a guest session on the product API (Use listing only).No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    Description, as the server wrote it
    Create a guest session on the product API (Use listing only). Guest cannot mint API keys or write from MCP.
  • veya_hash_blake3Compute BLAKE3 hex digest (commitment helper)No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Compute BLAKE3 hex digest (commitment helper)
  • veya_invalidate_memoryNullify one memory row owned by this API key.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Nullify one memory row owned by this API key.
  • veya_paid_callRun one metered x402 resource call through the VEYA policy gate.Can send data outNo findings

    Why it is in this group

    • The name "veya_paid_call" says "call": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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_runRead your VEYA runs.No findings

    Why it is in this group

    • The name "veya_paid_run" says "run": a word for a change.
    Description, as the server wrote it
    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_pq_fingerprintBLAKE3 fingerprint of an ML-DSA public key hexNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    BLAKE3 fingerprint of an ML-DSA public key hex
  • veya_pq_keygenGenerate an ML-DSA-44 post-quantum identity keypair (local, no chain write)No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    Generate an ML-DSA-44 post-quantum identity keypair (local, no chain write)
  • veya_pq_signSign UTF-8 text with ML-DSA-44No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Sign UTF-8 text with ML-DSA-44
  • veya_pq_verifyVerify an ML-DSA-44 signature over UTF-8 textNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify an ML-DSA-44 signature over UTF-8 text
  • veya_proveProve text, canonical JSON, or a receipt hash.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Prove text, canonical JSON, or a receipt hash. Anchor writes only when a product API key and a payer key are passed.
  • veya_public_statsPublic registry stats from the product API (verified agents / proofs)No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Public registry stats from the product API (verified agents / proofs)
  • veya_register_environmentregisterEnvironment on Veya.sol from YOUR wallet.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    registerEnvironment on Veya.sol from YOUR wallet. Pass product environmentId to confirm the tx on the product API.
  • veya_register_pq_onchainGenerate ML-DSA identity and register environment + commitment on Veya.sol from YOUR walletNo findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    Generate ML-DSA identity and register environment + commitment on Veya.sol from YOUR wallet
  • veya_route_messageCheck the saved tool rule for this API key before routing.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_consensusRun 2-of-3 BLAKE3 consensus on this server's validator list.No findings

    Why it is in this group

    • The name "veya_run_consensus" says "run": a word for a change.
    Description, as the server wrote it
    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_executionRun protected execution via product API (Build).1 finding

    Why it is in this group

    • The name "veya_run_protected_execution" says "run": a word for a change.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    Run protected execution via product API (Build). Product API key required.
  • veya_seal_decisionSeal an evidence id and a decision.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_executeAES-256-GCM protected execution on this server's sealed node.No findings

    Why it is in this group

    • The name "veya_sealed_execute" says "execute": a word for a change.
    Description, as the server wrote it
    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_policyAllow or deny a tool for an agent.No findings

    Why it is in this group

    • The name "veya_set_tool_policy" says "set": a word for a change.
    Description, as the server wrote it
    Allow or deny a tool for an agent. Requires the API key that owns the environment. Saved on that account.
  • veya_store_commitmentWrite a 32-byte commitment to Veya.sol from YOUR wallet (apiKey + payerPrivateKey)No findings

    Why it is in this group

    • The name "veya_store_commitment" says "store": a word for a change.
    Description, as the server wrote it
    Write a 32-byte commitment to Veya.sol from YOUR wallet (apiKey + payerPrivateKey)
  • veya_store_memoryStore agent memory for the account behind this API key.No findings

    Why it is in this group

    • The name "veya_store_memory" says "store": a word for a change.
    Description, as the server wrote it
    Store agent memory for the account behind this API key. No key, no write.
  • 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.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    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_onchainParse Veya.sol events from a tx and eth_call commitments(digest) for each CommitmentStoredNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Parse Veya.sol events from a tx and eth_call commitments(digest) for each CommitmentStored
  • veya_verify_proof_apiCheck a commitment or anchor transaction through the product API.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_messageVerify ML-DSA signature on a secure routed message envelopeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify ML-DSA signature on a secure routed message envelope
  • veya_verify_transactionVerify a Veya.sol commitment from a Robinhood Chain tx hashNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a Veya.sol commitment from a Robinhood Chain tx hash
  • veya_writes_statusReports how on-chain writes work on this server: your own wallet sends them, the host signer does notNo findings

    Why it is in this group

    • The name "veya_writes_status" says "write": a word for a change.
    Description, as the server wrote it
    Reports how on-chain writes work on this server: your own wallet sends them, the host signer does not
Only reads 18Show 18 read-only tools
  • veya_accountReturn the wallet bound to a product API key1 finding

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    Return the wallet bound to a product API key
  • veya_describeService info: AES-256-GCM sealed execution and the selected settlement profileNo findings

    Why it is in this group

    • The name "veya_describe" says "describe": a word for reading.
    Description, as the server wrote it
    Service info: AES-256-GCM sealed execution and the selected settlement profile
  • veya_get_environmentGet one environment by id1 finding

    Why it is in this group

    • The name "veya_get_environment" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    Get one environment by id
  • veya_list_agentsList agents in an environment1 finding

    Why it is in this group

    • The name "veya_list_agents" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    List agents in an environment
  • veya_list_api_memoryList memory entries via product API for an environment1 finding

    Why it is in this group

    • The name "veya_list_api_memory" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    List memory entries via product API for an environment
  • veya_list_environmentsList environments for a product API key (guest JWT sees showcase / Use scope only)1 finding

    Why it is in this group

    • The name "veya_list_environments" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    List environments for a product API key (guest JWT sees showcase / Use scope only)
  • veya_list_executionsList executions for an environment via product API1 finding

    Why it is in this group

    • The name "veya_list_executions" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    List executions for an environment via product API
  • veya_list_proofsList Use-mode proof anchors for the account1 finding

    Why it is in this group

    • The name "veya_list_proofs" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.apiKey.description mentions "credential".

      Matched text

      inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

      What this check looks for
    Description, as the server wrote it
    List Use-mode proof anchors for the account
  • veya_paid_discoverRead-only.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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_ping_chainPing Robinhood Chain RPC — block, contractNo findings

    Why it is in this group

    • The name "veya_ping_chain" says "ping": a word for reading.
    Description, as the server wrote it
    Ping Robinhood Chain RPC — block, contract
  • veya_public_get_agentFetch one public agent by idNo findings

    Why it is in this group

    • The name "veya_public_get_agent" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one public agent by id
  • veya_public_get_certificateFetch one public certificate by idNo findings

    Why it is in this group

    • The name "veya_public_get_certificate" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one public certificate by id
  • veya_public_get_executionFetch a public execution proof by idNo findings

    Why it is in this group

    • The name "veya_public_get_execution" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a public execution proof by id
  • veya_public_list_agentsList public agent registry rowsNo findings

    Why it is in this group

    • The name "veya_public_list_agents" says "list": a word for reading.
    Description, as the server wrote it
    List public agent registry rows
  • veya_public_list_certificatesList public certificate / attestation rowsNo findings

    Why it is in this group

    • The name "veya_public_list_certificates" says "list": a word for reading.
    Description, as the server wrote it
    List public certificate / attestation rows
  • veya_read_agent_onchainRead agent record from Veya.sol by 16-byte UUID hexNo findings

    Why it is in this group

    • The name "veya_read_agent_onchain" says "read": a word for reading.
    Description, as the server wrote it
    Read agent record from Veya.sol by 16-byte UUID hex
  • veya_read_environment_onchainRead environment record from Veya.sol by 16-byte UUID hexNo findings

    Why it is in this group

    • The name "veya_read_environment_onchain" says "read": a word for reading.
    Description, as the server wrote it
    Read environment record from Veya.sol by 16-byte UUID hex
  • veya_read_memoryRead one memory row owned by this API key.No findings

    Why it is in this group

    • The name "veya_read_memory" says "read": a word for reading.
    Description, as the server wrote it
    Read one memory row owned by this API key.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
37
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 37 tools that change things (37 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.veyanet.tech/mcp: tools/list returned 55 tools to an anonymous client, including veya_hash_blake3 (write), veya_verify_transaction (write), veya_api_health (write), veya_prove (write), veya_seal_decision (write) and 32 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 36 to 37
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 34 to 36

Findings

Matches of fixed checks, with the text they matched.

13 info
  • The input schema at properties.apiKey.description mentions "credential".

    Matched text

    inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

    What this check looks for
  • The input schema at properties.apiKey.description mentions "credential".

    Matched text

    inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

    What this check looks for
  • The input schema at properties.apiKey.description mentions "credential".

    Matched text

    inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

    What this check looks for
  • The input schema at properties.apiKey.description mentions "credential".

    Matched text

    inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

    What this check looks for
  • The input schema at properties.apiKey.description mentions "credential".

    Matched text

    inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

    What this check looks for
  • The input schema at properties.apiKey.description mentions "credential".

    Matched text

    inputSchema.properties.apiKey.description: "...product site. Guest JWT is not a write credential."

    What this check looks for
Show 7 more findings

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 added, 4 changed.+4 added~4 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 36 -> 37.View diff
    • Tools that change things, listed without credentials: 36 to 37
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 34 -> 36.View diff
    • Tools that change things, listed without credentials: 34 to 36

Install

Pinned to version 1.2.8. Values in angle brackets are yours to fill in.

claude mcp add --transport http veya https://mcp.veyanet.tech/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http veya https://mcp.veyanet.tech/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__veya__veya_describe",
      "mcp__veya__veya_ping_chain",
      "mcp__veya__veya_read_memory",
      "mcp__veya__veya_public_list_agents",
      "mcp__veya__veya_public_get_agent",
      "mcp__veya__veya_public_list_certificates",
      "mcp__veya__veya_public_get_certificate",
      "mcp__veya__veya_public_get_execution",
      "mcp__veya__veya_read_environment_onchain",
      "mcp__veya__veya_read_agent_onchain",
      "mcp__veya__veya_account",
      "mcp__veya__veya_list_environments",
      "mcp__veya__veya_get_environment",
      "mcp__veya__veya_list_agents",
      "mcp__veya__veya_list_api_memory",
      "mcp__veya__veya_list_executions",
      "mcp__veya__veya_list_proofs",
      "mcp__veya__veya_paid_discover"
    ],
    "ask": [
      "mcp__veya__veya_hash_blake3",
      "mcp__veya__veya_verify_transaction",
      "mcp__veya__veya_api_health",
      "mcp__veya__veya_prove",
      "mcp__veya__veya_seal_decision",
      "mcp__veya__veya_pq_keygen",
      "mcp__veya__veya_pq_sign",
      "mcp__veya__veya_pq_verify",
      "mcp__veya__veya_run_consensus",
      "mcp__veya__veya_sealed_execute",
      "mcp__veya__veya_set_tool_policy",
      "mcp__veya__veya_route_message",
      "mcp__veya__veya_route_secure_message",
      "mcp__veya__veya_verify_secure_message",
      "mcp__veya__veya_store_memory",
      "mcp__veya__veya_invalidate_memory",
      "mcp__veya__veya_client_run_consensus",
      "mcp__veya__veya_pq_fingerprint",
      "mcp__veya__veya_public_stats",
      "mcp__veya__veya_verify_commitment_onchain",
      "mcp__veya__veya_commitment_exists",
      "mcp__veya__veya_guest_login",
      "mcp__veya__veya_tier",
      "mcp__veya__veya_create_environment",
      "mcp__veya__veya_deploy_agent",
      "mcp__veya__veya_run_protected_execution",
      "mcp__veya__veya_boundnet_invoke",
      "mcp__veya__veya_anchor_proof",
      "mcp__veya__veya_verify_proof_api",
      "mcp__veya__veya_writes_status",
      "mcp__veya__veya_store_commitment",
      "mcp__veya__veya_attest_execution",
      "mcp__veya__veya_register_environment",
      "mcp__veya__veya_register_pq_onchain",
      "mcp__veya__veya_anchor_pq_attestation",
      "mcp__veya__veya_paid_call",
      "mcp__veya__veya_paid_run"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as veya. Review it before you use it.

Capability tags behind 1 rule
  • mcp__veya__veya_paid_call outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.veyanet/veya/verify?hash=3d8b541bac5d2196e360ed4d037f8a1ca632c3fcc635082552d0ddccd029b071" | jq -e '.changed == false'

Pinned hash 3d8b541bac5d, from Nov 20, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.veyanet/veya/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.veyanet/veya
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.veyanet/veya.svg)](https://radar.anlyon.com/servers/io.github.veyanet/veya)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:51 UTC.

VEYA MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the VEYA MCP server safe?

No scan can promise that. What its definitions show: 55 tools, 37 of which can change, send or delete something, and 13 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the VEYA MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the VEYA MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the VEYA MCP server have?

55 tools: 37 write, 18 read. veya_hash_blake3, veya_verify_transaction, veya_api_health, veya_prove, veya_seal_decision, veya_pq_keygen, veya_pq_sign, veya_pq_verify and 47 more.

Does the VEYA MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the VEYA MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): veya_paid_call.

Has the VEYA MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.