Skip to main content
Glama
deenesjakoruzh
8randonpickart5

x402-buyer-mcp

by 8randonpickart5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

x402-buyer-mcp

x402 경제를 위한 범용 구매자 에이전트.

Claude Desktop, Cursor 및 Claude Code 사용자가 모든 x402 엔드포인트를 자동으로 검색, 결제 및 호출할 수 있게 해주는 MCP 서버입니다. Claude에게 질문하면 USDC로 답변 비용을 지불합니다.

Decixa를 통해 구동되는 검색 기능(5,500개 이상의 검증된 x402 엔드포인트)과 로컬 레지스트리 폴백을 제공합니다.

설치

Claude Desktop / Cursor

MCP 설정에 추가하세요:

{
  "mcpServers": {
    "x402-buyer": {
      "command": "npx",
      "args": ["-y", "x402-buyer-mcp"]
    }
  }
}

요구 사항

  • Node.js 18 이상

  • AgentCash 지갑 설정 및 Base 네트워크의 USDC 충전 완료

Related MCP server: signal402-mcp

도구

도구

설명

x402_discover

x402 엔드포인트 검색 — Decixa의 5,500개 이상의 검증된 API를 로컬 폴백과 함께 쿼리

x402_call

AgentCash를 통한 자동 USDC 결제로 모든 x402 엔드포인트 호출

x402_balance

AgentCash 지갑 잔액 확인

x402_research

다중 엔드포인트 병렬 조사 — 3~5개의 엔드포인트를 동시에 호출

작동 방식

  1. Claude에게 질문합니다 ("stripe.com은 안전한가요?")

  2. x402_discover가 Decixa와 로컬 레지스트리에서 일치하는 엔드포인트를 검색합니다.

  3. x402_call이 AgentCash를 통해 Base 네트워크의 USDC로 엔드포인트 비용을 지불합니다.

  4. 데이터가 반환되면 Claude가 답변을 종합합니다.

로컬 레지스트리에는 프리미엄 소스(VirusTotal, People Data Labs, Hunter.io, AbuseIPDB, Qualys SSL Labs, NIH RxNorm, US Census, ESPN, The Odds API)를 기반으로 하는 8개의 Alderpost 인텔리전스 엔드포인트가 포함되어 있습니다. Decixa는 검색 범위를 전체 x402 생태계로 확장합니다.

검색 아키텍처

기본: Decixa /api/agent/resolve — 5,500개 이상의 검증된 x402 엔드포인트에 대한 의미론적 검색, 지연 시간, 가격, 신뢰 점수 및 기능 일치도에 따라 순위가 지정됩니다.

폴백: 전체 메타데이터를 포함하는 8개의 엄선된 Alderpost 엔드포인트 로컬 레지스트리. Decixa에 연결할 수 없는 경우 자동으로 사용됩니다.

이 "소프트 스왑(soft swap)" 패턴은 네트워크가 다운되어도 검색이 항상 작동함을 의미합니다.

로컬 레지스트리 엔드포인트

엔드포인트

가격

프리미엄 소스

Domain Shield

$0.12

VirusTotal (70개 이상의 엔진)

Company X-Ray

$0.15

People Data Labs, Hunter.io

Threat Pulse

$0.10

VirusTotal, AbuseIPDB

Compliance Check

$0.15

Qualys SSL Labs

Prospect IQ

$0.12

People Data Labs, Hunter.io

Sports Edge

$0.12

ESPN, The Odds API, Claude AI

Property Intel

$0.10

US Census, OpenWeather

Health Signal

$0.10

NIH RxNorm, FDA

변경 로그

v2.0.0

  • Decixa 통합 — 검색 시 Decixa의 /api/agent/resolve API를 기본 소스로 쿼리하며, 로컬 레지스트리를 폴백으로 사용합니다(소프트 스왑 패턴).

  • x402_discover가 Alderpost 엔드포인트뿐만 아니라 전체 x402 생태계의 결과를 반환합니다.

  • 자연어 쿼리를 Decixa의 동사 기반 분류 체계로 매핑하는 기능이 추가되었습니다.

  • 생태계 전반의 검색을 반영하도록 도구 설명이 업데이트되었습니다.

  • Decixa로부터 첫 번째 통합 파트너 크레딧을 받았습니다.

