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/cap-js/mcp-serverWrote 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/cap-js/mcp-server/cds-mcp)<a href="https://agentmods.dev/mcp/cap-js/mcp-server/cds-mcp"><img src="https://agentmods.dev/badge/mcp/cap-js/mcp-server/cds-mcp/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/cap-js/mcp-server/cds-mcp"><img src="https://agentmods.dev/badge/mcp/cap-js/mcp-server/cds-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cds-mcp 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cds-mcp — 100% identical, 0 lines differ
What it actually says
{
"cds-mcp": {
"command": "npx",
"args": [
"-y",
"@cap-js/mcp-server"
]
}
}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.
- 1mo ago First seen · 9 lines scan A 1a402ccbbdf5
cds-mcp is an MCP server published in the GitHub repository cap-js/mcp-server (117 stars, last pushed today), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
x-mcp-ai
Safety-first X (Twitter) API v2 MCP server: 41 typed tools across 12 packages, policy-gated. Runs locally from the x-mcp-ai npm package. Needs 18 environment variables to run.
capforge
MCP server that makes AI agents get SAP CAP/CDS right: modern scaffolding + real validation loop against cds compile. Runs locally from the capforge npm package.
cds-db-nlquery-mcp
MCP server for natural-language queries against SAP CAP db-layer entities via real CQN/SQL JOINs. Runs locally from the @shahid.la/cds-db-nlquery-mcp npm package. Needs 4 environment variables to run.
salesforce-mcp-server
Comprehensive Salesforce MCP Server with 61+ specialized tools for complete Salesforce ecosystem management - from data operations to advanced DevOps workflows. Supports stdio + HTTP modes for AI assistants and orchestration platforms. Runs locally from the @kirtijha/salesforce-mcp-server npm package.
gsheets
Model Context Protocol (MCP) server for Google Sheets API integration. Runs locally from the mcp-gsheets npm package.
kafka-schema-registry
MCP server "kafka-schema-registry" as configured in aywengo/kafka-schema-reg-mcp. Runs kafka_schema_registry_unified_mcp.py with python. Needs 3 environment variables to run.