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/merlhn/ehliyetWrote 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/merlhn/ehliyet/ehliyet-digital)<a href="https://agentmods.dev/mcp/merlhn/ehliyet/ehliyet-digital"><img src="https://agentmods.dev/badge/mcp/merlhn/ehliyet/ehliyet-digital/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/merlhn/ehliyet/ehliyet-digital"><img src="https://agentmods.dev/badge/mcp/merlhn/ehliyet/ehliyet-digital.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ehliyet-digital 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 9d 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
{
"ehliyet-digital": {
"url": "https://ehliyet-production.up.railway.app/mcp",
"type": "streamable-http"
}
}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.
- 9d ago First seen · 6 lines scan A 1e969d43e57b
ehliyet-digital is an MCP server published in the GitHub repository merlhn/ehliyet (0 stars, last pushed 16d 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
statcan-local
MCP server "statcan-local", hosted remotely at localhost, as configured in Aryan-Jhaveri/mcp-statcan.
mcp-statcan
MCP Server for interacting with Statistics Canada Web Data Services API. Runs locally from the statcan-mcp-server Python package.
nxopen-mcp
MCP server that gives AI coding agents accurate NXOpen .NET API knowledge via hybrid retrieval. Runs locally from the nxopen-mcp Python package.
swiss-procurement-mcp
MCP server for the simap.ch Swiss public procurement API — all cantons, read-only. Runs locally from the swiss-procurement-mcp Python package.
unhcr-opendata-gateway-mcp
MCP server "unhcr-opendata-gateway-mcp" as configured in Edouard-Legoupil/unhcr-opendata-gateway-mcp. Runs locally from the unhcr-opendata-gateway-mcp Python package.
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package. Needs 1 environment variable to run.