The Velora MCP server is hosted, so installation is one step: point your client at the endpoint. Nothing runs on your machine, and the server requires no API key.
https://ai.velora.xyz/mcp
The endpoint speaks Streamable HTTP, the current MCP transport. Clients that only support the legacy HTTP+SSE transport (pre-2025-03-26 spec) use https://ai.velora.xyz/mcp/sse instead.
Client setup claude mcp add --transport http velora https://ai.velora.xyz/mcp
Run /mcp inside Claude Code to confirm the server is connected and list its tools. Add the server as a custom connector:
Open Settings → Connectors .
Click Add custom connector .
Name it velora and set the URL to https://ai.velora.xyz/mcp.
No OAuth or token step appears because the server requires no authentication. Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally): { "mcpServers" : { "velora" : { "url" : "https://ai.velora.xyz/mcp" } } }
Add to .vscode/mcp.json in your workspace: { "servers" : { "velora" : { "type" : "http" , "url" : "https://ai.velora.xyz/mcp" } } }
Add to ~/.codeium/windsurf/mcp_config.json: { "mcpServers" : { "velora" : { "serverUrl" : "https://ai.velora.xyz/mcp" } } }
Any MCP-compatible client works with the generic remote-server config: { "mcpServers" : { "velora" : { "url" : "https://ai.velora.xyz/mcp" } } }
The server is stateless: each JSON-RPC POST stands alone, no initialize handshake or session header is required, and any number of clients can connect concurrently. CORS allows any origin, so browser-based clients work too. Verify the connection A correctly connected client lists 9 tools (all prefixed velora_) and 5 resources (all prefixed velora://docs/).
List the server’s tools (tools/list, or your client’s MCP panel). Expect 9 tools, from velora_search_docs to velora_validate_agent_plan.
Call velora_get_supported_chains with no arguments. Expect a chain list that includes Ethereum (1), Base (8453), and Arbitrum (42161).
You can also smoke-test from the command line without any MCP client:
curl -s https://ai.velora.xyz/mcp \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
The response arrives as a single SSE frame; the JSON-RPC result is on the data: line.
Troubleshooting Symptom Cause Fix 405 on GET /mcpThe stateless endpoint has no standalone SSE stream. POST JSON-RPC to /mcp, or use the legacy transport at /mcp/sse if your client requires a GET-opened stream. 406 Not Acceptable from your own client codeMissing Accept header values. Send Accept: application/json, text/event-stream on every POST. Client expects an SSE endpoint event The client speaks the pre-2025-03-26 HTTP+SSE transport. Point it at https://ai.velora.xyz/mcp/sse instead. Client asks for an API key or OAuth flow Misconfigured auth settings. Leave authentication empty; the server is public and requires none. Connection works but tool calls are rejected Per-IP rate limiting. Back off and retry; batch agent work instead of polling in a tight loop.
Next steps
Available tools Parameters, return shapes, and the agent rules each tool enforces.
Examples End-to-end tool-call sequences for Delta and Market flows.
Last modified on June 14, 2026
