Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/kts982/mcp-sap-guiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/kts982/mcp-sap-gui/sap-gui)<a href="https://agentmods.dev/mcp/kts982/mcp-sap-gui/sap-gui"><img src="https://agentmods.dev/badge/mcp/kts982/mcp-sap-gui/sap-gui/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/kts982/mcp-sap-gui/sap-gui"><img src="https://agentmods.dev/badge/mcp/kts982/mcp-sap-gui/sap-gui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sap-gui scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"sap-gui": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"python",
"-m",
"mcp_sap_gui.server"
],
"cwd": "${workspaceFolder}"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 13 lines scan A eaade31ae41c
sap-gui is an MCP server published in the GitHub repository kts982/mcp-sap-gui (31 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
linkedin-mcp-server
MCP server "linkedin-mcp-server" as configured in prakharagarwal-dev/linkedin-mcp-server. Runs in Docker (ghcr.io/prakharagarwal-dev/linkedin-mcp-server:0.16.0).
n8n-workflow-builder
A Python library for building, managing, and deploying n8n workflows with configuration-driven templates. Runs locally from the n8n-workflow-builder Python package.
teamcity
MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants. Runs locally from the @daghis/teamcity-mcp npm package. Needs 3 environment variables to run.
multisim-mcp
Unofficial MCP server for NI Multisim Automation API. Runs locally from the multisim-mcp Python package. Needs 1 environment variable to run.
servicenow-mcp
400+ ServiceNow tools across all modules — ITSM, CMDB, HRSD, CSM, SecOps, and more. Runs locally from the @aartiq/servicenow-mcp npm package. Needs 10 environment variables to run.
shotcut-mcp
MCP server "shotcut-mcp" as configured in matrodrigs/shotcut-mcp. Launched with https://github.com/matrodrigs/shotcut-mcp/releases/download/v1.5.1/shotcut-mcp-1.