X402 Express

io.github.ihen404Published by GitHub account ihen404v1.0.0Updated Oct 25, 2026

Express.js HTTP 402 payment middleware for AI agent micropayments

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

An MCP server exposing Express.js HTTP 402 payment middleware for AI agent micropayments.

What you can do
The listing provides no tool list, instructions or README, so capabilities cannot be confirmed beyond the stated purpose: Express.js HTTP 402 payment middleware for AI agent micropayments. It appears intended to let an assistant work with payment-gated HTTP endpoints in an Express.js setup. Treat the exact operations as undocumented until verified.
When to use it
Only consider it if you are building or testing Express.js services that charge AI agents per request through HTTP 402 micropayments and want an assistant involved in that workflow. Most users have no reason to add it.
Requirements
Runs as a local process on the user's machine (stdio transport). No packages, environment variables, headers or authentication are declared, so the actual runtime and setup requirements are undocumented.
Before you install
Payment middleware implies handling of payment credentials and real or test funds; the listing declares no authentication and no configuration details, so review the source before connecting it to anything that can spend money. Actions that gate or charge requests may change service behavior.

Installation

In SourceWeft

  1. Open X402 Express 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 has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 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.