mcpField
S
SMARD Energy Prices (x402)

SMARD Energy Prices (x402)

Remote
smard-energy-prices-x402.favo.workers.devFinance0Updated 38w ago

About 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

  1. 01Query DE-LU day-ahead prices
  2. 02Access 15-minute resolution data
  3. 03HTTP and streamable-http MCP endpoints
  4. 04Per-call x402 payments

Use cases

  1. 01Check prices at 15-minute intervals
  2. 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.

Endpointhttps://smard-energy-prices-x402.favo.workers.dev/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

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
ParameterTypeRequiredDescription
regionstringNo
seriesIdstringNo

Details

From the project README

SMARD 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

Markdown supported

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.