v1.0.5

  • npm bin 항목 및 ESM 모듈 구성 수정.

  • CLI를 루트 cli.js로 이동.

v1.0.0

  • 4개의 도구와 8개의 Alderpost 엔드포인트로 초기 릴리스.

크레딧

  • 검색: Decixa — AI 에이전트를 위한 의사결정 계층

  • 결제: AgentCash — AI 에이전트를 위한 USDC 지갑

  • 인텔리전스: Alderpost — 번들형 인텔리전스 API

링크

라이선스

MIT — Alderpost LLC

Available Tools

4 tools
x402_balanceA

Check your AgentCash USDC wallet balance on Base.

Returns current balance available for x402 payments and approximate number of calls you can afford. No parameters required.

If AgentCash is not set up, provides instructions to create and fund a wallet.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It accurately describes the read-only behavior, the information returned, and the fallback for unset wallets. No contradictions or hidden side effects noted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each providing essential info: purpose, return details, and fallback. No redundancy, perfectly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple balance check tool with no output schema, description covers all needed aspects: what it does, what it returns, and what happens if setup is missing. Context is fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters and schema coverage 100%. Description reiterates no parameters are required, which adds no new info but is consistent. Baseline 4 is appropriate for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies the tool checks the AgentCash USDC wallet balance on Base, detailing what is returned (balance and approximate call count). It clearly distinguishes itself from siblings like x402_call (which likely makes payments) and x402_discover.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states no parameters are needed and mentions setup instructions if missing. It implicitly conveys when to use (when you need balance info), but does not explicitly discuss when not to use or provide alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

x402_callA

Call any x402 paid API endpoint with automatic USDC payment via AgentCash.

Accepts a full URL with query parameters. Handles the complete x402 payment flow:

  1. Sends request → receives 402 payment requirement

  2. Signs USDC payment on Base via AgentCash wallet

  3. Retries with payment proof → returns endpoint data

