CrossingKey MCP
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
Production
Endpoint
https://mcp.crossingkeyintelligence.com/mcp
Canonical identity
Усильте агента
Собственный URL издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
https://mcp.crossingkeyintelligence.com/mcpКнопка Claude выше открывает Claude с заполненными названием и URL. Подтвердить добавление всё равно нужно там.
claude mcp add --transport http com.crossingkeyintelligence-crossingkey-mcp https://mcp.crossingkeyintelligence.com/mcpRun in a terminal.
{ "mcpServers": { "com.crossingkeyintelligence-crossingkey-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.crossingkeyintelligence.com/mcp" ] } }}claude_desktop_config.json
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
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.
ЗапускОт издателя
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
Endpoint
https://mcp.crossingkeyintelligence.com/mcp
Canonical identity
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
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 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.
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.
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.describeoffers.listrequirements.checkcost.estimateresult.previewexecution.preflightcredits.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.
The preserved anonymous marketplace surface also exposes:
marketplace.describeprovider.registerprovider.getcapability.getcapability.searchcatalog.listcommerce.quotecreator.applyDiscovery, 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.
These 13 tools perform valuable computation, validation, or artifact generation and use direct x402 payment:
x402.compatibility_auditmcp.schema_auditopenapi.quality_auditmachine_commerce.readiness_auditartifact.integrity_manifestxkey.validateCurrent 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 sessions can expose read-only verification tools including:
approval.verifyidempotency.inspectreceipt.verifyentitlement.inspectMarketplace 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.
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.
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.
The candidate preserves the public MCP resources for agent comprehension:
crossingkey://discovery-guidecrossingkey://commerce-policycrossingkey://capability/{name}These describe the free discovery sequence, commerce policy, and per-capability instructions.
CrossingKey supports governed machine-payment infrastructure including:
The CrossingKey seller wallet boundary is receiver-only.
Agents are not granted unrestricted wallet signing, sending, swapping, bridging, or autonomous seller-spend authority.
The production design includes:
No private keys, wallet secrets, Stripe secrets, API keys, seed phrases, mnemonics, or private customer information belong in this repository.
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
Operating online under the handle crossingkey_.
intelligence is the standard.
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
{ "mcpServers": { "com.crossingkeyintelligence-crossingkey-mcp": { "url": "https://mcp.crossingkeyintelligence.com/mcp", "headers": {} } }}Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Скопируйте на этой странице конфигурацию http для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
В этой записи не указано обязательных переменных окружения.
CrossingKey MCP доступен по HTTP.
Последняя проверка: 2026-11-08. Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.