WinCC V8 MCP Server (vogler75/winccv8-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 45 tools. No publisher has claimed this listing.

D
Caution
56/100

WinCC V8 MCP Server

MCP server providing access to Siemens WinCC V8 SCADA systems via REST API, enabling tag management, alarm logging, and archive operations.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

vogler75

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: WINCC_BEARER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes45 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

login-user

Logs a user in to WinCC using username and password. Stores the session credentials for subsequent requests. It is optional, because the MCP server could be started in the way that it is doing automatically a logon with the service account.

wincc-get-connections

Reads configuration data of all connections in Tag Management. Base URL: /tagManagement. Endpoint: Connections. According to WinCC REST docs, returns connections created below communication drivers; supports paging via itemLimit and continuationPoint.

wincc-get-connection

Read configuration data of a specific connection

wincc-get-groups

Read configuration data of all tag groups

wincc-get-group

Read configuration data of a specific tag group

wincc-get-structure-types

Read configuration data of all structure types

wincc-get-structure-type

Read configuration data of a specific structure type

wincc-get-structure-variables

Read instances of structure types

wincc-get-tag-value

Read runtime value of a specific tag

wincc-get-tag-values

Read runtime values of multiple tags

wincc-write-tag-value

Write a value to a specific tag

wincc-write-tag-values

Write values to multiple tags

wincc-get-tag-config

Read configuration data of a specific tag

wincc-get-tags-config

Read configuration data of all tags

wincc-get-archives

Read configuration data of all process value archives

wincc-get-archive

Read configuration data of a specific process value archive

wincc-get-archive-variable

Read configuration data of a specific archive variable

wincc-get-archive-variables

Read configuration data of all variables in an archive

wincc-get-archive-value

Read runtime value of an archive variable

wincc-get-archive-values

Read runtime values of multiple archive variables

wincc-get-timers

Read configuration data of all archive system timers

wincc-get-timer

Read configuration data of a specific archive system timer

wincc-get-archive-tag

Read configuration data of an archive system tag

wincc-get-archive-tags

Read configuration data of all archive system tags

wincc-get-alarm-message-classes

Lists message classes. GET /alarmLogging/MessageClasses with optional paging (itemLimit, continuationPoint). Use Accept-Language for response language and Content-Language for name resolution.

wincc-get-alarm-message-class

Reads a message class. GET /alarmLogging/MessageClass/{messageClassName}. Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-message-types

Lists message types. GET /alarmLogging/MessageTypes with optional paging (itemLimit, continuationPoint). Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-message-type

Reads a message type. GET /alarmLogging/MessageType/{messageTypeName}. Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-message-blocks

Lists message blocks. GET /alarmLogging/MessageBlocks with optional paging (itemLimit, continuationPoint). Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-message-block

Reads a message block. GET /alarmLogging/MessageBlock/{messageBlockName}. Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-messages

Lists messages. GET /alarmLogging/Messages with optional paging (itemLimit, continuationPoint). Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-message

Reads a message. GET /alarmLogging/Message/{messageNumber}. Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-limit-values

Lists limit values. GET /alarmLogging/LimitValues with optional paging (itemLimit, continuationPoint). Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-limit-value

Reads limit values for a tag. GET /alarmLogging/LimitValue/{tagName}. Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-message-groups

Lists message groups. GET /alarmLogging/MessageGroups with optional paging (itemLimit, continuationPoint). Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-message-group

Reads a message group. GET /alarmLogging/MessageGroup/{messageGroupName}. Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-rest-filters

Lists configured REST filters. GET /alarmLogging/RestFilters. Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-rest-filter

Reads a REST filter. GET /alarmLogging/RestFilter/{filterName}. Use Accept-Language for response language and Content-Language for identifier resolution.

wincc-get-alarm-message-list

MessageList

wincc-get-alarm-short-term-archive

ShortTermArchive

wincc-get-alarm-long-term-archive

LongTermArchive

wincc-get-alarm-hit-list

HitList

wincc-get-alarm-lock-list

LockList

wincc-get-alarm-hide-list

Hidelist

wincc-get-alarm-hidden-message-list

HiddenMessageList

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.13.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.13.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.13.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configWINCC_ALLOW_ORIGINCORS Configuration: Use to restrict allowed origins in production
🔐 secretWINCC_BEARER_TOKEN
configWINCC_PWD
configWINCC_SKIP_CERTIFICATE_VALIDATION
configWINCC_URL
configWINCC_USR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

45/45 tools missing one or more hints — login-user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wincc-get-connections (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wincc-get-connection (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +42 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

1 secret value sent to log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.13.1 (high), @modelcontextprotocol/sdk@1.13.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/6 production deps stale: node-fetch@2023-11-30 (2.8y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/vogler75/winccv8-mcp-server?variant=verified)](https://m8ven.ai/mcp/vogler75/winccv8-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b8d667b981ad74ceb7a707f4f68e5ab51101c444
code hash: a4656877f653648511853229b772222773a81d5cf0624ed9498c3008e9344699
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client