LIVE ENDPOINT
https://mcp.veyanet.tech/mcp
Connect to this endpoint to inspect the live schema for veya_get_environment and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.
Related tools
veya_describe— Service info: AES-256-GCM sealed execution and the selected settlement profileveya_ping_chain— Ping Robinhood Chain RPC — chain id, block, contractveya_hash_blake3— Compute BLAKE3 hex digest (commitment helper)veya_verify_transaction— Verify a Veya.veya_api_health— Check the VEYA API /health status (api.veya_prove— Prove text, canonical JSON, or a receipt hash.veya_seal_decision— Seal an evidence id and a decision.veya_pq_keygen— Generate an ML-DSA-44 post-quantum identity keypair (local, no chain write)