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.
npx agentmods add mcp/frlorenzon/mcp-sienge-node/sienge-nodegit clone --depth 1 https://github.com/frlorenzon/MCP-Sienge-NodeWrote 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/frlorenzon/mcp-sienge-node/sienge-node)<a href="https://agentmods.dev/mcp/frlorenzon/mcp-sienge-node/sienge-node"><img src="https://agentmods.dev/badge/mcp/frlorenzon/mcp-sienge-node/sienge-node.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sienge-node 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 9 lines scan A b49fb6b3be23
sienge-node is an MCP server published in the GitHub repository frlorenzon/MCP-Sienge-Node (1 stars, last pushed yesterday), with no licence file. 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
odoo-mcp-gateway
Security-first, version-agnostic MCP gateway for Odoo 17/18/19 — works with stock and custom modules via YAML configuration. Runs locally from the odoo-mcp-gateway Python package.
eyeot-erp
ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI. Remote server at erp.eyeot.fr.
cristianoaredes-mcp-dadosbr
MCP DadosBR Servidor MCP focado em dados públicos do Brasil. Oferece duas ferramentas simples e… Remote server at server.smithery.ai.
mcp-banco-do-brasil
MCP server for Banco do Brasil — Pix, Cobrança (boleto), Conta-Corrente, Arrecadação (OAuth2 + mTLS). Runs locally from the @codespar/mcp-banco-do-brasil npm package. Needs 6 environment variables to run.
mcp-shopee
MCP server for Shopee — LatAm marketplace Partner API v2 (orders, products, shipping, returns). Runs locally from the @codespar/mcp-shopee npm package. Needs 5 environment variables to run.
mcp-epayco
MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks. Runs locally from the @codespar/mcp-epayco npm package. Needs 3 environment variables to run.