BlinkCodes MCP server
Which servers in the official MCP registry are BlinkCodes's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namecom.blinkcodes/catalogverified in the MCP registry
The registry name sits under blinkcodes.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools3
- Server calls itselfblinkcodes-catalog
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 148 ms.
search_catalogSearch the store catalog of gift cards, service top-ups and eSIM data plans. Returns matching products with their price, availability and product page URL.
get_productGet one catalog product by id: available denominations with prices, required order inputs, and any countries where the code cannot be redeemed.
buy_productBuy a gift card, service top-up or travel eSIM and receive the delivery. Paid in USDC on Base (x402), no account and no browser. Call it twice: first with the order arguments to get payment requirements and an order_id (nothing is…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"catalog": {
"type": "http",
"url": "https://blinkcodes.com/mcp"
}
}
}OpenAPI spec
12 paths, read 2026-10-19. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.