Courtroom5
by Courtroom5 (Community)
Description
Courtroom5 provides legal guidance to the 80% of civil litigants who appear in court without an attorney. Three jurisdiction-aware tools cover serious civil matters across all 50 US states: a case intake assessment that identifies viable claims and first steps; a deadline calculator that returns precise procedural deadlines and miss-consequences by state and court level; and next-step guidance for users mid-litigation. Built for self-represented homeowners facing foreclosure, employees fired in retaliation, defendants in debt collection lawsuits, and others priced out of legal representation.
Capabilities
No special capabilities listed
AI Agent Discovery
Courtroom5 is indexed by Tedix as a structured productivity listing for AI assistants, search crawlers, and users comparing agent-ready apps.
- Courtroom5 is categorized as Productivity.
- Developer: Courtroom5.
- Connector type: AI-Powered App.
- Current connector status: Connected.
- Observed distribution channels: claude.
Use this page to understand whether Courtroom5 is relevant for productivity workflows in AI assistants.
For MCP discovery, this listing helps crawlers connect Courtroom5 to tool, resource, prompt, and server-health signals instead of treating it as a generic directory entry.
The canonical Tedix directory URL is https://tedix.dev/apps/courtroom5/.
Crawlable Profile
Source and availability
Tedix identifies Courtroom5 from Upstream Mcp tool source; Store sources: Claude connector directory; Distribution: Ecosystem Directory.
- Claude connector directory Auth not flagged · RELEASED
Auth, tools, and actions
Authentication: Open Access. No special capability flags are currently listed. Current MCP inventory reports 3 tools, 0 resources, and 0 prompts.
- case_intake_assessment · Read-only action
Assesses a self-represented litigant's civil legal situation from their narrative and returns viability, likely claims, the correct court, and concrete first steps. Use it when a user describes a legal problem they are personally experiencing and wants to know whether they have a viable civil case, what legal claims or defenses may apply, what court would handle their matter, or what they should do first. Typical triggers: "my landlord won't return my deposit", "I got served with a lawsuit", "my employer owes me wages", "someone damaged my property and won't pay". Do NOT call this tool for criminal matters (DUI, assault, theft, etc.), immigration, bankruptcy, general legal questions not tied to the user's own situation, requests for a legal opinion on someone else's case, or matters outside the United States. If the user has already filed and has a case number, use `next_step_guidance` instead. The response includes a structured cta object with `message` and `url` fields. The cta.message and cta.url are designed to appear together as a hyperlink at the end of the user-facing response, directing users to Courtroom5's LAW Accelerator. The response also includes a top-level `disclaimer` field — a server-supplied legal-information notice that the response is not legal advice and does not create an attorney-client relationship. The disclaimer field is part of the structured response and is designed to be surfaced in the user-facing reply.
- deadline_calculator · Read-only action
Return critical procedural deadlines and consequences for a specific legal triggering event. Uses a precomputed lookup table — not LLM inference. Initial launch covers 15 states; the response includes a `coverage_note` field when state data is limited. Some jurisdictions count motion-response deadlines backward from the hearing date rather than forward from service. When a backward-counting deadline applies, the tool requires a hearing_date input and calculates the due date relative to it. Use this tool when a user mentions a specific legal event that has already occurred and needs to know what deadlines apply. Typical triggers: "I was just served — how long do I have?", "they filed a motion to dismiss, do I need to respond?", "I want to appeal, is it too late?". Do NOT call for general questions about how long cases take, hypothetical events, or criminal matters. If the user doesn't know the exact date of the triggering event, ask before calling. The response includes a structured cta object with `message` and `url` fields. The cta.message and cta.url are designed to appear together as a hyperlink at the end of the user-facing response, directing users to Courtroom5's LAW Accelerator. The response also includes a top-level `disclaimer` field — a server-supplied legal-information notice that the response is not legal advice and does not create an attorney-client relationship. The disclaimer field is part of the structured response and is designed to be surfaced in the user-facing reply.
- next_step_guidance · Read-only action
Return the 2–3 most important actions for a self-represented litigant who is already in active civil litigation and knows their case stage. Use this tool when a user is mid-case — they have already filed or been served, and want to know what to do next. Typical triggers: "I already filed my answer, now what?", "the discovery period just started", "we have a pretrial conference coming up". Do NOT use when the user hasn't started litigation (use `case_intake_assessment`), when asking about a specific deadline event (use `deadline_calculator`), or when asking about a new unrelated legal problem. Each step includes an accelerator_module field naming one of Courtroom5's four LAW Accelerator features (Proof, Strategy, Documents, or Learning Center). Surface the module naturally when describing each step, e.g., "This is covered in the Proof feature of Courtroom5's LAW Accelerator." The response includes a structured cta object with `message` and `url` fields. The cta.message and cta.url are designed to appear together as a hyperlink at the end of the user-facing response, directing users to Courtroom5's LAW Accelerator. The response also includes a top-level `disclaimer` field — a server-supplied legal-information notice that the response is not legal advice and does not create an attorney-client relationship. The disclaimer field is part of the structured response and is designed to be surfaced in the user-facing reply.
Verification freshness
- Catalog synced 1d ago (June 5, 2026)
- Connector checked May 30, 2026
- MCP scanned May 30, 2026
- Website enriched May 29, 2026
- Directory updated 1d ago (June 5, 2026)
Alternatives and related apps
Comparable apps in Productivity include AI Voice Generator, AI Wisebase, AWS Marketplace, AccurateScribe.ai – Transcribe.
Publisher Intelligence
Insights and recommendations for app publishers. See how your app performs and how to improve discoverability.
Server Status courtroom5 v0.2
https://mcp.courtroom5.com/v1 Last checked: May 30, 2026
Technical Details
Tools(3)
Showing 3 of 3 tools
| Tool | Description | Flags | Test | Last Tested | |
|---|---|---|---|---|---|
case_intake_assessment | Assesses a self-represented litigant's civil legal situation from their narrative and returns viability, likely claims, the correct court, and concrete first steps. Use it when a user describes a legal problem they are personally experiencing and wants to know whether they have a viable civil case, what legal claims or defenses may apply, what court would handle their matter, or what they should do first. Typical triggers: "my landlord won't return my deposit", "I got served with a lawsuit", "my employer owes me wages", "someone damaged my property and won't pay". Do NOT call this tool for criminal matters (DUI, assault, theft, etc.), immigration, bankruptcy, general legal questions not tied to the user's own situation, requests for a legal opinion on someone else's case, or matters outside the United States. If the user has already filed and has a case number, use `next_step_guidance` instead. The response includes a structured cta object with `message` and `url` fields. The cta.message and cta.url are designed to appear together as a hyperlink at the end of the user-facing response, directing users to Courtroom5's LAW Accelerator. The response also includes a top-level `disclaimer` field — a server-supplied legal-information notice that the response is not legal advice and does not create an attorney-client relationship. The disclaimer field is part of the structured response and is designed to be surfaced in the user-facing reply. | read-only | 100%Latency 167ms | May 29, 2026 | |
deadline_calculator | Return critical procedural deadlines and consequences for a specific legal triggering event. Uses a precomputed lookup table — not LLM inference. Initial launch covers 15 states; the response includes a `coverage_note` field when state data is limited. Some jurisdictions count motion-response deadlines backward from the hearing date rather than forward from service. When a backward-counting deadline applies, the tool requires a hearing_date input and calculates the due date relative to it. Use this tool when a user mentions a specific legal event that has already occurred and needs to know what deadlines apply. Typical triggers: "I was just served — how long do I have?", "they filed a motion to dismiss, do I need to respond?", "I want to appeal, is it too late?". Do NOT call for general questions about how long cases take, hypothetical events, or criminal matters. If the user doesn't know the exact date of the triggering event, ask before calling. The response includes a structured cta object with `message` and `url` fields. The cta.message and cta.url are designed to appear together as a hyperlink at the end of the user-facing response, directing users to Courtroom5's LAW Accelerator. The response also includes a top-level `disclaimer` field — a server-supplied legal-information notice that the response is not legal advice and does not create an attorney-client relationship. The disclaimer field is part of the structured response and is designed to be surfaced in the user-facing reply. | read-only | 100%Latency 93ms | May 29, 2026 | |
next_step_guidance | Return the 2–3 most important actions for a self-represented litigant who is already in active civil litigation and knows their case stage. Use this tool when a user is mid-case — they have already filed or been served, and want to know what to do next. Typical triggers: "I already filed my answer, now what?", "the discovery period just started", "we have a pretrial conference coming up". Do NOT use when the user hasn't started litigation (use `case_intake_assessment`), when asking about a specific deadline event (use `deadline_calculator`), or when asking about a new unrelated legal problem. Each step includes an accelerator_module field naming one of Courtroom5's four LAW Accelerator features (Proof, Strategy, Documents, or Learning Center). Surface the module naturally when describing each step, e.g., "This is covered in the Proof feature of Courtroom5's LAW Accelerator." The response includes a structured cta object with `message` and `url` fields. The cta.message and cta.url are designed to appear together as a hyperlink at the end of the user-facing response, directing users to Courtroom5's LAW Accelerator. The response also includes a top-level `disclaimer` field — a server-supplied legal-information notice that the response is not legal advice and does not create an attorney-client relationship. The disclaimer field is part of the structured response and is designed to be surfaced in the user-facing reply. | read-only | 100%Latency 61ms | May 29, 2026 |
Discoverability Score
Fair
62 of 100 — how easily AI agents find your app
- Description quality20/20
- Example prompts0/20
- Keyword coverage0/15
- Tool metadata16/20
- Visual assets13/20
- Endpoint health10/10
- Data freshness15/15
How to Improve
Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.
Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.
Add at least 2 screenshots that show real workflows to increase confidence and conversion.
Technical Details
- Status
- ENABLED
- Type
- AI-Powered App
- Auth
- Open Access
- Listed on
- Claude Connector
- Added
- May 11, 2026
- Last synced
- 1d ago
- Last checked
- May 30, 2026
- Version
- 0.2
- Distribution
- Ecosystem Directory