MCP.so
ログイン

Cortex402 MCP Server

@Ooak21

基本情報

カテゴリ

その他

トランスポート

stdio

作者

Ooak21

投稿者

Luis Ocadiz

Cortex402 MCP Server について

Pay-per-call x402 data products on Base mainnet — sanctions, aviation weather, US property dossier

Cortex402 MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "cortex402": {
      "command": "npx",
      "args": [
        "-y",
        "cortex402-mcp"
      ],
      "env": {
        "CORTEX402_WALLET_PRIVATE_KEY": "0x..."
      }
    }
  }
}

Cortex402 MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Cortex402?

Cortex402 is a pay‑per‑call data product server on Base mainnet that uses the x402 protocol. It exposes three endpoints (sanctions_screen, aviation_weather, and property_dossier) with payments settled in USDC via the Coinbase CDP facilitator.

How to use Cortex402?

Call the available tools (sanctions_screen, aviation_weather, property_dossier) through the x402 protocol on Base mainnet. Each invocation charges a fixed USDC amount as specified in the endpoint list.

Key features of Cortex402

  • Three pay‑per‑call data endpoints on Base mainnet
  • Payments settle in USDC via Coinbase CDP facilitator
  • Sanctions screening endpoint ($0.50 per call)
  • Aviation weather endpoint ($0.10 per call)
  • Property dossier endpoint ($2.00, currently in development)

Use cases of Cortex402

  • Screen entities or individuals against sanctions lists.
  • Retrieve real‑time aviation weather data for flight planning.
  • Request property‑related information (in development).

よくある質問

1

What protocol does Cortex402 use?

Cortex402 uses the x402 protocol on Base mainnet.

2

How are payments handled?

Payments are settled in USDC through the Coinbase CDP facilitator.

3

What endpoints are currently available?

The available endpoints are sanctions_screen ($0.50), aviation_weather ($0.10), and property_dossier ($2.00, in development).

4

Is the property_dossier endpoint fully operational?

No, it is listed as “in development.”

コメント

「その他」の他のコンテンツ