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/postio-uk/postio-integrationsWrote 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/postio-uk/postio-integrations/mcp-postcode-address-validation)<a href="https://agentmods.dev/mcp/postio-uk/postio-integrations/mcp-postcode-address-validation"><img src="https://agentmods.dev/badge/mcp/postio-uk/postio-integrations/mcp-postcode-address-validation/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/postio-uk/postio-integrations/mcp-postcode-address-validation"><img src="https://agentmods.dev/badge/mcp/postio-uk/postio-integrations/mcp-postcode-address-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
postcode-address-validation 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
{
"postcode-address-validation": {
"command": "npx",
"args": [
"-y",
"@postio/mcp"
],
"env": {
"POSTIO_API_KEY": "",
"POSTIO_BASE_URL": ""
}
}
}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 · 13 lines scan A 6f1ab23913bb
postcode-address-validation is an MCP server published in the GitHub repository postio-uk/postio-integrations (0 stars, last pushed 5d 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
clerk
MCP server "clerk", hosted remotely at mcp.clerk.com, as configured in FloB95/qrcodly.
mcp-server
US address verification, parsing, autocomplete, geocoding, and IP geolocation APIs. Runs locally from the @sthan/mcp-server npm package. Needs 1 environment variable to run.
acuris-mcp-server
Address validation, UK postcode lookup (PAF), geocoding & reverse-geocoding in 240+ countries. Runs locally from the @acuris-geo/mcp-server npm package. Needs 1 environment variable to run.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
workos
MCP server "workos", hosted remotely at mcp.workos.com, as configured in praveenjuge/teak.
admin-mcp
Model Context Protocol (MCP) for Hellō Admin API. Runs locally from the @hellocoop/admin-mcp npm package.