LEGAION Verifier MCP server

LEGAION Verifier is the official remote MCP server from legaion.com. It answers at https://mcp.legaion.com over streamable HTTP and asks you to sign in with your legaion.com account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, got the sign-in challenge, so it is up.

Checks legal citations against the official register they should come from, and records it.

Description as the publisher wrote it.

What LEGAION Verifier needs before it works

A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your legaion.com account, and the tools appear once you have approved it.

Add LEGAION Verifier to your AI client

Every block below points at https://mcp.legaion.com. Pick your client and copy.

claude mcp add --transport http legaion-verifier https://mcp.legaion.com

{
  "mcpServers": {
    "legaion-verifier": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.legaion.com"]
    }
  }
}

{
  "mcpServers": {
    "legaion-verifier": {
      "url": "https://mcp.legaion.com"
    }
  }
}

{
  "servers": {
    "legaion-verifier": {
      "type": "http",
      "url": "https://mcp.legaion.com"
    }
  }
}

{
  "context_servers": {
    "legaion-verifier": {
      "url": "https://mcp.legaion.com"
    }
  }
}

{
  "mcpServers": {
    "legaion-verifier": {
      "serverUrl": "https://mcp.legaion.com"
    }
  }
}

{
  "mcpServers": {
    "legaion-verifier": {
      "url": "https://mcp.legaion.com"
    }
  }
}

name: LEGAION Verifier
version: 0.0.1
schema: v1
mcpServers:
  - name: LEGAION Verifier
    type: streamable-http
    url: https://mcp.legaion.com

{
  "mcpServers": {
    "legaion-verifier": {
      "httpUrl": "https://mcp.legaion.com"
    }
  }
}

{
  "mcpServers": {
    "legaion-verifier": {
      "type": "http",
      "url": "https://mcp.legaion.com"
    }
  }
}

{
  "mcpServers": {
    "legaion-verifier": {
      "url": "https://mcp.legaion.com"
    }
  }
}

goose://extension?url=https%3A%2F%2Fmcp.legaion.com&type=streamable_http&id=legaion-verifier&name=LEGAION%20Verifier

Is LEGAION Verifier up right now?

It answered our last check on 24 October 2026 in 1609 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to LEGAION Verifier

Questions about LEGAION Verifier

Is there an official LEGAION Verifier MCP server?

Yes. It is published by legaion.com and served from mcp.legaion.com, the vendor's own domain: https://mcp.legaion.com.

How do I sign in to LEGAION Verifier?

Add the server with a setup above. The first time your client connects it opens the sign-in page for legaion.com; approve it and the tools load.

Is LEGAION Verifier down?

It answered our last check on 24 October 2026 in 1609 ms. Over 6 checks since 12 September 2026 it answered 6.

How do I add LEGAION Verifier to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.legaion.com. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does LEGAION Verifier need an API key?

It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.

Where this comes from

Publisher: com.legaion. Endpoint host: mcp.legaion.com. ARD identifier: urn:air:com.legaion:mcp:verifier. First indexed 11 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.