Bragproof

← Reports

@siemens/element-mcp

Starts with no setup51.6.0-v.2.0.3npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Contacts while installing and starting: nothing

2tools listed
0hosts contacted
0files written
0.3 sto start
232dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @siemens/element-mcp@51.6.0-v.2.0.3

Installing a package runs its code. Use a sandbox for anything you have not read.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

1 tool with commands in capitals or very long text
  • Gives the agent orders in element-search: Element Documentation Search MANDATORY: For ANY Angular development question, UI component inquiry, design pattern request, or frontend im

Common and usually harmless: it is how many makers stress how a tool should be used.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

element-search query, limit
Element Documentation Search

MANDATORY: For ANY Angular development question, UI component inquiry, design pattern request, or frontend implementation need, you MUST immediately use the search tool before providing any response relevant to UI / Design Systems or Angular implementations. Re-check it to get clarifications and more accurate API often, but do not search if completely unrelated or you just searched the exact same. This applies to ALL Angular-related queries regardless of whether (SiMPL) Element libraries are explicitly mentioned. The tool provides access to version-specific Siemens (SiMPL) Element documentation that is automatically tuned to match the user's library versions. This ensures you get the exact APIs, components, and implementation patterns available in their specific setup rather than generic Angular advice. Always search first to leverage the comprehensive @siemens/element-ng, @siemens/maps-ng, @siemens/charts-ng, @siemens/dashboards-ng, @siemens/native-charts-ng, @siemens/element-theme, and @siemens/element-translate-ng documentation before offering any Angular guidance.

Semantic search tool for Siemens (SiMPL) Element Design System and Angular component libraries. This tool provides intelligent search across comprehensive documentation for:

Supported Libraries:
• @siemens/element-ng - Core UI components (buttons, inputs, modals, etc.)
• @siemens/maps-ng - Interactive mapping components
• @siemens/charts-ng - Data visualization charts
• @siemens/dashboards-ng - Dashboard layout components
• @siemens/native-charts-ng - Native charting solutions
• @siemens/element-theme - (S)CSS theme and utility classes similar to bootstrap
• @siemens/element-translate-ng - Translation abstraction layer

Use Cases:
• Find component APIs and properties
• Discover usage examples and code snippets
• Learn about component styling and theming
• Understand integration patterns
• Explore design system guidelines

Search Tips:
• Use component names: "button", "chart", "map"
• Describe functionality: "data visualization", "user input"
• Ask about APIs: "input", "output", "attributes", "methods", "type"

The search returns relevant documentation chunks with similarity scores and contextual headers to help you find exactly what you need.
element-icon-search query, limit
Element Icon Search

Please check the icon search tool before using or recommending any icons from @siemens/element-icons. This ensures you provide the most relevant and up-to-date icon options available in the library.

Semantic search tool for Siemens (SiMPL) Element Icons (including their metadata like tags)

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=22
Sourcehttps://code.siemens.com/ux/sdl-mcp
Install scripts@github/keytar, onnxruntime-node, protobufjs, sharp declare them. This runner does not run them.
Tarballsha512-TrXLY6wPlt0uX9mIFtP+FQaCGMdRVE+svhkXH9LfLWoVSP+eTPpcHehlLo9Ksuy5rMVKw3XU4W+97Os8GCBP3A==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@siemens/element-mcp.svg)](https://bragproof.smaverk.com/r/%40siemens/element-mcp)

New version out? Ask for a fresh report.