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/oktopeak/mycase-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/oktopeak/mycase-mcp/mycase-mcp)<a href="https://agentmods.dev/mcp/oktopeak/mycase-mcp/mycase-mcp"><img src="https://agentmods.dev/badge/mcp/oktopeak/mycase-mcp/mycase-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/oktopeak/mycase-mcp/mycase-mcp"><img src="https://agentmods.dev/badge/mcp/oktopeak/mycase-mcp/mycase-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mycase-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 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
{
"mycase-mcp": {
"command": "npx",
"args": [
"-y",
"@oktopeak/mycase-mcp"
],
"env": {
"MYCASE_CLIENT_ID": "",
"MYCASE_CLIENT_SECRET": "",
"ENCRYPTION_KEY": "",
"MYCASE_REDIRECT_PORT": "",
"MYCASE_EXPERIMENTAL_TOOLS": ""
}
}
}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 · 16 lines scan A bfa898d8a24c
mycase-mcp is an MCP server published in the GitHub repository oktopeak/mycase-mcp (6 stars, last pushed 11d 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
open-agreements
Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files. Runs locally from the @open-agreements/contract-templates-mcp npm package.
clio-mcp
Connect Claude to Clio: 34 tools for matters, custom fields, notes, documents, folders, billing. Runs locally from the @oktopeak/clio-mcp npm package. Needs 9 environment variables to run.
eu-ai-act-mcp
EU AI Act compliance MCP server with bounded system assessment, structured classification, article grounding, GPAI, Art. 6(3), Annex III/IV, deadlines, obligations, penalties, and FAQ. By Lexbeam Software. Runs locally from the @lexbeam-software/eu-ai-act-mcp npm 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.
mycase-mcp
MCP server for MyCase API — full coverage for law firm practice management. Runs locally from the mycase-mcp Python package.