SMARD Energy Prices (x402)
RemoteAbout SMARD Energy Prices (x402)
An MCP server for SMARD DE-LU day-ahead electricity prices at 15-minute resolution. Each call requires a USDC payment on Base.
Key features
- 01Query DE-LU day-ahead prices
- 02Access 15-minute resolution data
- 03HTTP and streamable-http MCP endpoints
- 04Per-call x402 payments
Use cases
- 01Check prices at 15-minute intervals
- 02Retrieve electricity prices from an MCP client
MCP support
Its streamable-http MCP endpoint provides SMARD DE-LU day-ahead prices to clients. Calls require per-request USDC payment.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://smard-energy-prices-x402.favo.workers.dev/mcpclaude mcp add --transport http moldy93-smard-x402 https://smard-energy-prices-x402.favo.workers.dev/mcp{"mcpServers":{"moldy93-smard-x402":{"type":"http","url":"https://smard-energy-prices-x402.favo.workers.dev/mcp"}}}Open in Cursor{"servers":{"moldy93-smard-x402":{"type":"http","url":"https://smard-energy-prices-x402.favo.workers.dev/mcp"}}}Open in VS Code{"mcpServers":{"moldy93-smard-x402":{"type":"http","url":"https://smard-energy-prices-x402.favo.workers.dev/mcp"}}}{"mcpServers":{"moldy93-smard-x402":{"serverUrl":"https://smard-energy-prices-x402.favo.workers.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
1| Parameter | Type | Required | Description |
|---|---|---|---|
| region | string | No | |
| seriesId | string | No |
Details
From the project READMESMARD Energy Prices (x402)
Paywalled SMARD day‑ahead electricity prices (DE‑LU, 15‑minute resolution) via x402 on Base mainnet. Hosted MCP (streamable‑http) + HTTP endpoint.
Homepage
https://smard-energy-prices-x402.favo.workers.dev
Endpoints
- HTTP:
GET https://smard-energy-prices-x402.favo.workers.dev/prices - MCP:
POST https://smard-energy-prices-x402.favo.workers.dev/mcp
Pricing
$0.001 per call (USDC on Base). Requires X-PAYMENT header (exact scheme).
MCP Connect (example)
{
"mcpServers": {
"smard-x402": {
"url": "https://smard-energy-prices-x402.favo.workers.dev/mcp",
"headers": {
"Accept": "application/json, text/event-stream"
}
}
}
}
Node.js Example (x402)
import { createWalletClient, http } from "viem";
import { base } from "viem/chains";
import { privateKeyToAccount } from "viem/accounts";
import { createPaymentHeader, selectPaymentRequirements } from "x402/client";
const url = "https://smard-energy-prices-x402.favo.workers.dev/prices";
// 1) Get payment requirements
const res = await fetch(url);
const data = await res.json();
const req = selectPaymentRequirements(data.accepts, "base", "exact");
// 2) Create payment header
const account = privateKeyToAccount(process.env.PRIVATE_KEY);
const client = createWalletClient({ account, chain: base, transport: http("https://mainnet.base.org") });
const xPayment = await createPaymentHeader(client, data.x402Version, req);
// 3) Call API with payment
const paid = await fetch(url, { headers: { "X-PAYMENT": xPayment } });
console.log(await paid.json());
Notes
- MCP endpoint uses streamable‑http. Send
Accept: application/json, text/event-stream. - Data source: SMARD (DE‑LU), 15‑minute resolution.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.