MCP.so
ログイン

x402 Triage MCP

@TateLyman

x402 Triage MCP について

概要はまだありません

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

node

公開者

TateLyman

設定

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

{
  "mcpServers": {
    "x402-triage": {
      "command": "npx",
      "args": [
        "--yes",
        "--package",
        "x402-triage-mcp",
        "x402-triage-mcp"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is x402 Triage MCP?

x402 Triage MCP is a read-only MCP server for performing no-payment x402 surface triage, checking the health of the 402 Index, and handing off to a paid review. It is intended for developers and operators inspecting public x402, MPP, Pay.sh, OpenAPI, manifest, or HTTP 402 endpoints.

How to use x402 Triage MCP?

Install and run directly with npx --yes x402-triage-mcp. Configure it as a stdio MCP client by adding an entry to your mcpServers configuration with the command npx, arguments ["--yes", "--package", "x402-triage-mcp", "x402-triage-mcp"]. The server exposes three tools: triage_x402_surface, watch_402_index, and x402_paid_paths.

Key features of x402 Triage MCP

  • Three MCP tools for triage, index watch, and paid paths.
  • Read‑only; never sends X-PAYMENT, wallet signatures, or credentials.
  • Returns status, payment headers, and challenge summaries.
  • Searches public 402 Index for health and validity signals.
  • Provides static paid review handoff URLs.
  • Checks for safety controls like spend limits and receipt trails.

Use cases of x402 Triage MCP

  • Inspecting a public x402 surface for security and payment readiness.
  • Monitoring the health of 402 Index records for specific domains or protocols.
  • Obtaining links to paid Tate Programs review services (e.g., five‑attack review, fix sprint).
  • Verifying that a target endpoint exposes expected safety controls before enabling live spending.

FAQ from x402 Triage MCP

Can I use x402 Triage MCP on private or tokenized URLs?

No. The server should only be used on public launch surfaces that you own or are authorized to inspect. Do not submit private URLs, tokenized URLs, customer data, or production secrets.

Does x402 Triage MCP require an API key or wallet to function?

No. The tools are read‑only and do not send X-PAYMENT headers, sign wallet messages, or call paid endpoints. No authentication or payment is needed.

What data is sent to Tate Programs when I use the tools?

Only the URL, HTTP method, origin, and query parameters you provide in the tool input. No credentials, private data, or wallet information is transmitted.

What transport does x402 Triage MCP use?

It uses STDIO, configured as a local MCP server in your MCP client. There is no network‑based transport.

Does the server support any authentication or environment variables?

No. The server uses the public Tate Programs triage API without any authentication. Environment variables are not required or supported.

コメント

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