Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MarioDeFelipe/sap-bdc-plugin/plugin install sap-bdcWrote 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/mariodefelipe/sap-bdc-plugin/sap-bdc)<a href="https://agentmods.dev/mcp/mariodefelipe/sap-bdc-plugin/sap-bdc"><img src="https://agentmods.dev/badge/mcp/mariodefelipe/sap-bdc-plugin/sap-bdc.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sap-bdc 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 6d 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.
What it actually says
{
"sap-bdc": {
"command": "python",
"args": [
"-m",
"sap_bdc_mcp.server"
],
"env": {
"PYTHONPATH": "${CLAUDE_PLUGIN_ROOT}/mcp-server/src",
"DATABRICKS_HOST": "${DATABRICKS_HOST}",
"DATABRICKS_TOKEN": "${DATABRICKS_TOKEN}",
"DATABRICKS_RECIPIENT_NAME": "${DATABRICKS_RECIPIENT_NAME}",
"DATABRICKS_WAREHOUSE_ID": "${DATABRICKS_WAREHOUSE_ID}",
"LOG_LEVEL": "INFO"
}
}
}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.
- 6d ago First seen · 17 lines scan A 410c8ababc5a
sap-bdc is an MCP server published in the GitHub repository MarioDeFelipe/sap-bdc-plugin (9 stars, last pushed 4mo ago), licensed MIT. 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-31.
Other mcp servers, from other repositories
knowledge_catalog
MCP server "knowledgecatalog", hosted remotely at dataplex.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
dataproc
MCP server "dataproc", hosted remotely at dataproc-$gcpregion.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
Pinecone
Model Context Protocol server for Pinecone - enables AI assistants to interact with Pinecone indexes and documentation. Runs locally from the @pinecone-database/mcp npm package. Needs 1 environment variable to run.
hubmesh
Centrality-aware GraphRAG retrieval planner — drop-in layer over any vector DB. Runs locally from the hubmesh Python package.
ollama-vision-mcp
MCP server "ollama-vision-mcp" as configured in masterLazy/ollama-vision-mcp. Runs locally from the ollama-vision-mcp Python package.