x402-sec-scan

io.github.6mickswagger9Published by GitHub account 6mickswagger9v0.0.3Updated Oct 31, 2026

x402 paid API for AI agents. USDC on Base. CDP facilitator.

The publisher's own server: scan.mx Email Diagnostics

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

Local stdio MCP server exposing an x402 paid API for AI agents, settling payments in USDC on Base through a CDP facilitator.

What you can do
  • The listing gives no tool list, so capabilities are inferred from the short description only.
  • It presents an x402 paid API that AI agents can call.
  • Payments are denominated in USDC on the Base network.
  • Settlement is handled through a CDP facilitator.
When to use it
Only worth considering if you specifically want an assistant to reach an x402-style paid API and you are comfortable with USDC payments on Base. The description is too thin to judge the actual endpoints or value.
Requirements
Runs as a local process over stdio, installed from the npm package x402-sec-scan, so a Node.js runtime is needed. No authentication, environment variables or headers are declared, but a funded USDC wallet on Base and access to a CDP facilitator are implied by the description.
Before you install
The server is described as a paid API, so using it can spend real USDC on Base; review pricing and spending limits before connecting an agent. Wallet or facilitator credentials are not documented here, and no tool list is published, so what it can do and what data it sends to third parties cannot be verified.

Installation

In SourceWeft

  1. Open x402-sec-scan in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not answer in time.

Version history

1
  1. v0.0.3LatestOct 31, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Scan integrations