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/john-walkoe/uspto_enriched_citation_mcpWrote 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/john-walkoe/uspto_enriched_citation_mcp/uspto-enriched-citation-mcp)<a href="https://agentmods.dev/mcp/john-walkoe/uspto_enriched_citation_mcp/uspto-enriched-citation-mcp"><img src="https://agentmods.dev/badge/mcp/john-walkoe/uspto_enriched_citation_mcp/uspto-enriched-citation-mcp/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/john-walkoe/uspto_enriched_citation_mcp/uspto-enriched-citation-mcp"><img src="https://agentmods.dev/badge/mcp/john-walkoe/uspto_enriched_citation_mcp/uspto-enriched-citation-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
uspto-enriched-citation-mcp 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 12d 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
{ "uspto-enriched-citation-mcp": { "command": "uvx", "args": [ "uspto-enriched-citation-mcp" ] } }
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.
- 12d ago First seen · 8 lines scan A 63eb754f1e76
uspto-enriched-citation-mcp is an MCP server published in the GitHub repository john-walkoe/uspto_enriched_citation_mcp (6 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
fpd-mcp
MCP server "fpd-mcp" as configured in Tam1379/usptofpdmcp. Runs locally from the fpd-mcp Python package.
yuandian-law
MCP server "yuandian-law", hosted remotely, as configured in lawyerllsx-dotcom/Legal-Workflow-Chain. Needs 1 environment variable to run.
yuandian-case
MCP server "yuandian-case", hosted remotely, as configured in lawyerllsx-dotcom/Legal-Workflow-Chain. Needs 1 environment variable to run.
fedlex
MCP server "fedlex" as configured in malkreide/fedlex-mcp. Runs fedlex_mcp.server with python.
fedlex-mcp
MCP Server for Swiss federal law via the Fedlex SPARQL endpoint. Runs locally from the fedlex-mcp Python package.
mycase-mcp
MCP server for MyCase API — full coverage for law firm practice management. Runs locally from the mycase-mcp Python package.