abapilot

MCPcommunity
v1.0.6io.github.NicoHernMITUpdated 14d agonpmGitHub

ABAP MCP connector for SAP ECC and on-premise S/4HANA. Requires a licensed ABAPilot backend.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
86Downloads/wk
3GitHub stars
14d agoLast update
Reads these credentials
  • ABAPILOT_PASSWORDAPI keyoptional

    SAP password for basic authentication

  • ABAPILOT_TOKENAPI keyoptional

    Bearer token, alternative to basic authentication

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.NicoHern
LicenseMIT
Version1.0.6
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv1.0.2 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 23, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged
Statically extracted from the published packagev1.0.2 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

sap_read_table_dataNo description published

This tool published no description. Forge does not invent one.

sap_read_table_structureNo description published

This tool published no description. Forge does not invent one.

sap_search_tablesNo description published

This tool published no description. Forge does not invent one.

sap_read_codeNo description published

This tool published no description. Forge does not invent one.

sap_read_where_usedNo description published

This tool published no description. Forge does not invent one.

sap_syntax_checkNo description published

This tool published no description. Forge does not invent one.

sap_read_dumpsNo description published

This tool published no description. Forge does not invent one.

sap_read_jobsNo description published

This tool published no description. Forge does not invent one.

0 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

ABAP MCP connector for SAP ECC and on-premise S/4HANA. Requires a licensed ABAPilot backend.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.