IoMarkets Topup
Travel eSIMs and mobile top-ups paid in USDC via x402.
Description from the maker (original English)
MCP server exposing AEMET (Spanish weather agency) forecasts, station data and warnings.
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.
AEMET_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"aemet": {
"command": "npx",
"args": [
"-y",
"@mmillan76/aemet-mcp"
],
"env": {
"AEMET_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add aemet --env AEMET_API_KEY=your-value -- npx -y @mmillan76/aemet-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"aemet": {
"command": "npx",
"args": [
"-y",
"@mmillan76/aemet-mcp"
],
"env": {
"AEMET_API_KEY": "your-value"
}
}
}
}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": {
"aemet": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mmillan76/aemet-mcp"
],
"env": {
"AEMET_API_KEY": "your-value"
}
}
}
}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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 9, 2026
The registry name was verified with the GitHub account mmillan76, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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.
You need to fill in: AEMET_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: IoMarkets Topup, Open Transfer Times, CLIO Geo
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Travel eSIMs and mobile top-ups paid in USDC via x402.
Check if a flight connection is comfortable, tight or risky, with cited airport data.
MCP server for rendering GeoJSON vector layers into map images with basemaps
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.
MCP server that exposes public weather data from AEMET (Agencia Estatal de Meteorología, Spain) to AI agents and MCP-compatible clients.
Three tools, well-typed, backed by AEMET's official OpenData API:
No install needed — run it directly with npx:
npx -y @mmillan76/aemet-mcp
The server communicates over stdio, so it's meant to be launched by an MCP client rather than run standalone in a terminal.
The server reads the API key from the AEMET_API_KEY environment variable. It exits with an error at startup if it's missing.
Add to your MCP client config (e.g. claude_desktop_config.json):
{
"mcpServers": { "aemet": { "command": "npx", "args": ["-y", "@mmillan76/aemet-mcp"], "env": { "AEMET_API_KEY": "your-api-key-here" } } } }
Any other MCP client that supports stdio servers works the same way — point it at npx -y @mmillan76/aemet-mcp with AEMET_API_KEY set in the environment.
git clone https://github.com/mmillan76/aemet-mcp.git
cd aemet-mcp npm install cp .env.example .env # fill in AEMET_API_KEY npm run build
Test tool calls interactively with the MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.js
(the Inspector reads AEMET_API_KEY from your shell environment, so export it — or source .env — before running the command above)
AEMET OpenData uses a two-step pattern on every endpoint: the first request returns a JSON envelope with a datos URL, not the actual data; a second request to that URL returns the real payload. This server hides that detail — tools just return the final data. Rate limits apply per API key; if you hit them, the tool returns a clear error instead of retrying silently.
MIT — see LICENSE.