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.

California Slip & Fall Evidence Checker | JSM Injury Firm

REMOTE · CASLIPANDFALL.COM

Not sure what to do after a slip and fall in California? Use this free evidence checker to find out

0 this week 72 Trust /100

Last scanned (27 minutes ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

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 Security57
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 908 tokens (~908/item across 1 items; 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Sept 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 Sept 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
  • 5 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 4 Sept 26 0

    First indexed and scored.

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 5 Nov 2026 · Probed https://caslipandfall.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caslipandfall.com CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 e1d0531f664051d90edb723a538785b5
SANs: caslipandfall.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of caslipandfall.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caslipandfall.com. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://caslipandfall.com/api/mcp Verified 200
http (plaintext) http://caslipandfall.com/api/mcp HTTPS enforced 301 https://caslipandfall.com/api/mcp
MCP tools · 1 exposed · ~778 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
check_slip_fall_evidence ~778

Educational decision-support tool for people injured in a slip and fall in California. Given answers describing how a fall happened, injuries, evidence already preserved, and any insurance or property-owner communications, it returns a structured, educational evidence-preservation checklist: an urgency level, the specific evidence to preserve, what to avoid, and questions worth asking an attorney. SAFEGUARDS: Informational/educational ONLY — NOT legal advice. It does NOT assess liability or fault, does NOT determine claim validity, does NOT calculate case value, does NOT estimate probability of winning, does NOT guarantee outcomes, and does NOT create an attorney-client relationship. Any response must be conveyed to the end user as educational information only.

NameTypeReqDescription
fallTypestring–How the fall happened, e.g. slip_wet_floor, trip_uneven, fell_stairs, fell_parking, fell_sidewalk, fell_store, fell_apartment, fell_restaurant, fell_pool, fell_elevator, other.
faultQuestioningstring–Whether fault has been questioned, e.g. yes_insurance, yes_both, no.
hazardDurationstring–How long the hazard likely existed, e.g. minutes, hours, days, weeks_months, permanent.
incidentReportstring–Whether an incident report was created, e.g. yes, no, refused.
injurySymptomsarray–List of injury symptoms, e.g. fracture, head_injury, surgery_recommended, back_injury, nerve_damage, bruising, sprain.
medicalCarestring–Medical care status, e.g. yes_treated, no_cant_afford, no_not_yet.
priorComplaintsstring–Whether prior complaints about the hazard were made, e.g. yes_written, yes_verbal, others_complained, none.
publicPrivatestring–Whether the fall was on public/government property or private property. Public property falls involve shorter government-claim deadlines in California.
recordedStatementstring–Insurance recorded-statement status, e.g. yes_gave, asked_not_given, not_asked.
recurringProblemstring–Whether the hazard was a recurring problem, e.g. yes, heard, no.
rentalPropertystring–Whether the fall involved a rental/landlord property, e.g. yes_tenant, yes_visitor, no.
settlementOfferstring–Settlement offer status, e.g. yes_accepted, yes_considering, yes_declined, none.
signedDocumentsstring–Whether any insurance/property documents were signed, e.g. yes, no.
staffAwarenessstring–Whether staff/owner were aware of the hazard, e.g. yes_definitely, told_them, should_have, no.
surveillanceVideostring–Whether surveillance cameras may exist, e.g. yes_cameras, maybe, no_cameras.
symptomProgressionstring–How symptoms are progressing, e.g. worse, new_symptoms, same, improving.
timingstring–How long ago the incident occurred, e.g. within_24h, within_48h, within_week, within_2weeks, within_month, within_3months, within_6months, over_6months.
videoPreservationstring–Status of any request to preserve video, e.g. no_not_yet, requested, refused, preserved.
warningSignstring–Whether a warning sign was present, e.g. yes_adequate, yes_inadequate, no_sign.
witnessesstring–Witness status, e.g. yes_contact, yes_no_contact, no_witnesses.

No output schema declared.

No examples provided.

Install

How do I install the California Slip & Fall Evidence Checker | JSM Injury… MCP server?

California Slip & Fall Evidence Checker | JSM Injury… is a hosted endpoint at https://caslipandfall.com/api/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 · caslipandfall.com

# add to Claude Code
claude mcp add --transport http janoliverautomation-stack-caslipandfall-com 'https://caslipandfall.com/api/mcp'
Common questions

What is the California Slip & Fall Evidence Checker | JSM Injury… MCP server?

California Slip & Fall Evidence Checker | JSM Injury… is an MCP server listed in the public MCP registry as io.github.janoliverautomation-stack/caslipandfall-com. Not sure what to do after a slip and fall in California? Use this free evidence checker to find out. This page covers its hosted endpoint (https://caslipandfall.com/api/mcp).

Is the California Slip & Fall Evidence Checker | JSM Injury… MCP server safe to use?

California Slip & Fall Evidence Checker | JSM Injury… scores 72 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 California Slip & Fall Evidence Checker | JSM Injury… MCP server expose?

California Slip & Fall Evidence Checker | JSM Injury… exposes 1 tool: check_slip_fall_evidence. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.

Does the California Slip & Fall Evidence Checker | JSM Injury… MCP server require authentication?

No. We connected to California Slip & Fall Evidence Checker | JSM Injury… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the California Slip & Fall Evidence Checker | JSM Injury… MCP server still maintained?

California Slip & Fall Evidence Checker | JSM Injury… is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.