← Registry

API Tools

crossingkeyintelligence.com

A read-only MCP server for discovering API/commerce providers, public offers, requirements, cost estimates, and result previews.

1 endpoint12 known toolsFirst detected September 29, 2026Last detected September 29, 2026

ENDPOINT 1

https://mcp.crossingkeyintelligence.com/mcp

No auth detected

MCP server metadata

Name
crossingkey-mcp
Version
3.0.0
Capabilities
tools.listChanged
Server instructions

Discover capabilities and requirements first. Obtain a cost estimate and result preview. Run execution preflight. Stop before payment or execution. Explicit human authorization is required before any purchase, signing, transfer, spending, entitlement creation, or paid execution. Required sequence: provider.describe -> offers.list -> requirements.check -> cost.estimate -> result.preview -> execution.preflight -> HUMAN AUTHORIZATION -> payment/entitlement -> execution -> receipt. These instructions are guidance only. Existing server-side authorization, payment, entitlement, receipt, replay, idempotency, and receiver-only controls remain authoritative.

Known tools 12

provider.describe

FREE read-only provider and commerce policy discovery.

Inferred read-only
offers.list

FREE read-only public offer and capability discovery.

Inferred read-only
requirements.check

FREE read-only requirements check.

Inferred read-only
cost.estimate

FREE read-only cost estimate.

Inferred read-only
result.preview

FREE read-only result-shape preview.

Inferred read-only
execution.preflight

FREE read-only execution preflight.

Inferred read-only
x402.compatibility_audit

PAID $1.

Inferred read-only
mcp.schema_audit

PAID $1.

Inferred read-only
openapi.quality_audit

PAID $1.

Inferred read-only
machine_commerce.readiness_audit

PAID $2.

Inferred read-only
artifact.integrity_manifest

PAID $0.

Inferred read-only
xkey.validate

PAID prepaid-credit XKEY intake validation.

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

.mcp.json

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

Settings → Connectors → Add custom connector

Name: crossingkey-mcp
Remote MCP URL: https://mcp.crossingkeyintelligence.com/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": {
    "crossingkey-mcp": {
      "url": "https://mcp.crossingkeyintelligence.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

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

Client-specific MCP configuration

{
  "name": "crossingkey-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.crossingkeyintelligence.com/mcp"
}
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 crossingkeyintelligence.com was fetched 2026-10-01T23:36:31.259Z.

Trust status Neutral

crossingkeyintelligence.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.