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/htristram/trustydata-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/htristram/trustydata-mcp-server/trustydata)<a href="https://agentmods.dev/mcp/htristram/trustydata-mcp-server/trustydata"><img src="https://agentmods.dev/badge/mcp/htristram/trustydata-mcp-server/trustydata/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/htristram/trustydata-mcp-server/trustydata"><img src="https://agentmods.dev/badge/mcp/htristram/trustydata-mcp-server/trustydata.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trustydata 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.
What it actually says
{
"trustydata": {
"url": "https://mcp.trustydata.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.
- 1mo ago First seen · 6 lines scan A 2de7a96d5d27
trustydata is an MCP server published in the GitHub repository htristram/trustydata-mcp-server (3 stars, last pushed yesterday), 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
acuris-mcp
Address validation & geocoding for AI agents: 240+ countries, UK PAF, free US/CA enrichment. Remote server at api.acuris-geo.com.
hu-postcode-validator
Hungarian postcode lookup + validation - 3,484 codes, sub-10ms lookups, bulk address endpoint. Remote server at unbearable-dev--hu-postcode-validator.apify.actor.
placeroot
Ground AI agents in open map data. MCP server for Overture Maps — compact answers, no API key. Runs locally from the placeroot Python package. Needs 1 environment variable to run.
wiktionary
Wiktionary MCP — multilingual dictionary via Wikimedia REST + MediaWiki Action API. Remote server at gateway.pipeworx.io.
fr-eli-mcp
MCP server for the French Legifrance API via PISTE (legifrance.gouv.fr) — search legislation (LODA, codes) and case law (JURI, Conseil constitutionnel, administrative courts) with verifiable citations and native ECLI. Runs locally from the fr-eli-mcp Python package.
synergieloc-mcp
MCP server "synergieloc-mcp" as configured in assoujojo82-coder/synergieloc-mcp. Runs locally from the synergieloc-mcp npm package.