Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CaseMagic — Federal Court Case Lookup & Monitor

REMOTE · CASEMAGIC.AI

Free US federal court case lookup: status, judge, filings, deadlines. Then watch it for new filings.

Available components

0 this week 82 Trust /100

Last scanned (21 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5204 tokens (~289/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management88
  • Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Nov 26 −2
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “explain_docket_entry” was removed ▼ security
    • Tool “send_case_mail” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_federal_case” rewrote its description, which is the text the model reads security
    • Destructive annotations: 100 → pass functional
    • New tool “draft_case_mail” functional
    • New tool “email_queued_case_result” functional
    • New tool “get_docket_entry” functional
    • “find_federal_case” dropped the optional parameter “notify_email” cosmetic
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Oct 26 +2
    • HSTS header: fail → pass ▲ security
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 7 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “explain_docket_entry” rewrote its description, which is the text the model reads security
    • Tool “find_federal_case” rewrote its description, which is the text the model reads security
    • Tool “get_case_deadlines” rewrote its description, which is the text the model reads security
    • Tool “get_case_documents” rewrote its description, which is the text the model reads security
    • Tool “get_case_status” rewrote its description, which is the text the model reads security
    • Tool “get_recent_case_activity” rewrote its description, which is the text the model reads security
    • Schema quality: 252 → 292 ▼ functional
    • First check of Tool coverage: 100 functional
  • 5 Oct 26 0
    • Tool “watch_case” rewrote its description, which is the text the model reads security
    • New tool “find_lawsuits_against_company” functional
    • New tool “list_my_cases” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://casemagic.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=casemagic.ai CN=YE2,O=Let's Encrypt,C=US 17 Nov 2026 15 Feb 2027 ECDSA 256 ECDSA-SHA384 6b54d9dedd4fc939e7bd21eb3dbefc7f014
SANs: casemagic.ai, www.casemagic.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of casemagic.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
casemagic.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self'; frame-src 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://casemagic.ai/mcp Verified 200
http (plaintext) http://casemagic.ai/mcp HTTPS enforced 301 https://casemagic.ai/mcp
MCP tools · 18 exposed · ~4,777 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_case_passport ~124

Save a case that find_federal_case just located to the signed-in CaseMagic account, which creates its Case Passport — the persistent record of the matter — and its permanent CaseMail address. Use this after the user has confirmed which case is theirs and wants CaseMagic to keep it. Requires the connect_token from that lookup, which expires shortly afterwards.

NameTypeReqDescription
connect_tokenstringyesThe connect_token returned by find_federal_case for the case the user confirmed.
user_rolestringyesThe user's own role in the case. Ask them rather than guessing.
NameTypeReqDescription
caseobject–Caption, number and court of the saved case.
docketobject–Docket size and latest activity.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
organization_matter_idstring–The saved case’s matter id.
passport_idstring–Case Passport id.
passport_versionnumber–Passport version.

No examples provided.

draft_case_mail ~184

Draft a CaseMail message from a saved case's address and return a link the user opens to review it and decide whether to send it. Use when the user asks you to reply to case correspondence or to write to someone about the case. Nothing is sent by this tool: the message only leaves CaseMagic after the user opens the review link and confirms it, and the link expires. Tell the user that they still have to confirm.

NameTypeReqDescription
bodystringyesThe message body, as plain text.
ccarray–Optional copied addresses.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
subjectstringyesThe subject line.
toarrayyesRecipient email addresses.
NameTypeReqDescription
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_idstring–The case.
sentboolean–Always false: the message is drafted for the user to approve, never sent by this tool.

No examples provided.

email_queued_case_result ~171

Have the answer to a queued find_federal_case lookup emailed to an address the user gives. When the court record’s daily request allowance is spent, find_federal_case comes back with status "queued" and a queue_id instead of the case; call this only after that, and only once the user has offered an email address and wants the result sent there. Do not ask for an address up front. CaseMagic emails the case page to that address when the lookup has run, or straight away if it already has. Calling it again with the same address changes nothing. Free and needs no account.

NameTypeReqDescription
emailstringyesThe email address the user offered for the result.
queue_idstringyesThe queue_id from a find_federal_case result whose status was "queued".
NameTypeReqDescription
case_numberstring–The case number the lookup was for.
court––The court code the lookup named, or null.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
messagestring–What to tell the user.
next_stepstring–What to do next.
notify_email_setboolean–Whether the lookup now has an address to email the answer to.
queue_idstring–The queued lookup the address was attached to.
statusstring–pending or running while it waits; ready or not_found once it has run and the answer has been emailed; failed or expired when nothing will be sent.

No examples provided.

find_federal_case ~645

Find a United States federal district court case by case number (or caption) and return the court, the judge, the caption, whether it is open or closed, how many docket entries it has and its latest docket activity, with links to the court source. Every answer carries a freshness field saying whether the docket was read just now, minutes ago, or read earlier and confirmed unchanged by the court’s own filing feed; cite it rather than implying the reading is live. Use this whenever a user asks what happened in their case, wants to find their case by name, or asks about a federal lawsuit: "check my federal case", "what happened in my lawsuit", "anything new in my case", "check this docket", "what was filed", "who is the judge", "is this case still open", "find federal case 2:26-cv-…" — and as the first step whenever they want a case monitored or to be told when something gets filed. Free and needs no account. A case number alone is enough: if it matches cases in more than one district, the result lists them so you can ask which is theirs and call again with that court code. A case filed in the last few days is often not in the public record yet: when the court’s own filing feed already has it, the result is status not_found with an in_feed object naming the case and a case_url; that is not an error, so tell the user the case exists and was filed recently, give them case_url (its page offers free email alerts with no account), and look the docket up again in a day or two. When the court record’s daily request allowance is spent the result is status queued with a queue_id rather than the case; that is not an error, so tell the user the case is loading and to try again shortly. This tool only reads and never sends anything: if the user then offers an email address for the answer, email_queued_case_result is the separate step that does that. Federal district courts only; it cannot look up state, county or traffic courts, does not file anything and does not give legal advi…

NameTypeReqDescription
case_namestring–The case caption, for example "Smith v. Acme". Used only when no case number is known.
case_numberstring–The case number as the court writes it, for example 1:23-cv-11195 or 2:24-cv-01234-ABC. Judge initials are optional and are ignored when matching.
courtstring–The court, as a CourtListener-style code such as cacd, nysd or ilnd. Optional: leave it out when the user does not know which district the case is in.
NameTypeReqDescription
can_watchboolean–Whether CaseMagic can monitor cases in this court.
caseobject–The case: court, case number, caption, filing date, status, judges, nature of suit, latest activity and docket size.
connect_tokenstring–Short-lived token for create_case_passport.
connect_token_expires_atstring–When connect_token expires.
connect_urlstring–Where the user starts watching this case.
data_freshnessstring–ISO timestamp the docket was last read from the court source.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
freshnessobject–Why the answer is as current as it claims: read now, inside the cache window, or confirmed unchanged by the court’s feed.
latest_eventsarray–Most recent docket entries, newest first.
messagestring–What to tell the user about a queued lookup.
next_stepstring–What to do next.
notify_email_setboolean–Whether the queued answer will be emailed.
queue_idstring–Ticket for a queued lookup.
recommended_next_actionobject–The offer to make after answering, decided by the server: action watch_case when the case is open and can be monitored, none otherwise.
retry_after_seconds––When a queued lookup is worth retrying.
sourceobject–Which court source answered, when it was read and where it can be seen.
statusstring–found when the case was answered; queued when the day’s court allowance is spent and the answer will follow.

No examples provided.

find_lawsuits_against_company ~197

Find new federal lawsuits filed against a company or organisation in the last 30 days: how many, in which district courts, and the newest cases with their case numbers and captions. Use when the user asks whether a company is being sued, "lawsuits against <company>", "has anyone sued <company>" or "new cases against <company>". Read from the federal district courts' public filing feeds; organisations only, never people; state courts and older suits are not covered. The result includes a link for an email whenever a new suit names the company. Free, no account.

NameTypeReqDescription
companystringyesThe company or organisation name, for example "FedEx" or "Wells Fargo Bank". Whole words are matched; Inc, LLC and the like are optional.
courtstring–Optional: limit to one district, as a code such as cacd, nysd or ilnd.
NameTypeReqDescription
casesarray–The newest suits with court, case number, caption, date and link.
coveragestring–What the search covers and does not.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
guide_url––The guide to the kind of case this company is usually sued in, or null.
matchesarray–Matching defendants with suit counts and districts.
next_stepstring–What to do next.
querystring–The company searched for.
total_suitsnumber–How many new suits name the company.
watch_new_suits_urlstring–Where the user can get an email whenever a new suit names the company.
what_it_doesstring–What that alert is and what it costs.
window_daysnumber–How many days back the search covers.

No examples provided.

get_case_deadlines ~464

Return the dates a federal docket states — "Responses due by 10/14/2026", "Hearing set for 3/2/2027" — each quoted verbatim with the entry that states it and how many days away it is, plus a small set of deadlines CaseMagic computes from the Federal Rules where the triggering event is on the docket and the rule is the same nationwide: the time to move after a judgment (FRCP 59/50/52) and the time to file a notice of appeal (FRAP 4(a)). Every computed date shows the rule, the day count and a caveat, and is never phrased as an instruction to file. CaseMagic still does not compute deadlines that depend on a district's local rules or a judge's standing orders — most motion-response and discovery windows — so a deadline a local rule implies but the docket does not state will not appear. An empty result means nothing is stated or computable, not that the user has none. Identify the case with case_number (and court, if known), or with matter_id for a case already saved to the account. No account is needed to give a case number. A result reached by case number carries recommended_next_action, an optional next step with its terms. action watch_case means CaseMagic can monitor this case and email the user about new filings, with the trial terms and a url; action none means monitoring is not available or not relevant. Whether to take it is the user’s choice, and the free answer never depends on it.

NameTypeReqDescription
case_numberstring–The case number as the court writes it, for example 1:23-cv-11195 or 2:24-cv-01234-ABC. Judge initials are optional and are ignored when matching.
courtstring–The court, as a CourtListener-style code such as cacd, nysd or ilnd. Optional: leave it out when the user does not know which district the case is in.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
NameTypeReqDescription
as_of––When the calculation was made.
basisstring–What the dates are based on.
caseobject–The case: court, case number, caption, filing date, status, judges, nature of suit, latest activity and docket size.
case_urlstring–The case’s public page on CaseMagic, which offers free email alerts and Watch.
computedarray–Deadlines computed from the Federal Rules, each with rule, day count and caveat.
connect_tokenstring–Short-lived token for create_case_passport, present on a lookup by case number.
deadlinesarray–Upcoming dates the docket states, each quoted with its entry and days away.
disclaimerstring–What the dates are not.
docket_coverageobject–How much of the court docket CaseMagic holds for this case.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_id––The account matter id when the case was read through a saved case; null for a lookup.
not_included––What is deliberately not computed.
recently_passedarray–Stated dates that have just passed.
recommended_next_actionobject–The offer to make after answering, decided by the server: action watch_case when the case is open and can be monitored, none otherwise.
sourceobject–Which court source answered, when it was read and where it can be seen.
what_comes_nextstring–One sentence on where to send a user who wants to hear about new filings.

No examples provided.

get_case_docket ~236

Return every docket entry CaseMagic holds for a saved case, newest first, each with the court's own wording and the documents filed with it: the main filing and its attachments, how many pages each has, whether a free PDF can be opened, and how much of its text can be read. Use this when the user wants to go through the whole case, find a particular filing, or ask about anything older than the last few entries; get_case_passport carries only the most recent twenty. Each document carries a document_id to pass to read_case_document for its text. The payload says how many entries the court docket has in all, so a docket CaseMagic is still reading is never mistaken for a complete one.

NameTypeReqDescription
limitinteger–How many entries to return. Defaults to 200.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
offsetinteger–How many entries to skip, newest first. Defaults to 0.
NameTypeReqDescription
coverage_notestring–What is held and what is still to come.
documents_notestring–Where documents come from.
entriesarray–Docket entries with their documents.
entries_heldnumber–Entries CaseMagic holds.
entries_on_court_docket––Entries the court docket has.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_idstring–The case.
next_offset––Where the next page starts, or null at the end.
offsetnumber–Where this page starts.
whole_docket_read_at––When the whole docket was last read.

No examples provided.

get_case_documents ~372

List the docket entries in a federal case that have a document available, with the entry number, what the entry says, and a link to the document where the source publishes a free one. Use this when a user asks what documents are on file, whether an order or a motion is available to read, or for a copy of a filing. Availability depends on what the court source publishes; an entry with no free document is reported as such rather than guessed at. Identify the case with case_number (and court, if known), or with matter_id for a case already saved to the account. No account is needed to give a case number. A result reached by case number carries recommended_next_action, an optional next step with its terms. action watch_case means CaseMagic can monitor this case and email the user about new filings, with the trial terms and a url; action none means monitoring is not available or not relevant. Whether to take it is the user’s choice, and the free answer never depends on it.

NameTypeReqDescription
case_numberstring–The case number as the court writes it, for example 1:23-cv-11195 or 2:24-cv-01234-ABC. Judge initials are optional and are ignored when matching.
courtstring–The court, as a CourtListener-style code such as cacd, nysd or ilnd. Optional: leave it out when the user does not know which district the case is in.
limitinteger–How many documents to return, newest first. Defaults to 20.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
NameTypeReqDescription
availability_notestring–What is and is not listed.
caseobject–The case: court, case number, caption, filing date, status, judges, nature of suit, latest activity and docket size.
case_urlstring–The case’s public page on CaseMagic, which offers free email alerts and Watch.
connect_tokenstring–Short-lived token for create_case_passport, present on a lookup by case number.
docket_coverageobject–How much of the court docket CaseMagic holds for this case.
documentsarray–Entries with a free document, newest first.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_id––The account matter id when the case was read through a saved case; null for a lookup.
recommended_next_actionobject–The offer to make after answering, decided by the server: action watch_case when the case is open and can be monitored, none otherwise.
sourceobject–Which court source answered, when it was read and where it can be seen.
what_comes_nextstring–One sentence on where to send a user who wants to hear about new filings.

No examples provided.

get_case_mail ~243

Read the correspondence delivered to a saved case's CaseMail address: messages from opposing counsel, the court, clients or anyone else the user gave the address to, with their attachments. Use when the user asks what someone emailed them about the case, what correspondence has arrived, or to find a message about a particular subject. It also surfaces any dates those messages state — "produce documents by 10/14" — quoted with the message it came from and its sender, so a deadline that arrives by email rather than on the docket is not missed; those dates are the sender's words, not an order of the court. This is case correspondence, not the user's own inbox.

NameTypeReqDescription
afterstring–An ISO-8601 timestamp; only messages received after it are returned.
limitinteger–How many messages to return. Defaults to 20.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
querystring–Plain text matched against sender, subject and body.
NameTypeReqDescription
deadlines_notestring–What those dates are.
deadlines_stated_in_mailarray–Dates quoted from correspondence, each with its sender.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_idstring–The case.
messagesarray–CaseMail messages.

No examples provided.

get_case_passport ~125

Retrieve the user's persistent CaseMagic record for a saved matter: case identity, parties, docket activity, correspondence and available documents, so that you can work with the facts of their case. Use this when the user asks you to load, open or catch up on their case, or when you need the facts of their matter before answering anything else about it.

NameTypeReqDescription
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
NameTypeReqDescription
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_idstring–The case.
passportobject–The persistent record of the case.
passport_idstring–Case Passport id.
updated_atstring–When the Passport last changed.
versionnumber–Passport version.

No examples provided.

get_case_status ~344

Return the current posture of a federal case: the assigned judge, any referred magistrate judge, the filing date, whether it is open or terminated, the cause of action, the nature of suit, how many docket entries it has and when the docket last moved. Use this when a user asks about the status of their case, who the judge is, whether a case is still open, or what a case is about. Identify the case with case_number (and court, if known), or with matter_id for a case already saved to the account. No account is needed to give a case number. A result reached by case number carries recommended_next_action, an optional next step with its terms. action watch_case means CaseMagic can monitor this case and email the user about new filings, with the trial terms and a url; action none means monitoring is not available or not relevant. Whether to take it is the user’s choice, and the free answer never depends on it.

NameTypeReqDescription
case_numberstring–The case number as the court writes it, for example 1:23-cv-11195 or 2:24-cv-01234-ABC. Judge initials are optional and are ignored when matching.
courtstring–The court, as a CourtListener-style code such as cacd, nysd or ilnd. Optional: leave it out when the user does not know which district the case is in.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
NameTypeReqDescription
caseobject–The case: court, case number, caption, filing date, status, judges, nature of suit, latest activity and docket size.
case_urlstring–The case’s public page on CaseMagic, which offers free email alerts and Watch.
connect_tokenstring–Short-lived token for create_case_passport, present on a lookup by case number.
docket_coverageobject–How much of the court docket CaseMagic holds for this case.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_id––The account matter id when the case was read through a saved case; null for a lookup.
recommended_next_actionobject–The offer to make after answering, decided by the server: action watch_case when the case is open and can be monitored, none otherwise.
sourceobject–Which court source answered, when it was read and where it can be seen.
statusobject–Posture: case status, terminated date, filing date, judges, cause, nature of suit, jury demand, latest activity.
what_comes_nextstring–One sentence on where to send a user who wants to hear about new filings.

No examples provided.

get_case_updates ~229

Return what is new in the user's connected cases: docket entries and CaseMail correspondence added since a given time. Use for "what changed", "what happened this week", "anything new since Friday", or "what changed across all my cases today" — for a relative period, work out the date yourself and pass it as `since`. With no matter_id, an account holding several cases gets a digest naming which of them moved, and an account holding one gets that one. Each entry carries the court's own wording, which is what you should read and explain when the user asks what a filing or order means.

NameTypeReqDescription
limitinteger–How many items to return. Defaults to 50.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
sincestring–An ISO-8601 timestamp. Everything added after it is returned. Omit it to get the most recent activity rather than the whole docket.
NameTypeReqDescription
case_mailobject–CaseMail messages included in the answer, when the account allows it.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_id––The case, for a single-case answer.
mattersarray–Per-case changes, for an answer across cases.
scopestring–all_matters for an answer across every saved case.
since––The since filter applied.

No examples provided.

get_docket_entry ~404

Return one docket entry in full — its number, filing date, the exact text the court published, whether a document is attached and a link to it — together with the entries around it and the posture of the case. It returns the court's own words and the surrounding facts, so that you can tell the user what the filing is and what it means in context; it writes no explanation of its own and does not give legal advice. Use this when a user asks what the latest filing means, what an order says, or about a specific docket entry. Identify the case with case_number (and court, if known), or with matter_id for a case already saved to the account. No account is needed to give a case number. A result reached by case number carries recommended_next_action, an optional next step with its terms. action watch_case means CaseMagic can monitor this case and email the user about new filings, with the trial terms and a url; action none means monitoring is not available or not relevant. Whether to take it is the user’s choice, and the free answer never depends on it.

NameTypeReqDescription
case_numberstring–The case number as the court writes it, for example 1:23-cv-11195 or 2:24-cv-01234-ABC. Judge initials are optional and are ignored when matching.
courtstring–The court, as a CourtListener-style code such as cacd, nysd or ilnd. Optional: leave it out when the user does not know which district the case is in.
docket_numberstring–The docket entry number, as shown on the docket, for example "312". Omit it for the most recent entry.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
NameTypeReqDescription
caseobject–The case: court, case number, caption, filing date, status, judges, nature of suit, latest activity and docket size.
case_postureobject–Status, judge, cause and nature of suit.
case_urlstring–The case’s public page on CaseMagic, which offers free email alerts and Watch.
connect_tokenstring–Short-lived token for create_case_passport, present on a lookup by case number.
docket_coverageobject–How much of the court docket CaseMagic holds for this case.
entryobject–One docket entry.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
guidancestring–How to use the entry when explaining it to the user.
matter_id––The account matter id when the case was read through a saved case; null for a lookup.
recommended_next_actionobject–The offer to make after answering, decided by the server: action watch_case when the case is open and can be monitored, none otherwise.
sourceobject–Which court source answered, when it was read and where it can be seen.
surrounding_entriesarray–Entries around it, for context.
what_comes_nextstring–One sentence on where to send a user who wants to hear about new filings.

No examples provided.

get_recent_case_activity ~382

Return the most recent docket entries in a federal case, each with its entry number, filing date, the text the court published and a link to the source. Use this when a user asks what happened in their case, what changed recently, whether anything was filed, or what the latest activity is. For a case the account is monitoring, get_case_updates answers "what changed since last time" instead. Identify the case with case_number (and court, if known), or with matter_id for a case already saved to the account. No account is needed to give a case number. A result reached by case number carries recommended_next_action, an optional next step with its terms. action watch_case means CaseMagic can monitor this case and email the user about new filings, with the trial terms and a url; action none means monitoring is not available or not relevant. Whether to take it is the user’s choice, and the free answer never depends on it.

NameTypeReqDescription
case_numberstring–The case number as the court writes it, for example 1:23-cv-11195 or 2:24-cv-01234-ABC. Judge initials are optional and are ignored when matching.
courtstring–The court, as a CourtListener-style code such as cacd, nysd or ilnd. Optional: leave it out when the user does not know which district the case is in.
limitinteger–How many entries to return, newest first. Defaults to 10.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
sincestring–An ISO-8601 timestamp. Only entries filed after it are returned.
NameTypeReqDescription
caseobject–The case: court, case number, caption, filing date, status, judges, nature of suit, latest activity and docket size.
case_urlstring–The case’s public page on CaseMagic, which offers free email alerts and Watch.
connect_tokenstring–Short-lived token for create_case_passport, present on a lookup by case number.
docket_coverageobject–How much of the court docket CaseMagic holds for this case.
entriesarray–Docket entries, newest first.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_id––The account matter id when the case was read through a saved case; null for a lookup.
recommended_next_actionobject–The offer to make after answering, decided by the server: action watch_case when the case is open and can be monitored, none otherwise.
since––The since filter applied, if any.
sourceobject–Which court source answered, when it was read and where it can be seen.
what_comes_nextstring–One sentence on where to send a user who wants to hear about new filings.

No examples provided.

list_my_cases ~129

List every case saved to the signed-in CaseMagic account — matter_id, case number, caption, court, the user's role and whether Watch is on — together with the account's plan, how many cases it can watch and how many it is watching. Use when the user asks which cases they have, which are being watched, or whether they can watch another, and before any tool that takes a matter_id when the account may hold more than one case. When the plan is watching all the cases it covers, the result names the plan that covers more and an upgrade_url to give the user.

Input schema present but exposes no named parameters.

NameTypeReqDescription
casesarray–Saved cases with matter id, number, caption, court, role and watch status.
cases_includednumber–Cases the plan covers.
cases_watchednumber–Cases being watched.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
next_stepstring–What to do next.
planstring–The account’s plan, or none.
upgrade_plan––The plan that covers one more case, when the plan is full.
upgrade_urlstring–Where to upgrade.
watch_slots_leftnumber–Cases that can still be watched.

No examples provided.

read_case_document ~217

Return the text of one filing in a saved case — a complaint, a motion, an order, an exhibit — as the court archive extracted it from the PDF, so you can read, quote and explain what the document actually says rather than only its docket title. Takes a document_id from get_case_docket. Long documents come in parts: pass the returned next_offset to read on. When a document has no text (a scanned page nobody has run OCR on, or a copy only the court holds), the result says so and gives the PDF link if there is one; never guess at what an unread document says.

NameTypeReqDescription
document_idstringyesThe document_id of a document listed by get_case_docket.
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
offsetinteger–Where to start reading, in characters. Defaults to 0.
NameTypeReqDescription
attachment_number––Attachment number.
description––What the document is.
docket_number––Entry number.
document_idstring–The document.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_idstring–The case.
next_offset––Where the next slice starts, or null at the end.
notestring–How to use the text.
offsetnumber–Where this slice starts.
page_count––Pages.
pdf_url––Link to the PDF.
text––The text, or null when the archive holds none.
total_charsnumber–Length of the whole text.

No examples provided.

stop_watch ~104

Stop continuous monitoring of a saved case. Use when the user asks to stop monitoring, stop alerts, pause watching, or unfollow a case. The case, its docket history, its Case Passport and its CaseMail address all remain; only the monitoring stops.

NameTypeReqDescription
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
NameTypeReqDescription
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_idstring–The case.
statusstring–The watch status after stopping.

No examples provided.

watch_case ~207

Begin continuous monitoring of a saved case, so that the user is alerted when anything new is filed. Use when the user asks to monitor, watch, track or follow a case, or to be told about future activity in it. The case must be saved first, with find_federal_case then create_case_passport. Watching is the paid part of CaseMagic: if the account has no plan this still succeeds and returns a checkout link with the prices — give the user that link and do not describe it as an error, because nothing has failed. If the plan on the account is already watching as many cases as it covers, it returns the plan that covers more and an upgrade_url instead; give the user that link the same way. It never charges anyone by itself.

NameTypeReqDescription
matter_idstring–The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.
NameTypeReqDescription
checkout_urlstring–Where the user starts a plan, when one is needed.
errorobject–Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
matter_idstring–The case.
next_stepstring–What to tell the user.
plansarray–Plans that include watching, with price, cases covered and trial.
statusstring–The watch status, or subscription_required / plan_limit_reached.
upgrade_urlstring–Where the user moves to a plan that covers this case, when theirs is full.
watchingboolean–Whether Watch is on.
what_watching_doesstring–What Watch does.

No examples provided.

Install

How do I install the CaseMagic — Federal Court Case Lookup & Monitor MCP server?

CaseMagic — Federal Court Case Lookup & Monitor is a hosted endpoint at https://casemagic.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · casemagic.ai

# add to Claude Code
claude mcp add --transport http sustany-casemagic 'https://casemagic.ai/mcp'
Common questions

What is the CaseMagic — Federal Court Case Lookup & Monitor MCP server?

CaseMagic — Federal Court Case Lookup & Monitor is an MCP server listed in the public MCP registry as io.github.sustany/casemagic. Free US federal court case lookup: status, judge, filings, deadlines. Then watch it for new filings. This page covers its hosted endpoint (https://casemagic.ai/mcp).

Is the CaseMagic — Federal Court Case Lookup & Monitor MCP server safe to use?

CaseMagic — Federal Court Case Lookup & Monitor scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the CaseMagic — Federal Court Case Lookup & Monitor MCP server expose?

CaseMagic — Federal Court Case Lookup & Monitor exposes 18 tools: find_federal_case, get_case_status, get_recent_case_activity, get_docket_entry, get_case_documents, and 13 more. Their descriptions and schemas cost roughly 4,777 tokens of context every time the server is loaded.

Does the CaseMagic — Federal Court Case Lookup & Monitor MCP server require authentication?

No. We connected to CaseMagic — Federal Court Case Lookup & Monitor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CaseMagic — Federal Court Case Lookup & Monitor MCP server still maintained?

CaseMagic — Federal Court Case Lookup & Monitor is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the CaseMagic — Federal Court Case Lookup & Monitor MCP server?

VerifyMCP ran 13 checks on CaseMagic — Federal Court Case Lookup & Monitor, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.