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/apitier/apitier-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/apitier/apitier-mcp-server/mcp-server)<a href="https://agentmods.dev/mcp/apitier/apitier-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/apitier/apitier-mcp-server/mcp-server/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/apitier/apitier-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/apitier/apitier-mcp-server/mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-server 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
{
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@apitier/mcp-server"
],
"env": {
"APITIER_EMAIL_KEY": "",
"APITIER_PHONE_KEY": "",
"APITIER_VAT_KEY": "",
"APITIER_POSTCODE_KEY": "",
"APITIER_PINCODE_KEY": "",
"APITIER_BARCODE_KEY": "",
"APITIER_CONVERT_DATA_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.
- 1mo ago First seen · 18 lines scan A 7785a99a2715
mcp-server is an MCP server published in the GitHub repository apitier/apitier-mcp-server (0 stars, last pushed 4mo 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
sui-mcp
Read-only Sui blockchain analytics: 61 tools, protocol-aware tx decoding, no API keys or wallet. Runs locally from the sui-analytics-mcp npm package. Needs 6 environment variables to run.
civicrm-mcp
Model Context Protocol server for CiviCRM — AuthX-first, schema-introspected, write-gated. Runs locally from the civicrm-mcp npm package. Needs 7 environment variables to run.
cluster-execution-mcp
MCP server "cluster-execution-mcp" as configured in marc-shade/cluster-execution-mcp. Runs locally from the cluster-execution-mcp Python package.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.2). Needs 6 environment variables to run.
apibase
MCP endpoint to APIbase catalog (https://apibase.pro/llms.txt). USDC: x402 Base, MPP Tempo. Runs locally from the apibase-mcp-client npm package.
ellmos-filecommander-mcp
Filesystem MCP server: files, processes, sessions, async search, OCR, archives, safe delete. Runs locally from the ellmos-filecommander-mcp npm package.