BlinkCodes catalog

com.blinkcodesPublished by blinkcodes.comOfficial publisherv0.1.1Updated Oct 24, 2026

Read-only catalog of gift cards, service top-ups and travel eSIMs sold by BlinkCodes.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote BlinkCodes MCP server that lets an assistant search a catalog of gift cards, service top-ups and travel eSIMs, inspect products, and buy them with USDC.

What you can do
Search the store catalog for gift cards, top-ups and eSIM plans, with price, availability and product URL returned per match. Look up a single product by id to see denominations with prices, required order inputs and countries where the code cannot be redeemed. Buy a product and receive the delivery, paid in USDC on Base over x402 in two calls: the first returns payment requirements and an order id without charging, the second submits the signed payment payload and returns the code.
When to use it
Useful when an assistant needs to find or compare gift cards, service top-ups or travel eSIM plans, or complete a purchase of one on the user's behalf without an account or browser. The two catalog tools are free and read-only, so they can be added for browsing alone.
Requirements
A remote MCP client that speaks Streamable HTTP, pointed at the hosted endpoint; nothing to install. The catalog tools need no key, account or payment. Buying needs a Base wallet able to sign x402 USDC payments, and an email address for delivery. A stdio-only client can use the documented Docker bridge.
Before you install
The buy tool spends real money in USDC on Base and delivers codes by email, so purchases are irreversible once settled. A wallet signing key is used to authorize payment. The first buy call creates an order but charges nothing; only the second, with the signed payload, settles. Product codes may be unusable in some countries, which the product lookup reports.

Installation

In SourceWeft

  1. Open BlinkCodes catalog in the dashboard and add it to a workspace.
  2. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.blinkcodes%2Fcatalog/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "blinkcodes-catalog": {
      "type": "http",
      "url": "https://blinkcodes.com/mcp"
    }
  }
}

README

BlinkCodes agent interfaces

[blinkcodes-agent-interfaces MCP server] [smithery badge]

Machine-readable interfaces for blinkcodes.com — a store selling gift card codes, service top-ups and travel eSIMs, with delivery by email in seconds.

Everything here is a remote, hosted service. There is nothing to install and no server to run: point your client at the URLs below. This repository exists to document those endpoints, pin their schemas, and give working examples.

InterfaceEndpointSpec
MCP (catalog + buy)https://blinkcodes.com/mcpStreamable HTTP, protocol 2025-06-18
A2Ahttps://blinkcodes.com/a2aJSON-RPC, protocol 0.3
x402 (pay per call)https://blinkcodes.com/api/v1/buyx402 v2 (v1 on request), USDC on Base
OpenAPIhttps://blinkcodes.com/openapi.jsonincludes x-payment-info (MPP)
Plain-language docs for agentshttps://blinkcodes.com/llms.txt

Discovery documents: /.well-known/agent-card.json, /.well-known/mcp/server-card.json, /.well-known/api-catalog, /.well-known/agent-skills/index.json, /.well-known/acp.json, /.well-known/ucp.

MCP server

Published to the Official MCP Registry as com.blinkcodes/catalog (server.json).

Three tools. The two catalog tools are read-only and free — no key, no account, no payment. The third takes money, and only over x402:

ToolPurpose
search_catalogSearch gift cards, top-ups and eSIM plans. Returns price, availability and product URL.
get_productOne product by id: denominations with prices, required order inputs, countries where the code cannot be redeemed.
buy_productBuy and receive the delivery. Two calls: arguments in → x402 payment requirements out; signed payload in → the code out.

buy_product runs the same rail as POST /api/v1/buy below — verify, reserve, settle, fulfil, in that order — so an agent that found the store through MCP never has to change protocol to complete the purchase. Nothing is charged by the first call, and no wallet is needed to use the other two tools.

Add it to a client that speaks remote MCP:

json
{  "mcpServers": {    "blinkcodes": {      "type": "http",      "url": "https://blinkcodes.com/mcp"    }  }}

Full tool schemas and a curl transcript: docs/mcp.md.

A stdio-only client can use the bridge in Dockerfile, which proxies to the same hosted endpoint:

sh
docker build -t blinkcodes-mcp . && docker run -i --rm blinkcodes-mcp

Prefer the direct URL above wherever your client speaks remote MCP — the bridge adds a hop and buys nothing.

Buying, for agents

Payment is USDC on Base over x402. One endpoint, two passes:

  1. POST /api/v1/buy with the order body → 402 carrying payment requirements priced for that exact item, plus an order block (id, access token, status URL).
  2. The identical request with a PAYMENT-SIGNATURE header → 200 with the code, or 202 + status_url if fulfilment outlives the sync window.
jsonc
// the body, in both passes{  "email": "[email protected]",  "product_type": "giftcard",   // giftcard | topup | esim | phone_rental  "product_id": 187,  "item_id": 1195,  "quantity": 1}
  • Network eip155:8453, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC).
  • x402 v2 by default; v1 clients send X-PAYMENT, or ask for a v1 quote with X-PAYMENT-VERSION: 1.
  • GET /api/v1 describes the rail for free.
  • Calling /api/v1/buy with nothing named answers 402 quoting the rail's floor and creates no order — that is the probe form, safe for crawlers.

Worked example: examples/x402-buy.mjs. Rails, floors and payable coin pairs: GET /api/public/payment-methods.

A2A

Agent card at /.well-known/agent-card.json, JSON-RPC message/send at https://blinkcodes.com/a2a. Skills are the two catalog tools plus buy_product, which over this transport carries the a2a-x402 payments extension (https://github.com/google-a2a/a2a-x402/v0.1, declared required: false because the catalog skills are free).

Quote → Task in input-required with x402.payment.required; pay → same taskId with x402.payment.payload → Task completed plus the delivery as an artifact. See examples/a2a.sh.

Human docs

Store, prices and terms: https://blinkcodes.com. Support: [email protected].

License

MIT — applies to the documentation and examples in this repository. The service itself is governed by the terms published on the site.

Source: README.md at commit 6ea47f4

Tools

3

search_catalog

Search the store catalog of gift cards, service top-ups and eSIM data plans. Returns matching products with their price, availability and product page URL.

Parameterstypelimitquerycountry

get_product

Get one catalog product by id: available denominations with prices, required order inputs, and any countries where the code cannot be redeemed.

Parametersidrequired

buy_product

Buy 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 charged), then with that order_id plus the signed x402 payment payload to settle and receive the code.

Parametersemailamountitem_idorder_idquantityproduct_idproduct_typeaccount_numberpayment_payload

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts