Netzhandwerker EU Power Dispatch API

de.netzhandwerker.energyPublished by energy.netzhandwerker.deOfficial publisherv3.0.0Updated Oct 24, 2026

EU power dispatch for wallet-enabled compute, DePIN, battery and trading agents.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFinance

Overview

AI-generated overview

Remote MCP endpoint offering EU power dispatch data and actions for wallet-enabled compute, DePIN, battery and trading agents.

What you can do
  • The listing gives no tool list, so capabilities can only be inferred from its one-line description.
  • It is positioned as an EU power dispatch service for agents that manage energy.
  • Intended users named are wallet-enabled compute, DePIN, battery and trading agents.
  • No further detail on data sources, regions or operations is published.
When to use it
Consider it only if you are building or running an agent that needs EU electricity dispatch context, such as battery scheduling, DePIN compute or energy trading workflows, and you are willing to evaluate an undocumented endpoint.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. No authentication, environment variables or headers are declared, and no packages are listed.
Before you install
The description mentions wallet-enabled agents, so expect wallet or payment-related interactions, though no credential requirements are documented. No tool list, README or instructions are published, so what the server reads or changes is unknown; verify before connecting anything that holds funds or controls real energy assets.

Installation

In SourceWeft

  1. Open Netzhandwerker EU Power Dispatch API 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/de.netzhandwerker.energy%2Fresearch-hub/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": {
    "netzhandwerker-eu-power-dispatch-api": {
      "type": "http",
      "url": "https://energy.netzhandwerker.de/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v3.0.0LatestSep 16, 2026

Score

17% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.