Connect VeriActa to your AI assistant

VeriActa is a remote MCP server at https://veriacta.ai/mcp. Add it to your assistant and ask a tax or legal question: the answer quotes the law in force and cites it. Most assistants sign you in through the browser, so there is no key to copy. You need a VeriActa account, which is free and starts with 200 free credits: create one, or let the sign-in page do it.

Claude

Sign in, no keyChecked 2026-11-02

VeriActa is in Claude's connector directory: add it from there, then sign in. There is no key to copy.

Add to Claude from its directoryAdd as a custom connector

  1. Use the first button above to open VeriActa in Claude's directory, and add it.
  2. Claude opens a VeriActa page: sign in or create a free account, then allow Claude.
  3. In a chat, switch VeriActa on under the tools menu and ask your question.
  4. Or add it yourself as a custom connector: the second button, or in Claude go to Settings, Connectors, Add custom connector, name it VeriActa and paste the address.
Connector address
https://veriacta.ai/mcp

Claude's own guide to MCP servers

What to ask VeriActa in Claude, with worked answers

ChatGPT

Sign in, no keyChecked 2026-11-02

Add VeriActa as a custom MCP server, then sign in. There is no key to copy.

  1. In ChatGPT open Settings, Apps and connectors. Custom servers need developer mode: switch it on under Advanced settings.
  2. Choose Create, name it VeriActa and paste the address. Authentication: OAuth.
  3. ChatGPT opens a VeriActa page: sign in or create a free account, then allow ChatGPT.
  4. In a chat, pick VeriActa from the plus menu and ask your question.
MCP server URL
https://veriacta.ai/mcp

ChatGPT's own guide to MCP servers

What to ask VeriActa in ChatGPT, with worked answers

Cursor

Sign in, no keyFrom the client's documentation, not yet run by us

One block for the editor and the cursor-agent CLI: both read the same file. Cursor signs you in through the browser the first time it connects.

Add to Cursor

  1. Use the button above, or add the block to ~/.cursor/mcp.json.
  2. Open Cursor Settings, MCP: VeriActa shows a sign-in prompt. Sign in or create a free account and allow Cursor.
  3. Ask in Agent mode.
~/.cursor/mcp.json
{
  "mcpServers": {
    "veriacta": {
      "url": "https://veriacta.ai/mcp"
    }
  }
}

Cursor's own guide to MCP servers

VS Code and GitHub Copilot

Sign in, no keyFrom the client's documentation, not yet run by us

Register the server in your workspace. VS Code opens a browser to sign in when the server starts, and the tools are then available to Copilot Chat in agent mode.

Add to VS Code

  1. Use the button above, or add the block to .vscode/mcp.json in your workspace.
  2. Start the server from the file (the Start link above it). Sign in or create a free account and allow VS Code.
  3. Open Copilot Chat in agent mode and ask.
.vscode/mcp.json
{
  "servers": {
    "veriacta": {
      "type": "http",
      "url": "https://veriacta.ai/mcp"
    }
  }
}

VS Code and GitHub Copilot's own guide to MCP servers

Claude Code

Sign in, no keyFrom the client's documentation, not yet run by us

One command. Claude Code opens a browser to sign in the first time you use the server.

  1. Run the command.
  2. In Claude Code run /mcp, choose veriacta and authenticate: sign in or create a free account and allow Claude Code.
  3. Ask your question.
Terminal
claude mcp add --transport http veriacta https://veriacta.ai/mcp

Claude Code's own guide to MCP servers

Codex CLI

API keyFrom the client's documentation, not yet run by us

Codex configures MCP in TOML. The key stays in your environment: the file names the variable, not the key.

Create an API key

  1. Create an API key on your account page and export it in your shell as VERIACTA_API_KEY.
  2. Add the block to ~/.codex/config.toml.
  3. Start Codex and ask your question.
~/.codex/config.toml
[mcp_servers.veriacta]
url = "https://veriacta.ai/mcp"
bearer_token_env_var = "VERIACTA_API_KEY"

Codex CLI's own guide to MCP servers

Gemini CLI

API keyFrom the client's documentation, not yet run by us

One command adds VeriActa to your Gemini CLI settings. Gemini stores the header in ~/.gemini/settings.json, so the key ends up in that file: keep the file private.

Create an API key

  1. Create an API key on your account page and export it in your shell as VERIACTA_API_KEY.
  2. Run the command on one line.
  3. Start Gemini CLI and ask your question.
Terminal
gemini mcp add --scope user --transport http veriacta https://veriacta.ai/mcp --header "Authorization: Bearer $VERIACTA_API_KEY"

Gemini CLI's own guide to MCP servers

GitHub Copilot CLI

API keyFrom the client's documentation, not yet run by us

For the Copilot CLI. Using Copilot inside your editor? Follow VS Code above.

Create an API key

  1. Create an API key on your account page and export it in your shell as VERIACTA_API_KEY.
  2. Add the block to ~/.copilot/mcp-config.json.
  3. Start the Copilot CLI and ask your question.
~/.copilot/mcp-config.json
{
  "mcpServers": {
    "veriacta": {
      "type": "http",
      "url": "https://veriacta.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${VERIACTA_API_KEY}"
      }
    }
  }
}

GitHub Copilot CLI's own guide to MCP servers

Agent Skill

Sign in, no keyFrom the client's documentation, not yet run by us

The skill teaches an assistant when to use VeriActa, which tool to call and how to cite the answer. It works with the MCP server connected as above.

  1. Run the command to install the skill for your user.
  2. Connect the MCP server as shown for your assistant.
  3. Ask a tax or legal question: the assistant picks the skill up by itself.
Terminal
mkdir -p ~/.claude/skills/veriacta && curl -fsSL https://veriacta.ai/skill.md -o ~/.claude/skills/veriacta/SKILL.md

Agent Skill's own guide to MCP servers

Any other MCP host

API keyFrom the client's documentation, not yet run by us

Any host that supports remote MCP servers over streamable HTTP can use VeriActa. A host with OAuth needs only the address and signs you in. A host without it sends your API key in a header.

Create an API key

  1. Add a remote MCP server with the address below.
  2. If the host does not offer sign-in: create an API key on your account page and send it as the Authorization header (Bearer) or in X-API-Key.
  3. Keep the key in an environment variable or the host's secret store, not in a file you commit.
MCP server settings
{
  "url": "https://veriacta.ai/mcp",
  "headers": {
    "Authorization": "Bearer ${VERIACTA_API_KEY}"
  }
}

Using an API key

For a host that cannot sign in through the browser. Create a key on your account page; it is shown once. Keep it in your environment and let the config name the variable:

Shell profile
export VERIACTA_API_KEY="your key here"

The server reads the key from Authorization: Bearer … or from X-API-Key. Never paste a key into a conversation, and never commit one. You can revoke a key, or disconnect a signed-in assistant, on your account page at any time.

Then ask

The assistant should quote the provision and give its citation. Every answered call spends credits from your account; your account page shows what each call cost.

If it does not connect

For agents: llms.txt, the server card and the skill say the same in a form a machine reads.