Agents

AI Infrastructure for
Digital Assets

Bring Validation Cloud into Claude Code, Codex, Cursor or VS Code through the MCP server, the CLI or the Admin API skill.
‍

Get started free →
Read the docs

Server URL

https://mcp.validationcloud.io/mcp

Add to Claude Code

claude mcp add --transport http validation-cloud https://mcp.validationcloud.io/mcp

Then run /mcp in Claude Code, select validation-cloud, choose Authenticate and log in with your Validation Cloud account.

See the tools

|

Every tool, by product →

Connect

MCP server, CLI or skill

Pick the one that fits where your agent runs.
They share one login and one set of permissions.

MCP

For editors and chat clients

One remote server over Streamable HTTP with OAuth. Twelve tools across Node API and Mavrik, for Claude Code, Codex, Cursor, VS Code and any MCP client.

Server reference

CLI

For terminals, scripts, CI

A shortcut to the MCP server from the terminal and CI. Log in once, then create endpoints, check usage and send RPC calls from scripts and from agents that work in a shell.

CLI reference

Skill

For Claude Code, Codex

The Admin API skill teaches Claude Code and Codex to call the Admin API for endpoints, usage and chains. Installs from the validationcloud/skills marketplace.

View on GitHub
Install the MCP server

How it fits

A layer on the products you already use

Your agent uses the account, plan and roles your team already has.

Your agent

Where the work starts: an editor, a chat client, a notebook, a shell or a CI job.

Claude CodeCodexCursorVS Codeany MCP clientscripts and CI
One login, twelve toolsMCP server

You log in once with your Validation Cloud account. The server inherits your team's plan and your role, and routes each tool call to one of the products below.

CLI

A shortcut to the same server from a terminal, a script or CI. Same tools, same login.

ManageAdmin API

The admin side of the Node API: create and delete endpoints, pull compute-unit usage, check plan limits and team roles.

QueryNode API

Send RPC calls through your endpoints and get the node's response back, metered in compute units as usual.

AskMavrik

Digital-asset market intelligence in plain language, from the same Chat, Monitor and Recon workspaces.

The Admin API skill sits beside this stack: it teaches Claude Code and Codex to call the Admin API directly.

How you use it

Connect, prompt, execute

Three steps, whichever client you use.

1. Connect

What you do

Add the MCP server to your client or install the CLI, then log in with your Validation Cloud account.
‍

Example

claude mcp add --transport http validation-cloud https://mcp.validationcloud.io/mcp

Works with

Claude Code

Codex

Cursor

VS Code

2. Prompt

What you do

Describe what you need in plain language. The agent picks the tool and the parameters, within your plan and your role.
‍

Example

"Create a Base mainnet endpoint for staging and give me the HTTPS URL."
‍

Tools it calls

nodeapi_create_endpoint

nodeapi_get_endpoint

3. Execute

What you do

The agent runs the tool against your team's account and returns the result.

Example

"Show this month's compute-unit usage by endpoint."

‍

Tools it calls

nodeapi_get_team_usage

MCP server

Install the MCP server

One remote server over Streamable HTTP.
Point your client at the URL and log in with your Validation Cloud account.

Claude Code

Codex

Cursor

VS Code

  1. Open a terminal in your project folder. The server is added for that project only; to use it in every project, add --scope user after --transport http.
  2. Add the server:
    claude mcp add --transport http validation-cloud https://mcp.validationcloud.io/mcp
  3. Run /mcp inside Claude Code, select validation-cloud, choose Authenticate and log in when the browser opens. The server then shows as connected, with its tools.

For more details, see the Claude Code MCP documentation.

  1. Open ~/.codex/config.toml, or create it if it does not exist.
  2. Add the server:
    [mcp_servers.validation-cloud]
url = "https://mcp.validationcloud.io/mcp"
  3. Run codex mcp login validation-cloud and log in when the browser opens. Then start Codex and ask it to call nodeapi_get_health.

For more details, see the Codex MCP documentation.

Install in Cursor

