MCP server — VVDex docs

Address	`https://vvdexops.com/mcp`
Transport	Streamable HTTP, `POST` only, replies as `application/json`
Authentication	`Authorization: Bearer vvx_…` (an API key from Settings → API keys)
Protocol versions	`2025-06-18`, `2025-03-26`, `2024-11-05`

Add it to a client

Claude Code:

shell

$ claude mcp add --transport http vvdex https://vvdexops.com/mcp \
    --header "Authorization: Bearer $VVDEX_API_KEY"

Clients that read an mcpServers JSON file (for example a project’s .mcp.json):

json

{
  "mcpServers": {
    "vvdex": {
      "type": "http",
      "url": "https://vvdexops.com/mcp",
      "headers": { "Authorization": "Bearer vvx_…" }
    }
  }
}

Keep the key out of shared files: most clients can read it from an environment variable.

Tools

Tool	What it does	Arguments
`list_models`	Your saved models, your connections with the model ids each reported	none
`list_forge_exams`	The certified Forge exams, with their step budget, tools and certification evidence	none
`run_playground`	One prompt to 1–8 models; answers with latency, tokens and cost	`prompt` or `messages`, `models`, optional `system`, `temperature`, `max_tokens`, `json_mode`
`start_eval`	Starts a run on a Forge exam or a dataset; returns its id	`forge` (with `attempts`) or `dataset_id`, `models`, optional `name`, `graders`, `judge`, `repeats`
`get_eval`	Status, progress and per-model results; optionally individual cases	`id`, optional `results` (`failed`, `error`, `passed`, `all`) and `limit`
`compare_evals`	Regressions, improvements and unchanged cases between two runs	`a`, `b`

A model is {"connection_id": "…", "model": "…"}. There are no tools that delete, revoke or share anything.

How it behaves

Each tool calls the same REST endpoint the web app uses, with your key. Limits, metering and workspace rules are exactly the API’s.
A refusal comes back as a tool error with the API’s own words, for example a reached daily limit; an unknown tool name is a protocol error.
The server keeps no session between requests and offers no server-initiated stream (GET /mcp answers 405).
Browser cookies are ignored: only an API key opens this endpoint.

Try it with curl

shell

$ curl -s https://vvdexops.com/mcp \
    -H "Authorization: Bearer $VVDEX_API_KEY" \
    -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
    -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

The VVDex MCP server

Add it to a client

Tools

How it behaves

Try it with curl