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.
ENDPOINT 1
https://mcp.veyanet.tech/mcp
MCP server metadata
- Name
- @veyanet/mcp
- Version
- 1.2.8
Known tools 51
veya_describeService info: AES-256-GCM sealed execution and the selected settlement profile
Inferred read-onlyveya_pq_keygenGenerate an ML-DSA-44 post-quantum identity keypair (local, no chain write)
Potential side effectsveya_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.
Potential side effectsveya_verify_secure_messageVerify ML-DSA signature on a secure routed message envelope
Potential side effectsveya_public_statsPublic registry stats from the product API (verified agents / proofs)
Inferred read-onlyveya_list_environmentsList environments for a product API key (guest JWT sees showcase / Use scope only)
Inferred read-onlyveya_boundnet_invokeInvoke a Boundnet / coordination tool via product API (policy gated)
Inferred read-onlyveya_verify_proof_apiCheck a commitment or anchor transaction through the product API.
Inferred read-onlyveya_writes_statusReports how on-chain writes work on this server: your own wallet sends them, the host relayer does not
Inferred read-onlyveya_register_pq_onchainGenerate ML-DSA identity and register environment + commitment on Veya.
Inferred read-onlyCONNECT 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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.