Digital Simon Ems

org.umweltsicherheitPublished by umweltsicherheit.orgOfficial publisherv1.0.0Updated Oct 25, 2026

Digital-Simon EMS: Messwerte und Gerätestatus abfragen, Verläufe lesen, mit Freigabe schalten.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureData & Analytics

Overview

AI-generated overview

Remote MCP server for a Digital-Simon EMS that lets an assistant query measurements and device status, read histories, and switch devices with approval.

What you can do
Query current measurements and device status from the energy management system (EMS). Read historical value series and trends. Switch devices, with an approval step required before switching.
When to use it
Useful when an assistant should inspect an energy management system's readings and device states, review past values, or make controlled switching changes that need explicit approval.
Requirements
Remote streamable HTTP endpoint at mcp.umweltsicherheit.org. OAuth authentication is required; no environment variables or headers are declared.
Before you install
Switching devices changes real system state, so confirm each action and rely on the stated approval step. Access is tied to an OAuth account, and measurement and device data are sent to the remote provider.

Installation

In SourceWeft

  1. Open Digital Simon Ems in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/org.umweltsicherheit%2Fdigital-simon-ems/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "digital-simon-ems": {
      "type": "http",
      "url": "https://mcp.umweltsicherheit.org/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 20, 2026

Score

60% 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
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.