Goodquote
Payment rails (x402, ACP, AP2) move the money once there's a number. But how do two agents get to the number without one anchoring or leaking its position? That's the gap I tried to fill.
GoodQuote is a blind price-settlement MCP server. Agent A locks a price + an acceptable margin. Agent B submits a blind offer — it unlocks only if it's within A's range. If it doesn't match, neither side learns anything. When it matches, both get the agreed price (mid-price split) and a confirmation record, then settle however they like.
Remote MCP over Streamable HTTP — one URL, five tools Stateless & private: no accounts, no database, deals auto-erase Auth: OAuth 2.0 (works as a Claude.ai custom connector) or a bearer token for CLI/API Supports partial fulfilment — split a large volume across multiple counter-agents Zero dependencies (plain Node), self-hosted Endpoint: https://goodquote.online/mcp · Overview for agents: https://goodquote.online/agents
Would love feedback from people building multi-agent / commerce workflows — especially on the blind-matching model and where it'd plug into your settlement stack.
Server Config
{
"mcpServers": {
"good-quote": {
"type": "streamable-http",
"url": "https://goodquote.online/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Recommend Servers
View All高德地图官方 MCP Server
summarize chat message