← Registry

Security & Testing

verixid.com

Verifies a VerixID registration record by its Record ID and optional Ownership Key.

1 endpoint1 known toolsFirst detected August 18, 2026Last detected September 18, 2026

ENDPOINT 1

https://mcp.verixid.com

No auth detected

MCP server metadata

Name
VerixID Verifier
Version
1.0.0
Capabilities
tools.listChanged

Known tools 1

verixid_verify

Verify a VerixID registration record using a Record ID, optionally with an Ownership Key.

Inferred read-only

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.verixid-verifier]
url = "https://mcp.verixid.com"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: verixid-verifier
Remote MCP URL: https://mcp.verixid.com

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": {
    "verixid-verifier": {
      "url": "https://mcp.verixid.com"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "verixid-verifier": {
      "type": "http",
      "url": "https://mcp.verixid.com"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "verixid-verifier",
  "transport": "streamable-http",
  "url": "https://mcp.verixid.com"
}
MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for verixid.com was fetched 2026-08-21T18:35:27.411Z and is being refreshed.

Trust status Neutral

verixid.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

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