SAP CAP MCP

90/100

Capped at 90: 1 of 2 real tool calls passed in our test; the tests add up to 100. Why scores are capped

Last tested 2026-11-11 (Fresh: tested within 30 days) Working (tool call tested 2026-11-11) No key needed for the tools we called

No advisories in range for tested 0.1.0 (checked 2026-11-11)

Security review: not tested

Test points add up to 100; the score is capped at 90 because not every real tool call passed. Not a quality or security rating. Why scores are capped

Test points before the cap (100/100)

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs15/15
  • License10/10

Tested npm @cap-js/mcp-server 0.1.0 (Apache-2.0; repo cap-js/mcp-server). Stdio (bin cds-mcp), 2 tools. search_model returned the Books entity from a small local CAP project. search_docs failed: its local embedding model could not load (onnxruntime-node shared-library version mismatch, 'VERS_1.31.1 not found') and the server returned that as text with isError false; counted as not passed. Not labelled Official: no vendor-site page recorded this run.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): partial. 1 of 2 calls passed; docs search failed to load its embedding model on Linux x64, Node 24. Evidence: local test run, Nov 11, 2026.

Transport (tested 2026-11-11): stdio

Token cost (estimate): approx. 427 tokens, cl100k estimate (2 tools, measured 2026-11-11, version 0.1.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 2 read, 0 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • search_docs — read
  • search_model — read

handshake and tools listed without a recorded key or OAuth

Score 90/100 · Tools 2 · Token cost approx. 427 tokens · Compare · Last tested 2026-11-11 · Version tested 0.1.0 · Package @cap-js/mcp-server · Repo cap-js/mcp-server

Summary: SAP CAP MCP completed an MCP handshake without credentials and exposed 2 tools.

Evidence summary

Handshake
pass
Tools listed
2
Context cost
approx. 427 tokens, cl100k estimate (2 tools, measured 2026-11-11, version 0.1.0; an estimate) ranking · add up your servers' context cost
API key
No key needed for the tools we called
Tested
2026-11-11

Test results

TestResultPointsEvidence
installpass20npm install @cap-js/mcp-server (Node 20, Linux) succeeded in 7s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 2 tools listed in 11.2s.
maintenancepass25Repo pushed 0 days before test; 118 GitHub stars.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package).
licensepass10Apache-2.0 (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 427 tokens, cl100k estimate for 2 tools · about 5% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-11

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 2 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Checked on 2026-11-11 for version 0.1.0 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.

No published advisories found in OSV and GitHub advisories for @cap-js/mcp-server 0.1.0 as of 2026-11-11. This is not a security audit.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-11 test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

b29a5670740f: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "@cap-js/mcp-server",
  "version": "0.1.0",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-11",
  "tools_count": 2,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @cap-js/mcp-server` (Node 20, Linux) succeeded in 7s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 2 tools listed in 11.2s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 118 GitHub stars."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "Apache-2.0 (OSI-approved)."
    ]
  }
}

Install

npx -y @cap-js/mcp-server

Pin the version we tested

npx -y @cap-js/mcp-server@0.1.0

tested 2026-11-11. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "sap-cap-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cap-js/mcp-server@0.1.0"
      ]
    }
  }
}

Tools listed

search_docs, search_model

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "sap-cap-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cap-js/mcp-server"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install @cap-js/mcp-server (Node 20). This is the exact command we ran on 2026-11-11.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (2 in our test).
{
  "mcpServers": {
    "sap-cap-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cap-js/mcp-server"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best dev MCP servers · Troubleshooting: Native module won't load

FAQ

Is SAP CAP MCP deprecated?

No. @cap-js/mcp-server was not deprecated or archived when we last tested it on 2026-11-11.

What replaces SAP CAP MCP?

Nothing; SAP CAP MCP is not deprecated as of 2026-11-11.

Does SAP CAP MCP need an API key?

No. It completed an MCP handshake with no credentials and listed 2 tools.

Embed the badge

TestedMCP: 90/100, tested 2026-11-11

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue