Analytics

veriasia.io

Verified performance tracking for all model positions with SHA-256 commitments and public auditability.

1 endpoint0 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://veriasia.io/mcp

No auth detected

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.veriasia-io]
url = "https://veriasia.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "veriasia-io": {
      "type": "http",
      "url": "https://veriasia.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: veriasia-io
Remote MCP URL: https://veriasia.io/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": {
    "veriasia-io": {
      "url": "https://veriasia.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "veriasia-io": {
      "type": "http",
      "url": "https://veriasia.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "veriasia-io",
  "transport": "streamable-http",
  "url": "https://veriasia.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

BuiltWith Trust API v2 evidence for veriasia.io was fetched 2026-08-03T23:26:51.617Z and is being refreshed.

Trust status RestrictedContent

veriasia.io is assessed as RestrictedContent: Domain runs gambling-related technology.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.