Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.fr0ster/mcp-abap-adt

NPM · @MCP-ABAP-ADT/CORE · SCANNED SEP 20

MCP server for SAP ABAP ADT: repository analysis and CRUD for RAP and classic ABAP

Available components

0 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 68 of 208 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 22728 tokens (~110/item across 205 items; 205 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 23 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "DeleteDomain" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 205 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.fr0ster/mcp-abap-adt server?

io.github.fr0ster/mcp-abap-adt runs locally as an npm package, launched with npx -y @mcp-abap-adt/core. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @mcp-abap-adt/core

# add to Claude Code
claude mcp add fr0ster-mcp-abap-adt -- npx -y @mcp-abap-adt/core
// .cursor/mcp.json
{
  "mcpServers": {
    "fr0ster-mcp-abap-adt": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/core"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fr0ster-mcp-abap-adt": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/core"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add fr0ster-mcp-abap-adt -- npx -y @mcp-abap-adt/core
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr0ster-mcp-abap-adt": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mcp-abap-adt/core"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fr0ster-mcp-abap-adt --command npx --arg -y --arg @mcp-abap-adt/core
# ~/.hermes/config.yaml
mcp_servers:
  fr0ster-mcp-abap-adt:
    command: "npx"
    args: ["-y", "@mcp-abap-adt/core"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fr0ster-mcp-abap-adt": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mcp-abap-adt/core"
      ]
    }
  }
}
# add to Vellum
assistant mcp add fr0ster-mcp-abap-adt -t stdio -c npx -a -y @mcp-abap-adt/core
// mcp.json
{
  "mcpServers": {
    "fr0ster-mcp-abap-adt": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/core"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 17 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 16 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@mcp-abap-adt/core@8.8.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 208 packages
Packages resolved 208
Deprecated 1
Stale 66
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 205 exposed · ~22,728 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
UpdateServiceDefinition ~137

Operation: Update, Create. Subject: ServiceDefinition. Will be useful for updating or creating service definition. Update source code of an existing ABAP service definition. Locks, updates, unlocks, and optionally activates.

NameTypeReqDescription
activatebooleanActivate service definition after update. Default: true.
service_definition_namestringyesService definition name (e.g., ZSD_MY_SERVICE). Must exist in the system.
source_codestringyesComplete service definition source code.
transport_requeststringTransport request number (e.g., E19K905635). Optional if object is local or already in transport.

No output schema declared.

No examples provided.

UpdateStructure ~192

Operation: Update, Create. Subject: Structure. Will be useful for updating or creating structure. Update DDL source code of an existing ABAP structure. Locks, updates, unlocks, and optionally activates.

NameTypeReqDescription
activatebooleanActivate structure after source update. Default: true.
ddl_codestringyesComplete DDL source code for structure. Example: '@EndUserText.label : \'My Structure\' @AbapCatalog.tableCategory : #TRANSPARENT define structure zz_s_test_001 { client : abap.clnt not null; id : ab…
structure_namestringyesStructure name (e.g., ZZ_S_TEST_001). Structure must already exist.
transport_requeststringTransport request number (e.g., E19K905635). Optional if object is local or already in transport.

No output schema declared.

No examples provided.

UpdateTable ~193

Operation: Update, Create. Subject: Table. Will be useful for updating or creating table. Update DDL source code of an existing ABAP table. Locks, updates, unlocks, and optionally activates.

NameTypeReqDescription
activatebooleanActivate table after source update. Default: true.
ddl_codestringyesComplete DDL source code for table. Example: '@EndUserText.label : \'My Table\' @AbapCatalog.tableCategory : #TRANSPARENT define table ztst_table { key client : abap.clnt not null; key id : abap.char…
table_namestringyesTable name (e.g., ZZ_TEST_TABLE_001). Table must already exist.
transport_requeststringTransport request number (e.g., E19K905635). Optional if object is local or already in transport.

No output schema declared.

No examples provided.

UpdateUnitTest ~53

Update an ABAP Unit test run. Note: ADT does not support updating unit test runs and will return an error.

NameTypeReqDescription
run_idstringyesRun identifier returned by CreateUnitTest/RunUnitTest.

No output schema declared.

No examples provided.

ValidateServiceBinding ~103

Validate service binding parameters (name, service definition, package, version) via ADT validation endpoint.

NameTypeReqDescription
descriptionstringOptional description used during validation.
package_namestringABAP package for the binding.
service_binding_namestringyesService binding name to validate.
service_binding_versionstringService binding version (for example: 1.0).
service_definition_namestringyesService definition linked to binding.

No output schema declared.

No examples provided.

Common questions

What is the io.github.fr0ster/mcp-abap-adt server?

io.github.fr0ster/mcp-abap-adt is listed in the public MCP registry as io.github.fr0ster/mcp-abap-adt. MCP server for SAP ABAP ADT: repository analysis and CRUD for RAP and classic ABAP. This page covers its npm package (@mcp-abap-adt/core).

Is the io.github.fr0ster/mcp-abap-adt server safe to use?

io.github.fr0ster/mcp-abap-adt scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.fr0ster/mcp-abap-adt server expose?

io.github.fr0ster/mcp-abap-adt exposes 205 tools: GetTableContents, GetPackageContents, GetInclude, GetIncludesList, GetEnhancements, and 200 more. Their descriptions and schemas cost roughly 22,728 tokens of context every time the server is loaded.

Is the io.github.fr0ster/mcp-abap-adt server still maintained?

io.github.fr0ster/mcp-abap-adt is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.fr0ster/mcp-abap-adt server under?

io.github.fr0ster/mcp-abap-adt declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.