Security & Testing

opulencedigitech.ca

Screens x402 endpoints to provide a risk verdict with a numeric score and reasons before payment.

1 endpoint1 known toolsFirst detected August 17, 2026Last detected August 17, 2026

ENDPOINT 1

https://check.opulencedigitech.ca/mcp

No auth detected

Capabilities

tools.listChanged

Free trial summary: screen any x402 endpoint before paying and get an ALLOW / REVIEW / BLOCK verdict with a numeric score and the top reasons.

Inferred read-only

CONNECT WITH APPROVAL

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

Codex

~/.codex/config.toml

[mcp_servers.clearpay-mcp]
url = "https://check.opulencedigitech.ca/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "clearpay-mcp": {
      "type": "http",
      "url": "https://check.opulencedigitech.ca/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: clearpay-mcp
Remote MCP URL: https://check.opulencedigitech.ca/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": {
    "clearpay-mcp": {
      "url": "https://check.opulencedigitech.ca/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "clearpay-mcp": {
      "type": "http",
      "url": "https://check.opulencedigitech.ca/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "clearpay-mcp",
  "transport": "streamable-http",
  "url": "https://check.opulencedigitech.ca/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 opulencedigitech.ca was fetched 2026-08-21T11:00:53.383Z.

Trust status Neutral

opulencedigitech.ca 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.