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/Coaspe/sap-abap-mcpWrote 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/coaspe/sap-abap-mcp/sap-abap-mcp-sap-abap)<a href="https://agentmods.dev/mcp/coaspe/sap-abap-mcp/sap-abap-mcp-sap-abap"><img src="https://agentmods.dev/badge/mcp/coaspe/sap-abap-mcp/sap-abap-mcp-sap-abap/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/coaspe/sap-abap-mcp/sap-abap-mcp-sap-abap"><img src="https://agentmods.dev/badge/mcp/coaspe/sap-abap-mcp/sap-abap-mcp-sap-abap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sap-abap 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 12d 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-abap": {
"command": "npx",
"args": [
"--yes",
"--prefer-online",
"@coaspe/sap-abap-mcp@latest",
"serve"
]
}
}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.
- 12d ago First seen · 11 lines scan A 62cb0fb55bc6
sap-abap is an MCP server published in the GitHub repository Coaspe/sap-abap-mcp (4 stars, last pushed 4d 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-31.
Other mcp servers, from other repositories
sap-adt-mcp
Give Claude live access to SAP ABAP via ADT: read, search, check, test, and edit objects. Runs locally from the sap-adt-mcp npm package. Needs 1 environment variable to run.
folderbridge-mcp
MCP server "folderbridge-mcp" as configured in MoonTzai/folderbridge-mcp. Runs locally from the folderbridge-mcp Python package.
sap-abap-sql
Checks and fixes ABAP Open SQL for SAP's ADT data-preview console. Connects to nothing. Runs locally from the sap-abap-sql-mcp npm package.
sap-adt-mcp
MCP server "sap-adt-mcp" as configured in engoetz/sap-adt-mcp. Runs locally from the sap-adt-mcp Python package.
lsp
MCP server "lsp" as configured in blackwell-systems/agent-lsp. Launched with agent-lsp go:gopls.
behavior-mcp
MCP server "behavior-mcp" as configured in putervision/state-memory-mcp. Launched with behavior-mcp run. Needs 1 environment variable to run.