Settled
tools.settledv0.2.0Updated Oct 3, 2026
Check x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports
Overview
AI-generated overview
Lets an assistant check x402 payment endpoints before paying, including payTo details, paid test purchases, and payee and buyer reports.
- What it does
- Settled is an MCP server for inspecting x402 payment endpoints before an agent commits money. According to its registry description, it surfaces payTo information, can run paid test purchases, and produces payee and buyer reports. It is offered both as a remote endpoint and as a local npm package run with npx.
- When to use it
- Worth adding when an assistant or agent workflow needs to verify an x402 endpoint's payment details or reputation before sending funds. Useful for pre-payment checks and for reviewing payee or buyer history.
- Requirements
- Either a remote endpoint connection or a local Node.js runtime to run the npm package settled-x402 with npx. No authentication is declared. An optional day pass is available via the SETTLED_PASS environment variable or the x-settled-pass header, paid over x402.
Before you install
The optional day pass costs $0.05 over x402 and is supplied through SETTLED_PASS or x-settled-pass; treat that value as a secret. The server is built around paid test purchases, so real money can be spent. Verify what the paid test purchase does before enabling it.
Installation
In SourceWeft
- Open Settled in the dashboard and add it to a workspace.
- 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": {
"settled": {
"type": "http",
"url": "https://settled.tools/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.2.0LatestOct 3, 2026


