Satring

What toadlyBroodle/satring MCP server does

toadlyBroodle/satring MCP server connects agent workflows with Satring, a curated directory of APIs that accept machine-oriented payments. The directory covers three payment approaches: L402 using Bitcoin Lightning, x402 using USDC on Base, and MPP using Stripe or Tempo. Services can advertise more than one protocol, and searches can match any constituent protocol in a multi-protocol listing.

The project supports discovery rather than acting as a general payment wallet or API gateway. Agents and developers can browse services, search by text, inspect service details, review ratings, and list available categories. Listings also include operational information such as status and, where available, health and reputation data.

How it works

Satring exposes a JSON API under /api/v1. Public routes include paginated service listings, text search, individual service details, ratings, and category data. Query parameters allow callers to narrow results by category, status, and protocol.

The API limits free access to 10 results per IP each day and applies a rate limit of six requests per minute, with a burst of five. Premium routes return payment challenges when called without authorization. These routes include bulk service export, directory analytics, per-service health analytics, and reputation information. Payment can be completed using L402, MPP, or x402 credentials, depending on the configured challenge.

Setup and configuration

The repository README describes running the underlying application locally with Python. The documented sequence creates a virtual environment, installs requirements.txt, copies .env.example to .env, and starts the application with Uvicorn at http://localhost:8000.

Payment settings can be configured in .env. For local testing, setting AUTH_ROOT_KEY=test-mode bypasses payment gates. The material does not provide a complete list of production environment variables or describe a packaged MCP-specific launch command, so deployment details beyond the Python application startup are not established here.

Tools and capabilities

• Search and filter directory services by text, category, status, or protocol.
• Retrieve service records, ratings, and category identifiers.
• Inspect bulk directory data through a payment-gated endpoint.
• Query directory-wide analytics, including health, pricing, growth, and route information.
• Review service-level uptime, latency, probe history, rating trends, and reputation data.
• Submit or edit service listings when the required payment authorization or edit token is available.
• Recover edit access by placing a verification challenge at a service domain.

Limitations and notes

toadlyBroodle/satring MCP server depends on Satring's directory and its payment flows; it does not make listed APIs free to use. Paid operations require compatible L402, MPP, or x402 payment credentials, and free access is quota-limited. Editing uses service-specific or shared domain edit tokens, while lost tokens require domain verification through .well-known/satring-verify.

The supplied material does not identify supported MCP desktop clients, a software license, or a standalone package name for installing this project. It also does not document the exact MCP tool names exposed by the /mcp source path.