Skip to content

VEYA

by veyanet · remote · no sign-in to list tools · v1.2.8 · published by GitHub user veyanet

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

Changes · 34

51 tools: 34 change things and 17 only read.

Scanned Oct 21, 2026

12 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

12 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 6 more findings

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

51 tools

Changes things 34Claude 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 relayer.
  • 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_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 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_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_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 relayer 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 relayer does not
Only reads 17Claude Code: allow
  • 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_ping_chainPing Robinhood Chain RPC — chain id, 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 — chain id, 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.

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>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, 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"
    ],
    "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_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"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as veya. Review it before you use it.