{
  "markdown": "# KnowJudges MCP\n\nAdd source-linked U.S. judge and court research directly to AI assistants and agents through the Model Context Protocol.\n\n**Website:** https://knowjudges.com\n**MCP documentation:** https://knowjudges.com/mcp\n**Remote MCP endpoint:** `https://mcp.knowjudges.com/mcp`\n\n## Overview\n\nThe KnowJudges MCP server exposes six focused research tools over **Streamable HTTP**.\n\nCompatible MCP clients can discover the available tools, validate inputs, and retrieve structured, source-linked KnowJudges results without building a custom API integration.\n\nPublic access currently requires **no authentication token**.\n\n## Connect\n\nUse this remote MCP endpoint:\n\n```text\nhttps://mcp.knowjudges.com/mcp\n```\n\n**Transport:** Streamable HTTP\n**Authentication:** None required for public access\n\nFor clients that support an MCP server configuration object:\n\n```json\n{\n  \"mcpServers\": {\n    \"know-your-judge\": {\n      \"url\": \"https://mcp.knowjudges.com/mcp\"\n    }\n  }\n}\n```\n\nConfiguration field names vary between MCP clients. If your client asks only for a server URL, enter:\n\n```text\nhttps://mcp.knowjudges.com/mcp\n```\n\nThe official KnowJudges connection instructions use this same remote endpoint and transport.\n\n## Available tools\n\n### `find_judges`\n\nResolve a likely judge and canonical KnowJudges slug.\n\nUse this when you know some combination of a judge's name, court, or jurisdiction and need to identify the correct KnowJudges profile.\n\n### `get_judge_profile`\n\nRetrieve a public judge profile containing source-linked, scoped findings.\n\n### `get_judge_biography`\n\nRetrieve sourced public background information about a judge without behavioral inference.\n\n### `get_courtroom_presentation_rules`\n\nResearch courtroom presentation requirements and guidance, including topics such as:\n\n* PowerPoint\n* Video\n* Exhibits\n* Demonstratives\n* Related courtroom presentation requirements\n\n### `find_ai_abuse_cases`\n\nFind up to 10 court cases involving AI-generated legal errors.\n\nResults can include:\n\n* Judge\n* Court response\n* Dataset source\n* Verified official decision link when available\n\n### `get_recent_rule_changes`\n\nRetrieve changes recorded since KnowJudges change tracking began.\n\nThese are the six tools currently exposed by the public MCP service.\n\n## Example prompt\n\nAfter connecting the MCP server, try:\n\n> Find the five most recent New York court cases involving fabricated AI-generated legal material. Include the judge, court response, and verified official decision URL when available.\n\nA provenance-aware response should preserve the underlying source information and avoid making claims beyond what the published records support.\n\n## Rate limits\n\nThe public KnowJudges REST API and MCP server share the same allowance for each public client or network:\n\n| Window |    Allowance |\n| ------ | -----------: |\n| Hourly |  20 requests |\n| Daily  | 100 requests |\n\nRequests exceeding either limit return HTTP `429`.\n\nMCP initialization, tool discovery, and individual tool calls are separate HTTP requests and each counts toward this shared allowance.\n\nFor datasets, recurring feeds, batch research, higher-volume usage, or private integrations, see:\n\nhttps://knowjudges.com/mcp\n\n## Provenance\n\nKnowJudges is designed around source-linked research.\n\nApplications and agents should preserve source information returned by MCP tools, including official decision links and other provenance metadata where available.\n\nIn particular:\n\n* Do not remove source URLs when presenting results.\n* Do not represent a source as supporting more than it actually states.\n* Distinguish judge-specific information from courtwide or jurisdiction-wide guidance.\n* Preserve verified official decision links when returned.\n* Do not convert sourced facts into unsupported behavioral conclusions.\n\n## Example research workflow\n\nA typical agent workflow might be:\n\n```text\nUser question\n    ↓\nfind_judges\n    ↓\ncanonical judge\n    ↓\nget_judge_profile\n    ↓\nget_judge_biography\n    ↓\nget_courtroom_presentation_rules\n    ↓\nsource-linked answer\n```\n\nFor legal-AI research:\n\n```text\nUser question\n    ↓\nfind_ai_abuse_cases\n    ↓\nsource-linked cases\n    ↓\nverified official decisions where available\n```\n\n## REST API\n\nKnowJudges also provides a public REST API for applications that do not use MCP.\n\n**API documentation:**\n\nhttps://knowjudges.com/api\n\nMCP is generally the simpler interface for MCP-compatible AI assistants and agents, while the REST API provides direct HTTP access for conventional applications.\n\n## Links\n\n* **KnowJudges:** https://knowjudges.com\n* **Judicial Registry:** https://knowjudges.com/kyj\n* **Judicial Directory:** https://knowjudges.com/judicial-directory\n* **API:** https://knowjudges.com/api\n* **MCP documentation:** https://knowjudges.com/mcp\n* **Remote MCP endpoint:** `https://mcp.knowjudges.com/mcp`\n\n## About KnowJudges\n\nKnowJudges provides free, source-linked research on U.S. judges and courts through public judicial profiles, court information, research tools, API access, and MCP integrations.\n\nThe MCP server is intended to make that information directly usable by AI assistants, research agents, and other MCP-compatible software while preserving the provenance of the underlying research.\n\nFor current terms, data-use information, licensing information, and corrections policies, refer to the relevant pages on https://knowjudges.com.\n",
  "bytes": 5364,
  "sha": "145d6295d09642afbb5f785352d0476090b30f81c1fd2783a44a10101cbad57a",
  "repo_slug": "knowjudges/knowjudges-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_knowjudges_knowjudges_9d0774e9/readme"
}