VEYA

VEYA MCP

The official Model Context Protocol server for post-quantum agent tools, chain verification, sealed-execution service info, and protocol settlement on Robinhood Chain.

[Official Website](https://veyanet.tech) • [X (Twitter)](https://x.com/withveya) • [Public MCP URL](https://mcp.veyanet.tech/mcp) • [Documentation Index](./docs/README.md) • [Network Specifications](./docs/NETWORK_PIN.md) • [Security Policy](./SECURITY.md)

---

💡 Information: What is VEYA?

The VEYA Protocol is a cryptographically shielded execution layer engineered for post-quantum resilient autonomous agent fleets on Robinhood Chain. Traditional LLM agent frameworks suffer from severe structural vulnerabilities: because agents require private execution contexts—such as API integration credentials, proprietary system prompts, treasury authority, and policy rules—running them in standard host runtimes exposes sensitive state in plaintext to host operators, database administrators, and network intermediaries.

VEYA solves this security gap by establishing client-side cryptographic boundaries and post-quantum attestation primitives. Sensitive agent workloads are protected through local post-quantum key generation (ML-DSA-44), quantum-resistant session negotiation (Kyber-768), high-throughput cryptographic digests (BLAKE3-256), sealed execution with AES-256-GCM, and 2-of-3 multi-node consensus. This tree defaults to Mainnet. Veya.sol there is the protocol contract 0x87dC582eEA544A434a5C1e30Ca3d12c1e548a674. ROBINHOOD_NETWORK=testnet keeps Testnet.

The VEYA MCP Server

The @veyanet/mcp package is the canonical Model Context Protocol surface for VEYA — the full agent-facing tool set. It speaks Streamable HTTP so Claude, Cursor, and other MCP clients can paste a single URL and invoke crypto, fleet, registry, product API, and own-wallet on-chain write tools without cloning @veyanet/sdk. Cryptography, chain-id guards, and receipt parsing are delegated to @veyanet/sdk; this package owns the HTTP transport, tool registration, product apiKey forwarding, and the public service info.

By connecting an MCP client to @veyanet/mcp, you enable the following core capabilities:

• Paste-URL Access: Connect via https://mcp.veyanet.tech/mcp (Streamable HTTP).
• Public Tools: Describe the stack, ping Robinhood Chain, BLAKE3, verify Veya.sol txs, PQ crypto, registry, product sessions via https://api.veyanet.tech.
• Own-wallet writes: On-chain tools need a product API key (veya_dev_ / veya_live_) and your funded wallet. The hosted signer is not the gas payer.
• SDK-Backed Settlement: Chain calls use @veyanet/sdk. The default profile is Mainnet. Testnet is ROBINHOOD_NETWORK=testnet.
• Backend-owned fleet: Consensus validators and sealed capacity belong to the product API (https://api.veyanet.tech).

---

📖 Table of Contents

1. Architectural Design Philosophy
2. High-Level MCP Data Flow
3. Installation & Environmental Requirements
4. Server Configuration & Initialization
5. Connect in Claude / Cursor
6. Core Tools Overview

• Service info & Discovery
• Chain Read & Verify
• BLAKE3 Commitment Helper
• Product API Health
• Authenticated On-Chain Writes

1. Comprehensive Quickstart
2. Transport, Auth & Reliability
3. Advanced Cryptography Boundaries
4. Operator Diagnostics & CLI Tools
5. Documentation Directory Index
6. Frequently Asked Questions (FAQ)
7. Contributing & Security Guidelines
8. License

---

🛡️ Architectural Design Philosophy

The design of @veyanet/mcp is governed by the paradigm of Thin Protocol Gate over Thick Cryptographic Client. In naive MCP servers, business logic, secrets, and chain writes are mixed into tool handlers with soft auth. VEYA separates those concerns: the MCP process is a transport and policy shell; @veyanet/sdk remains the cryptographic engine that executes hashing, verification, and EvmAnchor writes.

This core philosophy is implemented through three primary architectural pillars:

1. Streamable HTTP as the Public Contract

Public users and agent runtimes connect with a single URL. The server implements MCP Streamable HTTP (POST /mcp) using @modelcontextprotocol/sdk.

2. Own-wallet write surface

On-chain write tools are always registered. Product writes need a product apiKey and your payerPrivateKey. veya_prove is separate: a read needs no key, and an anchor needs environmentId plus payerPrivateKey only. msg.sender is your address. An empty wallet returns: Mainnet: 'Your wallet has no ETH on Robinhood Chain.' Testnet: 'You don't have testnet tokens. Please get them for the transaction.'

3. Clear service info

GET /health and veya_describe name the selected profile, sealed = AES-256-GCM, and whether writes are enabled. The default profile is Mainnet. Quorum is matching hashes; unreachable nodes return consensus_reached: false. Veya.sol is a protocol contract.

---

⚡ High-Level MCP Data Flow

The following diagram illustrates how @veyanet/mcp accepts Streamable HTTP tool calls, gates writes, and settles through @veyanet/sdk onto Robinhood Chain:

flowchart TB

subgraph ClientSpace["MCP Client (Claude / Cursor / Agent Runtime)"] PasteURL["Paste https://mcp.veyanet.tech/mcp"] ToolCall["veya_* tool invocation"] end

subgraph McpBoundary["@veyanet/mcp Streamable HTTP"] Landing["GET /"] Health["GET /health"] PostMcp["POST /mcp"] Auth{"product apiKey + your wallet?"} PublicTools["Public tools"] WriteTools["Own-wallet write tools"] end

subgraph SdkBoundary["@veyanet/sdk"] ReadClient["VeyaClient read / verify / hash"] EvmAnchor["EvmAnchor writes + eth_chainId guard"] end

subgraph ApiBoundary["VEYA Product API"] ApiHealth["https://api.veyanet.tech/health"] end

subgraph Blockchain["Protocol settlement (Mainnet by default)"] VeyaSol["Veya.sol\nCommitments · Environments · Attestations"] end

PasteURL --> PostMcp ToolCall --> PostMcp PostMcp --> Auth Auth -->|"no key / public tools"| PublicTools Auth -->|"apiKey + funded payer"| WriteTools PublicTools --> ReadClient PublicTools -->|"veya_api_health"| ApiHealth WriteTools --> EvmAnchor ReadClient --> VeyaSol EvmAnchor --> VeyaSol Landing --> McpBoundary Health --> McpBoundary

---

📦 Installation & Environmental Requirements

Public users (recommended)

Paste into Claude / Cursor (Streamable HTTP):

https://mcp.veyanet.tech/mcp

Optional TypeScript library:

npm install @veyanet/sdk

npm package (optional)

npm install -g @veyanet/mcp

veya-mcp

or: npx -y @veyanet/mcp

Starts a Streamable HTTP server. After TLS, point clients at your public HTTPS connector. Keep PUBLIC_MCP_URL=https://mcp.veyanet.tech/mcp as the product paste URL in docs and landing. See docs/DEPLOYMENT.md.

Requirements

• Node.js ≥ 20
• Outbound HTTPS to Robinhood RPC and https://api.veyanet.tech
• Dependency: @veyanet/sdk from npm

---

🔑 Server Configuration & Initialization

The process loads configuration from environment variables. Unset ROBINHOOD_NETWORK is Mainnet. ROBINHOOD_NETWORK=testnet is Testnet. Copy .env.example to .env for local overrides. Never commit `.env`.

Configuration Resolution Cascade

Parameters resolve from process environment first, then the Mainnet profile (PUBLIC_MCP_URL=https://mcp.veyanet.tech/mcp). Testnet is ROBINHOOD_NETWORK=testnet. Addresses are in docs/NETWORK_PIN.md.

import { loadConfig, createHttpApp, startHttpServer } from "@veyanet/mcp";

// 1. Zero-config start (Mainnet) startHttpServer();

// 2. Explicit config for operators const cfg = loadConfig(); const app = createHttpApp(cfg); app.listen(cfg.port, cfg.host);

Environment Variables Reference

Host-only settings (fleet URLs and host signing keys) are covered in the operator guide, docs/DEPLOYMENT.md. Public users never set them.

---

🔌 Connect in Claude / Cursor

Production (public users / public clients)

Paste into a custom MCP connector using Streamable HTTP transport:

https://mcp.veyanet.tech/mcp

No API key is required for public tools, including veya_prove. Product tools need apiKey. Product on-chain writes need that key plus your funded wallet. An anchor through veya_prove needs environmentId and payerPrivateKey only.

Claude CLI

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

Cursor IDE

Settings → MCP → Add custom MCP server / connector