← Registry

Security & Testing

veyanet.tech

Provides Veya cryptographic execution and transaction verification tools, including sealed execution info, chain RPC ping, BLAKE3 hashing, transaction verification, and API health checks.

1 endpoint51 known toolsFirst detected October 6, 2026Last detected October 22, 2026

ENDPOINT 1

https://mcp.veyanet.tech/mcp

No auth detected

MCP server metadata

Name
@veyanet/mcp
Version
1.2.8
Capabilities
tools.listChanged

Known tools 51

veya_describe

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

Inferred read-only
veya_ping_chain

Ping Robinhood Chain RPC — chain id, block, contract

Inferred read-only
veya_hash_blake3

Compute BLAKE3 hex digest (commitment helper)

Inferred read-only
veya_verify_transaction

Verify a Veya.

Inferred read-only
veya_api_health

Check the VEYA API /health status (api.

Inferred read-only
veya_prove

Prove text, canonical JSON, or a receipt hash.

Inferred read-only
veya_seal_decision

Seal an evidence id and a decision.

Inferred read-only
veya_pq_keygen

Generate an ML-DSA-44 post-quantum identity keypair (local, no chain write)

Potential side effects
veya_pq_sign

Sign UTF-8 text with ML-DSA-44

Inferred read-only
veya_pq_verify

Verify an ML-DSA-44 signature over UTF-8 text

Inferred read-only
veya_run_consensus

Run 2-of-3 BLAKE3 consensus on this server's validator list.

Inferred read-only
veya_sealed_execute

AES-256-GCM protected execution on this server's sealed node.

Inferred read-only
veya_set_tool_policy

Allow or deny a tool for an agent.

Inferred read-only
veya_route_message

Check the saved tool rule for this API key before routing.

Inferred read-only
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.

Potential side effects
veya_verify_secure_message

Verify ML-DSA signature on a secure routed message envelope

Potential side effects
veya_store_memory

Store agent memory for the account behind this API key.

Inferred read-only
veya_read_memory

Read one memory row owned by this API key.

Inferred read-only
veya_invalidate_memory

Nullify one memory row owned by this API key.

Inferred read-only
veya_client_run_consensus

Deprecated: use veya_run_consensus.

Inferred read-only
veya_pq_fingerprint

BLAKE3 fingerprint of an ML-DSA public key hex

Inferred read-only
veya_public_stats

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

Inferred read-only
veya_public_list_agents

List public agent registry rows

Inferred read-only
veya_public_get_agent

Fetch one public agent by id

Inferred read-only
veya_public_list_certificates

List public certificate / attestation rows

Inferred read-only
veya_public_get_certificate

Fetch one public certificate by id

Inferred read-only
veya_public_get_execution

Fetch a public execution proof by id

Inferred read-only
veya_verify_commitment_onchain

Parse Veya.

Inferred read-only
veya_commitment_exists

eth_call Veya.

Inferred read-only
veya_read_environment_onchain

Read environment record from Veya.

Inferred read-only
veya_read_agent_onchain

Read agent record from Veya.

Inferred read-only
veya_guest_login

Create a guest session on the product API (Use listing only).

Potential side effects
veya_account

Return the wallet bound to a product API key

Inferred read-only
veya_list_environments

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

Inferred read-only
veya_get_environment

Get one environment by id

Inferred read-only
veya_create_environment

Create a workspace in the product API.

Potential side effects
veya_list_agents

List agents in an environment

Inferred read-only
veya_deploy_agent

Create an agent in a workspace.

Potential side effects
veya_list_api_memory

List memory entries via product API for an environment

Inferred read-only
veya_list_executions

List executions for an environment via product API

Inferred read-only
veya_run_protected_execution

Run protected execution via product API (Build).

Inferred read-only
veya_boundnet_invoke

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

Inferred read-only
veya_list_proofs

List Use-mode proof anchors for the account

Inferred read-only
veya_anchor_proof

Anchor a content proof on Veya.

Inferred read-only
veya_verify_proof_api

Check a commitment or anchor transaction through the product API.

Inferred read-only
veya_writes_status

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

Inferred read-only
veya_store_commitment

Write a 32-byte commitment to Veya.

Potential side effects
veya_attest_execution

attestExecution on Veya.

Inferred read-only
veya_register_environment

registerEnvironment on Veya.

Inferred read-only
veya_register_pq_onchain

Generate ML-DSA identity and register environment + commitment on Veya.

Inferred read-only
veya_anchor_pq_attestation

Link PQ identity hash to execution hash on Veya.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.veyanet-mcp]
url = "https://mcp.veyanet.tech/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "veyanet-mcp": {
      "type": "http",
      "url": "https://mcp.veyanet.tech/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: veyanet-mcp
Remote MCP URL: https://mcp.veyanet.tech/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "veyanet-mcp": {
      "url": "https://mcp.veyanet.tech/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "veyanet-mcp": {
      "type": "http",
      "url": "https://mcp.veyanet.tech/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "veyanet-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.veyanet.tech/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.