MCP Server
Connect GetCurrentOffer to Claude and other AI assistants. No account, no API key.
Endpoint
A remote Model Context Protocol server over the Streamable HTTP transport. One endpoint, JSON-RPC 2.0 over POST:
https://getcurrentoffers.com/mcpAdd it to Claude, or any MCP-aware client, as a remote server:
{
"mcpServers": {
"getcurrentoffer": {
"url": "https://getcurrentoffers.com/mcp"
}
}
}Tools
| Tool | Arguments | Returns |
|---|---|---|
| search_offers | store (required), spend (optional) | Every card offer, cashback portal rate and wallet offer tracked for a store, ranked by estimated dollars back at the purchase amount. Returns up to 3 matching stores and 8 offers each. |
| list_programs | — | Every offer program covered — card issuer programs, cashback portals and wallet offers — and how each one is redeemed. |
curl -X POST https://getcurrentoffers.com/mcp \
-H 'Content-Type: application/json' \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_offers",
"arguments": { "store": "Nike", "spend": 200 }
}
}'How to read the results
- Estimates, not promises.
estimated_savingsis dollars back atspend_used, the purchase amount passed in — or the largest stated minimum, floored at $100, when none was given. - A null is not a zero.
estimated_savings: nullmeans the reward cannot honestly be valued in dollars — points, miles and “up to” rates. Those are never ranked best. - Card and wallet offers are targeted. A listing means the offer exists, not that it is in your account. Confirm it in the issuer’s app and activate it before you pay.
- Public catalog only. Offers synced from your own card accounts need a signed-in session and are never served here.
Limits
- No authentication. 60 requests per minute per IP.
- Read-only: no tool changes anything.
- Search-shaped, one store at a time. For bulk access, pagination and filtering across the whole catalog, use the REST API.
Supported methods
initialize, ping, tools/list, tools/call and notifications/initialized, at protocol version 2025-06-18. Resources, prompts and server-initiated streams are not implemented; GET returns 405.