How do I install CrossingKey MCP?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does CrossingKey MCP need an API key?

No required environment variable is listed on this record.

What transport does CrossingKey MCP use?

CrossingKey MCP is reached over HTTP.

CrossingKey MCP server

Q: When was CrossingKey MCP last checked?

Last checked 2026-11-08. Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mcp.crossingkeyintelligence.com/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http com.crossingkeyintelligence-crossingkey-mcp https://mcp.crossingkeyintelligence.com/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "com.crossingkeyintelligence-crossingkey-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.crossingkeyintelligence.com/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 3.0.1
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

CrossingKey MCP

Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.

Production

Endpoint

https://mcp.crossingkeyintelligence.com/mcp

Canonical identity

com.crossingkeyintelligence/crossingkey-mcp

Published source release

3.0.1 (historical production baseline)

Current local release candidate

4.0.0-rc.1

Current production release

v3.0.1 (unchanged; the v4 candidate is not deployed)

The v4.0.0-rc.1 source candidate is prepared and tested in the isolated development worktree. Source preparation does not imply production deployment.

Source publication does not imply production deployment.

Transport

MCP Streamable HTTP

CrossingKey MCP v4.0.0-rc.1 candidate

CrossingKey MCP is a governed machine-commerce interface for AI agents and authorized software clients.

The candidate preserves the existing anonymous MCP surface and adds the two authorized v4 paid audits. The exact live/public tool count remains a deployment-time verification item.

7 free discovery and commercial-navigation tools
8 public marketplace tools
13 direct x402 paid tools plus a separately named legacy credit-redemption compatibility tool for existing customers

Authenticated sessions additionally expose verification and role-gated marketplace operations.

The operating principle is:

Discovery is free. Evaluation is safe. Payment is explicit. Authority stays bounded. Execution is deterministic. Fulfillment is verifiable.

Free discovery

These seven tools can be used anonymously to understand the provider, available offers, requirements, price, expected result, authorization state, and prepaid-credit options without spending money:

provider.describe
offers.list
requirements.check
cost.estimate
result.preview
execution.preflight
credits.options (legacy compatibility status; new credit sales are disabled)

The normal discovery sequence is:

provider.describe
→ offers.list
→ requirements.check
→ cost.estimate
→ result.preview
→ execution.preflight
→ credits.options (legacy compatibility status; new credit sales are disabled)

A valid commercial flow may reach:

READY_FOR_HUMAN_AUTHORIZATION

and then stop at:

STOPPED_BEFORE_PAYMENT

until the required buyer authorization and payment conditions are satisfied.

Public marketplace discovery

The preserved anonymous marketplace surface also exposes:

marketplace.describe
provider.register
provider.get
capability.get
capability.search
catalog.list
commerce.quote
creator.apply

Discovery, catalog browsing, capability inspection, and quoting do not themselves authorize paid execution.

provider.register and creator.apply are public write surfaces for application and intake workflows. They do not grant unrestricted commercial authority.

Paid and gated execution

These 13 tools perform valuable computation, validation, or artifact generation and use direct x402 payment:

x402.compatibility_audit
mcp.schema_audit
openapi.quality_audit
machine_commerce.readiness_audit
artifact.integrity_manifest
xkey.validate

Current v4 paid capabilities use exact x402 Base USDC payments. Historical prepaid credit balances remain redeemable only through the separately named legacy compatibility path; v4 does not sell new credit packs.

Free discovery does not consume paid execution credits.

Authenticated verification

Authenticated sessions can expose read-only verification tools including:

approval.verify
idempotency.inspect
receipt.verify
entitlement.inspect

Marketplace sessions may additionally expose role-gated job, receipt, purchase, provider, capability, and settlement operations.

Approval minting remains a local operator action and is not exposed over MCP.

Commercial flow

The governed machine-commerce path is:

discover
→ inspect requirements
→ estimate cost
→ preview result
→ preflight
→ authorize
→ pay
→ verify settlement
→ execute
→ issue result
→ bind entitlement
→ issue verifiable receipt

Payment alone does not create unrestricted authority.

Authorization, payment verification, execution, fulfillment, entitlement creation, and receipt generation remain separate governed stages.

Human authorization

CrossingKey does not treat an LLM-supplied boolean such as approved: true as buyer authorization.

Where human authorization is required, approval is bound to the relevant commercial context, including the buyer, capability, inputs, quote, idempotency state, and expiration conditions.

Paid execution does not occur merely because an agent asks for it.

MCP resources

The candidate preserves the public MCP resources for agent comprehension:

crossingkey://discovery-guide
crossingkey://commerce-policy
crossingkey://capability/{name}

These describe the free discovery sequence, commerce policy, and per-capability instructions.

Machine commerce

CrossingKey supports governed machine-payment infrastructure including:

x402 v1
x402 v2
Base USDC
historical prepaid request credits through a separately named compatibility path only
settlement verification
entitlements
result-bound receipts
idempotent execution
replay protection

The CrossingKey seller wallet boundary is receiver-only.

Agents are not granted unrestricted wallet signing, sending, swapping, bridging, or autonomous seller-spend authority.

Security properties

The production design includes:

bounded input validation
strict capability schemas
SSRF protections
DNS and address validation
response-size controls
authorization boundaries
approval binding
idempotency protection
payment replay protection
duplicate-settlement protection
deterministic result hashing
entitlement binding
receipt verification
receiver-only seller wallet policy
explicit uncertain-settlement handling

No private keys, wallet secrets, Stripe secrets, API keys, seed phrases, mnemonics, or private customer information belong in this repository.

Agent discovery

Recommended entry point:

provider.describe

Canonical MCP endpoint:

https://mcp.crossingkeyintelligence.com/mcp

Canonical identity:

com.crossingkeyintelligence/crossingkey-mcp

Official MCP Registry identity:

com.crossingkeyintelligence/crossingkey-mcp

Website:

https://www.crossingkeyintelligence.com

CrossingKey Intelligence

Operating online under the handle crossingkey_.

intelligence is the standard.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install CrossingKey MCP?

Does CrossingKey MCP need an API key?

What transport does CrossingKey MCP use?

When was CrossingKey MCP last checked?

Documentation

CrossingKey MCP

Production

CrossingKey MCP v4.0.0-rc.1 candidate

Free discovery

Public marketplace discovery

Paid and gated execution

Authenticated verification

Commercial flow

Human authorization

MCP resources

Machine commerce

Security properties

Agent discovery

CrossingKey Intelligence