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/handonn2000/vnlawkgWrote 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/handonn2000/vnlawkg/vnlaw-kg)<a href="https://agentmods.dev/mcp/handonn2000/vnlawkg/vnlaw-kg"><img src="https://agentmods.dev/badge/mcp/handonn2000/vnlawkg/vnlaw-kg/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/handonn2000/vnlawkg/vnlaw-kg"><img src="https://agentmods.dev/badge/mcp/handonn2000/vnlawkg/vnlaw-kg.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vnlaw-kg 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
{ "vnlaw-kg": { "command": "uvx", "args": [ "vnlaw-kg" ] } }
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 · 8 lines scan A 4d7befd21663
vnlaw-kg is an MCP server published in the GitHub repository handonn2000/vnlawkg (0 stars, last pushed 12d ago), licensed Apache-2.0. 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
clio-mcp
Connect Claude to Clio: 26 tools for matters, contacts, documents, tasks, billing, audit logs. Runs locally from the @oktopeak/clio-mcp npm package. Needs 8 environment variables to run.
sg-eli-mcp
MCP server for Singapore Statutes Online (sso.agc.gov.sg) — browse, fetch, and cite Singapore legislation by act code. Runs locally from the sg-eli-mcp Python package.
trademarks
Trademark search, monitoring and conflict research across 30+ registers, with provenance. Remote server at markmesh.com.
korea-tax-law-mcp
Korean tax law graph: current statutes, 150k+ court/tribunal cases, 145k+ NTS rulings. Remote server at mcp.taxjarvis.com.
hkopenai.hk_law_mcp_server
Hong Kong law MCP Server providing law data tools. Runs locally from the hkopenai.hk_law_mcp_server Python package.
be-eli-mcp
MCP server for Belgian legislation via Moniteur Belge / Belgisch Staatsblad (ejustice.just.fgov.be) — ELI-coordinate metadata and full text with verifiable citations. Runs locally from the be-eli-mcp Python package.