Requires AgentCash wallet to be set up and funded (https://agentcash.dev).

Examples:

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesFull endpoint URL with query parameters

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Despite no annotations, the description fully discloses the 3-step payment flow, requirements for AgentCash wallet, and retry logic. No contradictions or hidden behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections, bullet-point steps, and examples. Every sentence adds value; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description lacks explicit return value details, but examples imply endpoint data. Overall, it covers purpose, flow, requirements, and usage adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers the 'url' parameter with 100% coverage, and description adds examples and explains it accepts full URLs with query parameters, adding value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it calls x402 paid APIs with automatic USDC payment. It distinguishes from siblings (x402_balance, x402_discover, x402_research) which handle different aspects of the x402 protocol.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides when-to-use context with examples and mentions integration with x402_discover. Lacks explicit when-not-to-use or alternative tools, but context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

x402_discoverA

Search for x402 paid API endpoints that can answer a question or provide data.

Discovery powered by Decixa (5,500+ verified x402 endpoints) with local registry fallback. Searches across the entire x402 ecosystem — not just Alderpost endpoints.

Local registry includes premium endpoints backed by VirusTotal, People Data Labs, Hunter.io, AbuseIPDB, Qualys SSL Labs, NIH RxNorm, US Census Bureau, OpenWeather, The Odds API.

Categories: security, company/business, threat intelligence, sales/leads, compliance, health/drug, property/location, sports, and any x402 capability indexed by Decixa.

Examples:

  • query "domain security" → finds Domain Shield + other x402 security scanners

  • query "company information" → finds Company X-Ray + other enrichment APIs

  • query "verify factual claims" → finds verification endpoints via Decixa

  • query "drug interactions" → finds Health Signal (NIH RxNorm)

Use x402_call to call any discovered endpoint.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesWhat data do you need? E.g. "domain security", "company revenue", "drug interactions", "verify a claim"

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It describes the tool as a read-only search across the ecosystem, mentions the fallback mechanism, and lists categories. No destructive behavior is indicated, and no contradictions are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with bullet points and examples, front-loading the core purpose. While somewhat lengthy, every sentence adds value and the structure aids readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks explicit details about the output format (e.g., what fields are returned). Given no output schema, this is a notable gap. However, the mention of x402_call for calling endpoints implies the tool returns endpoint details, and the examples suggest a list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'query' has a clear description in the schema, and the tool description adds valuable examples and context (e.g., 'domain security' → finds Domain Shield). Schema coverage is 100%, so the description complements the schema well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches for x402 paid API endpoints, specifies the source (Decixa with local fallback), and distinguishes it from siblings like x402_call. Examples illustrate specific queries and expected results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells when to use this tool (for discovery) and explicitly links to x402_call for calling endpoints. It provides query examples but does not explicitly state when not to use it or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

x402_researchA

Run comprehensive research by calling multiple x402 endpoints in parallel.

Given a subject (domain, IP, address, drug name, or sport), this tool:

  1. Detects the input type automatically

  2. Finds all relevant x402 endpoints (local registry)

  3. Calls up to 5 endpoints simultaneously with automatic payment

  4. Returns all results combined for synthesis

This is the fastest way to get a complete intelligence picture on any subject.

Input types (auto-detected):

  • Domain "stripe.com" → calls security + company + threat + compliance + sales (~$0.64)

  • IP "8.8.8.8" → calls threat intelligence (~$0.10)

  • Address "123 Main St Milwaukee WI" → calls property/location (~$0.10)

  • Drug "ibuprofen" → calls health intelligence (~$0.10)

  • Sport "nba" → calls sports intelligence (~$0.12)

Set max_cost to control budget per research call (default: $1.00).

ParametersJSON Schema
NameRequiredDescriptionDefault
subjectYesThe subject to research: domain, IP, address, drug name, or sport
max_costNoMaximum total cost in USD (default: 1.00). Cheapest endpoints called first.

TDQS

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses parallel calling, automatic payment, and cost control via max_cost. However, it omits details like authentication requirements, error handling, rate limits, and potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear main sentence, followed by bullet points and examples. It is concise yet informative, with no redundant sentences. Every part contributes to understanding the tool's functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema or annotations, the description covers the essential aspects: input processing, parallel execution, and cost management. It lacks details on return format and error scenarios, but these are mitigated by the tool's simplicity and the combined results description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage. The description significantly adds value by explaining the subject parameter's auto-detection behavior and providing concrete examples. For max_cost, it clarifies that cheapest endpoints are called first, which is not evident from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: running comprehensive research by calling multiple x402 endpoints in parallel. It specifies the input types (domain, IP, address, drug, sport) and the workflow (auto-detection, endpoint selection, parallel calls). This distinguishes it from siblings like x402_call, which likely calls a single endpoint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context, including when to use (fastest way to get intelligence) and examples for each input type. However, it does not explicitly mention when not to use or compare with sibling tools like x402_call or x402_discover.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updatesv2.0.0
    • First observedx402_balance
    • First observedx402_call
    • First observedx402_discover
    • First observedx402_research
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: checking balance, making a single payment-supported call, discovering endpoints, and running parallel research. No overlap or ambiguity.

Naming Consistency5/5

All tools follow the 'x402_<action>' pattern with consistent lowercase and underscores. The actions are all verbs except 'balance', which is a noun but commonly understood as a verb in API contexts.

Tool Count5/5

Four tools are exactly appropriate for the server's purpose. Each tool is essential and none feel redundant or missing.

Completeness5/5

The tool surface covers the full workflow: discover endpoints, check balance, call an endpoint, and run multi-endpoint research. No obvious gaps for the stated purpose of interacting with x402 APIs.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers