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/atomno-mcp/mcp-trademarksWrote 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/atomno-mcp/mcp-trademarks/mcp-trademarks)<a href="https://agentmods.dev/mcp/atomno-mcp/mcp-trademarks/mcp-trademarks"><img src="https://agentmods.dev/badge/mcp/atomno-mcp/mcp-trademarks/mcp-trademarks/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/atomno-mcp/mcp-trademarks/mcp-trademarks"><img src="https://agentmods.dev/badge/mcp/atomno-mcp/mcp-trademarks/mcp-trademarks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-trademarks 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 11d 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-trademarks": {
"command": "uvx",
"args": [
"atomno-mcp-trademarks"
],
"env": {
"MCP_TRADEMARKS_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.
- 11d ago First seen · 11 lines scan A f24df07f8e98
mcp-trademarks is an MCP server published in the GitHub repository atomno-mcp/mcp-trademarks (0 stars, last pushed 7d 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
mcp-erid
A local MCP server that checks Russian advertising-marking requirements under 38-ФЗ, a Russian law governing how certain advertisements must be labelled. MCP is a standard way for an assistant to connect to external tools.
mcp-pharma
MCP server "mcp-pharma" as configured in atomno-mcp/mcp-pharma. Runs locally from the atomno-mcp-pharma Python package. Needs 1 environment variable to run.
mcp-zakupki
A local connector for searching Russian government procurement records on zakupki.gov.ru, the official website for public tenders. It covers procedures governed by Russia's 44-FZ and 223-FZ laws and 615-PP rules.
mcp-sudact
Thin MCP client for Russian court practice (Sudact) hosted API: full-text case search + full decision text. Engine is hosted; this package only talks to the atomno-mcp backend. Runs locally from the atomno-mcp-sudact Python package. Needs 1 environment variable to run.
mcp-fns-calc
A local MCP server for Russian tax calculations and checks of taxpayer status. It uses a hosted API for fiscal-status checks and needs an access token.
mcp-fssp
MCP server for Russian FSSP (bailiff service) debt lookups: enforcement proceedings (ИП) for individuals and legal entities via multi-provider fallback. Runs locally from the atomno-mcp-fssp Python package.