
Base Payment Assurance
io.github.PGhannmmnv0.1.0Updated Oct 7, 2026
Dual-RPC Base USDC payment assurance with safe finality and exact transfer matching.
Overview
AI-generated overview
A remote MCP endpoint that verifies Base USDC payments, checking finality and matching transfers exactly.
- What it does
- Base Payment Assurance is a remote MCP server that provides payment assurance for USDC transfers on the Base network. According to its description, it uses dual RPC sources to confirm safe finality and to match transfers exactly. No individual tools are listed in the manifest, so the specific operations exposed are not documented here.
- When to use it
- Consider it when an assistant needs to confirm that a Base USDC payment has settled and that the transfer details match what was expected. It is aimed at payment verification workflows rather than general blockchain queries.
- Requirements
- A remote streamable HTTP endpoint; no local package or runtime is needed. An Authorization header is declared: an optional Bearer credit token, and it is required for protected assurance tools. Network access to the endpoint is required.
Before you install
The server is remote, so requests and any payment details you submit go to a third-party endpoint. The Authorization header carries a Bearer credit token; treat it as a secret and avoid exposing it. The description mentions credit tokens, which may imply paid usage, but no pricing is stated. No tools are listed, so verify what the server actually does before relying on it for payment decisions.
Installation
In SourceWeft
- Open Base Payment Assurance 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": {
"base-payment-assurance": {
"type": "http",
"url": "https://base-payment-assurance-002.qqqa16521-dce.workers.dev/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.1.0LatestOct 7, 2026
