INDIVIDUAL MCP TOOL
inspect_test
Decodes a test and describes it: slots, variants, context, and whether it can be served by redirect.
LIVE ENDPOINT
https://livevariant.link/mcp
Connect to this endpoint to inspect the live schema for inspect_test 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.livevariant]
url = "https://livevariant.link/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"livevariant": {
"type": "http",
"url": "https://livevariant.link/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: livevariant
Remote MCP URL: https://livevariant.link/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": {
"livevariant": {
"url": "https://livevariant.link/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"livevariant": {
"type": "http",
"url": "https://livevariant.link/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "livevariant",
"transport": "streamable-http",
"url": "https://livevariant.link/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
build_test— Creates a LiveVariant test and returns every URL needed to run it, plus a freshly generated stats secret.generate_priors— Takes YOUR estimate of how each variant will perform and converts it into the prior the model starts from, so a test does not spend its first visitors rediscovering what you already suspect.get_stats— Fetches a test's results and works out what they mean.get_test_status— Reports what the deployment's registry knows about a test: whether it is claimed into an account (and by which organization), and whether each redirect destination is a verified domain.list_tests— Lists tests registered to the signed-in account, newest first, with cursor pagination and an optional case-insensitive name filter.register_test— Registers a test you built earlier to the organization a publishable key belongs to, so it shows under My tests and its stats are readable from the dashboard without the secret.upload_image— Uploads an image to the deployment's asset store and returns its URL, for use as a variant's `image` (email tests) or `url`.variant_brief— Returns the constraints to write or generate test variants against, for email or web, plus the rules that decide whether a test can be read at all once it runs.