ToolsMCP
Cleared
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- clearedpay.xyz
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 0.1.0 · updated
- Official links
Publisher’s description
USDC invoicing on Base: send invoices, share pay links, track payments and customers.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.0, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- clearedpay.xyz
- Version observed
- 0.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/xyz.clearedpay%2Fcleared/versions/0.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Create invoices and handle payments | Publisher description mentions “invoicing”, “invoices”, “payments”, “send”. | No connection check or task run. Capability is as described by the publisher. | Rule payments-invoices matched: “invoicing”, “invoices”, “payments”, “send”. Rule payments-invoices. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://api.clearedpay.xyz/mcp(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
xyz.clearedpay/cleared
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.