OPX

dev.opx-statusv0.1.0Updated Oct 4, 2026

Buyer-side machine commerce: choose where to spend using recent paid x402 provider evidence.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant pick where to spend by consulting recent paid x402 provider evidence.

What it does
OPX is a remote MCP endpoint for buyer-side machine commerce. According to its registry description, it helps an assistant choose where to spend using recent paid x402 provider evidence. No tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to decide between paid x402 providers and should base that choice on recent payment evidence. It is not useful if you do not work with x402 payments or provider selection.
Requirements
A remote streamable HTTP endpoint at the provider's host; no packages, environment variables, or headers are declared. The manifest declares no authentication, and no account or API key is documented.
Before you install
The description concerns spending decisions and paid provider evidence, so any actual payment or spending action should be reviewed before use. The manifest declares no authentication, so verify who can reach the endpoint and what data it returns. No tool list is published, so confirm its behavior before relying on it.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "opx": {
      "type": "http",
      "url": "https://opx-status.dev/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.0LatestOct 4, 2026