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/assoujojo82-coder/synergieloc-mcpWrote 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/assoujojo82-coder/synergieloc-mcp/synergieloc)<a href="https://agentmods.dev/mcp/assoujojo82-coder/synergieloc-mcp/synergieloc"><img src="https://agentmods.dev/badge/mcp/assoujojo82-coder/synergieloc-mcp/synergieloc/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/assoujojo82-coder/synergieloc-mcp/synergieloc"><img src="https://agentmods.dev/badge/mcp/assoujojo82-coder/synergieloc-mcp/synergieloc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
synergieloc 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
{
"synergieloc": {
"type": "http",
"url": "https://synergieloc.fr/mcp",
"headers": {
"Authorization": "Bearer ${SYNERGIELOC_API_KEY}"
}
}
}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 · 9 lines scan A 8a867afc5770
synergieloc is an MCP server published in the GitHub repository assoujojo82-coder/synergieloc-mcp (0 stars, last pushed 7d 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-10-29.
Other mcp servers, from other repositories
sg-eli-mcp
MCP server for Singapore Statutes Online (sso.agc.gov.sg) — browse, fetch, and cite Singapore legislation by act code. Runs locally from the sg-eli-mcp Python package.
tr-eli-mcp
MCP server for Turkish legislation via the Adalet Bakanligi Bedesten API — fetch legislation with resolvable identifiers and verifiable citations. Runs locally from the tr-eli-mcp Python package.
sk-eli-mcp
MCP server for the Slovak Collection of Laws (Zbierka zakonov) via static.slov-lex.sk - Slovak legislation with national ELI identifiers and verifiable citations. Runs locally from the sk-eli-mcp Python package.
tenderapi-mcp
MCP server for TenderAPI: French (BOAMP) and EU (TED) public procurement data. Runs locally from the tenderapi-mcp Python package. Needs 2 environment variables to run.
gb-eli-mcp
MCP server for UK legislation (legislation.gov.uk), case law (Find Case Law) and GOV.UK tribunal decisions, HMRC manuals and CMA cases — with persistent identifiers and verifiable citations. Runs locally from the gb-eli-mcp Python package.
ro-eli-mcp
MCP server for the Romanian Portal Legislativ (legislatie.just.ro) SOAP API - search and fetch Romanian legislation with verifiable citations. Runs locally from the ro-eli-mcp Python package.