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/Synter-Media-AI/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/synter-media-ai/mcp-server/synter)<a href="https://agentmods.dev/mcp/synter-media-ai/mcp-server/synter"><img src="https://agentmods.dev/badge/mcp/synter-media-ai/mcp-server/synter/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/synter-media-ai/mcp-server/synter"><img src="https://agentmods.dev/badge/mcp/synter-media-ai/mcp-server/synter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
synter 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
{
"synter": {
"command": "npx",
"args": [
"-y",
"@synterai/mcp-server"
],
"env": {
"SYNTER_API_KEY": "${SYNTER_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.
- 1mo ago First seen · 12 lines scan A 6e0069be7091
synter is an MCP server published in the GitHub repository Synter-Media-AI/mcp-server (21 stars, last pushed today), 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-30.
Other mcp servers, from other repositories
google-meta-ads-ga4-mcp
Google Ads, Meta Ads, SEO, GEO & GA4 MCP by Ryze AI - audits, reports, keywords, Search Console. Remote server at connector.get-ryze.ai.
google-meta-ads-ga4
MCP server "google-meta-ads-ga4", hosted remotely at connector.get-ryze.ai, as configured in irinabuht12-oss/google-meta-ads-ga4-mcp.
adspirer
MCP server "adspirer", hosted remotely at mcp.adspirer.com, as configured in amekala/ads-mcp.
ads
Manage Google, Meta, Amazon, TikTok, LinkedIn & ChatGPT ads. 430 tools for campaigns & analytics. Remote server at mcp.adspirer.com.
linkedin-mcp
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own. Runs locally from the @gtm-api/linkedin-mcp npm package. Needs 1 environment variable to run.
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.