run.daslab/sap-abap-sql
NPM · SAP-ABAP-SQL-MCP · SCANNED SEP 27
Checks and fixes ABAP Open SQL for SAP's ADT data-preview console. Connects to nothing.
Available components
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
- 32 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to daslabhq/sap-abap-sql-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 50 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 508 tokens (~127/item across 4 items; 4 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the run.daslab/sap-abap-sql MCP server?
run.daslab/sap-abap-sql runs locally as an npm package, launched with npx -y sap-abap-sql-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sap-abap-sql-mcp
claude mcp add run-daslab-sap-abap-sql -- npx -y sap-abap-sql-mcp
{
"mcpServers": {
"run-daslab-sap-abap-sql": {
"command": "npx",
"args": [
"-y",
"sap-abap-sql-mcp"
]
}
}
} {
"servers": {
"run-daslab-sap-abap-sql": {
"command": "npx",
"args": [
"-y",
"sap-abap-sql-mcp"
]
}
}
} codex mcp add run-daslab-sap-abap-sql -- npx -y sap-abap-sql-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"run-daslab-sap-abap-sql": {
"type": "local",
"command": [
"npx",
"-y",
"sap-abap-sql-mcp"
],
"enabled": true
}
}
} openclaw mcp add run-daslab-sap-abap-sql --command npx --arg -y --arg sap-abap-sql-mcp
mcp_servers:
run-daslab-sap-abap-sql:
command: "npx"
args: ["-y", "sap-abap-sql-mcp"] {
"McpServers": {
"run-daslab-sap-abap-sql": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"sap-abap-sql-mcp"
]
}
}
} assistant mcp add run-daslab-sap-abap-sql -t stdio -c npx -a -y sap-abap-sql-mcp
{
"mcpServers": {
"run-daslab-sap-abap-sql": {
"command": "npx",
"args": [
"-y",
"sap-abap-sql-mcp"
]
}
}
} 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.
- 26 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 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.
- 22 Sept 26 −2
- Stability: pass → 0.80 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 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.
- 17 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.
- 15 Sept 26 −2
- Stability: pass → 0.80 functional
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 27 Sept 2026 · Analysed npm/sap-abap-sql-mcp@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | daslabhq/sap-abap-sql-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/daslabhq/sap-abap-sql-mcp/.github/workflows/release.yml@refs/tags/v0.3.0 |
| Rekor log index | 2375065418 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1792a3f2fedad0875b2fd3c5bff816914916e934f48cac57a81cd403887690c85de5dc9a6f8c6519572c5d7d52f6781e107b8658d3bf7ec99e5a0d571 |
Background: How many MCP packages publish verified provenance →
Dependencies 107 packages
| Packages resolved | 107 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
abap_sql_explain Decode a statement the console rejected ~71
The console rejected a statement and its error does not say why. Reports every dialect problem with the correction and a stable rule id, without rewriting anything. Use abap_sql_prepare instead when you just want a statement that works.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | A single ABAP Open SQL SELECT statement. |
No output schema declared.
No examples provided.
abap_sql_prepare Prepare a statement before sending it ~72
Call this before sending any SELECT to an SAP ADT data-preview console. Returns the statement to send, or refuses it and names what to change. Fixes the mechanical problems itself and enforces the console's 255-character ceiling.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | A single ABAP Open SQL SELECT statement. |
No output schema declared.
No examples provided.
abap_sql_query Run a statement against a connected system ~128
Prepare a SELECT and run it against the SAP system this server is configured for, returning rows. Only available when SAP_URL, SAP_USER and SAP_PASSWORD are set; without them the other tools still work. Read-only: the data-preview console cannot write. Results are capped at 5000 rows by the console, and a result at the cap is reported as truncated rather than returned as if complete.
| Name | Type | Req | Description |
|---|---|---|---|
| max_rows | number | – | Rows to request, up to the console's hard cap of 5000. |
| sql | string | yes | A single ABAP Open SQL SELECT statement. |
No output schema declared.
No examples provided.
abap_sql_rules List the dialect rules ~40
The five ways this dialect differs from standard SQL, each with the correct form. Also delivered in the server instructions, so you likely have them already.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the run.daslab/sap-abap-sql MCP server?
run.daslab/sap-abap-sql is an MCP server listed in the public MCP registry as run.daslab/sap-abap-sql. Checks and fixes ABAP Open SQL for SAP's ADT data-preview console. Connects to nothing. This page covers its npm package (sap-abap-sql-mcp).
Is the run.daslab/sap-abap-sql MCP server safe to use?
run.daslab/sap-abap-sql scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 run.daslab/sap-abap-sql MCP server expose?
run.daslab/sap-abap-sql exposes 4 tools: abap_sql_prepare, abap_sql_explain, abap_sql_query, abap_sql_rules. Their descriptions and schemas cost roughly 311 tokens of context every time the server is loaded.
Is the run.daslab/sap-abap-sql MCP server still maintained?
run.daslab/sap-abap-sql is still listed as active in the MCP registry. We last reached this channel on 27 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 run.daslab/sap-abap-sql MCP server under?
run.daslab/sap-abap-sql declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.