Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read-only catalog of gift cards, service top-ups and travel eSIMs sold by BlinkCodes.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://blinkcodes.com/mcpRun this in your terminal
claude mcp add --transport http catalog https://blinkcodes.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"catalog": {
"url": "https://blinkcodes.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"catalog": {
"type": "http",
"url": "https://blinkcodes.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://blinkcodes.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain blinkcodes.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
| Interface | Endpoint | Spec |
|---|---|---|
| MCP (catalog + buy) | https://blinkcodes.com/mcp | Streamable HTTP, protocol 2025-06-18 |
| A2A | https://blinkcodes.com/a2a | JSON-RPC, protocol 0.3 |
| x402 (pay per call) | https://blinkcodes.com/api/v1/buy | x402 v2 (v1 on request), USDC on Base |
| OpenAPI | https://blinkcodes.com/openapi.json | includes x-payment-info (MPP) |
| Plain-language docs for agents | https://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.
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:
| Tool | Purpose |
|---|---|
search_catalog | Search gift cards, top-ups and eSIM plans. Returns price, availability and product URL. |
get_product | One product by id: denominations with prices, required order inputs, countries where the code cannot be redeemed. |
buy_product | Buy 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:
{
"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:
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.
Payment is USDC on Base over x402. One endpoint, two passes:
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).PAYMENT-SIGNATURE header → 200 with the code, or 202 + status_url if fulfilment outlives the sync window.// the body, in both passes
{ "email": "buyer@example.com", "product_type": "giftcard", // giftcard | topup | esim | phone_rental "product_id": 187, "item_id": 1195, "quantity": 1 }
eip155:8453, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC).X-PAYMENT, or ask for a v1 quote with X-PAYMENT-VERSION: 1.GET /api/v1 describes the rail for free./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.
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.
Store, prices and terms: https://blinkcodes.com. Support: .
MIT — applies to the documentation and examples in this repository. The service itself is governed by the terms published on the site.