One click opens Cursor and asks to install the server, or follow the manual steps below.

  1. Open ~/.cursor/mcp.json, or create it if it does not exist.
  2. Add the server, save the file and restart Cursor:
    {
  "mcpServers": {
    "validation-cloud": {
      "url": "https://mcp.validationcloud.io/mcp"
    }
  }
}
  3. Open Customize > MCPs in the sidebar (Settings > Tools & MCP in some versions). When validation-cloud shows Needs authentication, select Connect or Authenticate and log in when the browser opens; its tools then appear.

For more details, see the Cursor MCP documentation.

Install in VS Code

One click opens the server in VS Code; select Install, or follow the manual steps below.

  1. Create .vscode/mcp.json in your workspace:
    {
  "servers": {
    "validation-cloud": {
      "type": "http",
      "url": "https://mcp.validationcloud.io/mcp"
    }
  }
}
  2. Press ⌘ShiftP (Ctrl Shift P on Windows and Linux), run MCP: List Servers, select validation-cloud, then Start Server.
  3. When VS Code says validation-cloud wants to authenticate, select Allow and log in with your Validation Cloud account. The file you commit holds no credentials.

Requires VS Code 1.101 or later. For more details, see the VS Code MCP documentation.

Other clients

  1. Any client that speaks MCP over Streamable HTTP with OAuth can connect. Point it at the URL; the client opens a browser for you to log in on first connect:
    https://mcp.validationcloud.io/mcp
  2. Call nodeapi_get_health first. It returns the team ID and your role on the team, so the agent knows which tools will succeed.

For more details, see the Model Context Protocol specification.

Reading this as an agent? The same instructions are published as plain text at docs.validationcloud.io/agents/mcp.md.

Tools

Every tool, one list

Tools are grouped by product: Node API and Mavrik.

Node API

Account, usage and endpoint management for your team, plus chain data through your endpoints.

Tool

Access

Plan

What it does

nodeapi_rpc_call

READFREE

Sends a JSON-RPC request or batch through one of the team's endpoints and returns the node's response unchanged. Metered in compute units like any request to that endpoint.

nodeapi_get_health

READFREE

Checks the connection and returns the team ID and your role on the team.

nodeapi_get_account

READFREE

Plan, compute-unit quota, compute units used and remaining, and the current billing cycle.

nodeapi_list_chains

READFREE

Chains and networks available for endpoint creation, with WebSocket support per chain.

nodeapi_get_compute_unit_costs

READFREE

Compute-unit cost per method, chain, network and protocol, for pricing a request or a workload before running it.

nodeapi_list_endpoints

READFREE

The team's endpoints with chain, network, enabled state and HTTPS and WSS URLs.

nodeapi_get_endpoint

READFREE

One endpoint by ID.

nodeapi_get_team_usage

READFREE

Compute-unit time series for the team. Granularity HOUR, DAY, WEEK or MONTH; defaults to the current UTC month.

nodeapi_get_endpoint_usage

READFREE

Compute-unit time series for one endpoint, including deleted ones. Same granularity and defaults as team usage.

nodeapi_create_endpoint

WRITESCALE

Creates an endpoint on a chain and network, within the team's endpoint limit.

nodeapi_delete_endpoint

WRITESCALE

Deletes an endpoint. The key stops resolving immediately.

Mavrik

Digital-asset intelligence in natural language.

Tool

Access

Plan

What it does

mavrik_answerQuestion

READFREE

Asks Mavrik a question about digital-asset markets, wallets or flows in plain language and returns the answer into the agent's context.

FAQ

Questions

Short answers before you connect.

What should I use?

MCP when your agent lives in an editor or a chat client and you want tool calls with no setup beyond a login. The CLI when the work happens in a shell, a script or CI. The Admin API skill when you want Claude Code or Codex to write code against the Admin API.

Do I need a key?

No. The MCP server and the CLI log in with your Validation Cloud account in the browser and inherit your team's plan and your role, so there is no key to create. The Admin API skill is the exception: it uses an Admin API key from your dashboard.

What does it cost?

Read tools work on the Free plan. Creating an endpoint needs the Scale plan, and deleting one also needs the Admin role on the team. RPC calls made through an agent are metered in compute units, exactly like any other request to the same endpoint.

Get started

Connect your agent today

Free plan, no credit card required. Add the server, log in, and ask your agent about your chains, your endpoints or the market.

Get started →
Connect with our team