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/asgard-ai-platform/mcp-tw-judgmentWrote 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/asgard-ai-platform/mcp-tw-judgment/tw-judgment)<a href="https://agentmods.dev/mcp/asgard-ai-platform/mcp-tw-judgment/tw-judgment"><img src="https://agentmods.dev/badge/mcp/asgard-ai-platform/mcp-tw-judgment/tw-judgment/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/asgard-ai-platform/mcp-tw-judgment/tw-judgment"><img src="https://agentmods.dev/badge/mcp/asgard-ai-platform/mcp-tw-judgment/tw-judgment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tw-judgment 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 9d 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
{
"tw-judgment": {
"command": "uv",
"args": [
"run",
"mcp-tw-judgment"
],
"cwd": "${PWD}",
"env": {
"PYTHONPATH": "${PWD}"
}
}
}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.
- 9d ago First seen · 13 lines scan A 5e42101a8573
tw-judgment is an MCP server published in the GitHub repository asgard-ai-platform/mcp-tw-judgment (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
taiwan-legal-db
MCP server "taiwan-legal-db" as configured in lawchat-oss/mcp-taiwan-legal-db. Runs mcp_server.server with .venv/bin/python.
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.
legal
Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow. Runs locally from the @scope-bid/scope-mcp npm package. Needs 3 environment variables to run.
scope-mcp
Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow. Runs locally from the @jackgillen15-dev/scope-mcp npm package. Needs 3 environment variables to run.
lr-labs
Deterministic cross-border tax engine: PE, GAAR, Indian TP, rule-level lookup. Compiled law, no LLM. Remote server at lrlabs.ai.