mcp-registry/io.github.janoliverautomation-stack/caslipandfall-com · v1.0.0
As of 2026-10-26 18:46 UTC, the Janoliverautomation Stack Caslipandfall Com MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Not sure what to do after a slip and fall in California? Use this free evidence checker to find out
Point your MCP client at this streamable-http endpoint: https://caslipandfall.com/api/mcp
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.janoliverautomation-stack%2Fcaslipandfall-com/fixes
{
"name": "check_slip_fall_evidence",
"description": "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 faul",
"inputSchema": {
"type": "object",
"properties": {
"timing": {
"type": "string",
"description": "How long ago the incident occurred, e.g. within_24h, within_48h, within_week, within_2weeks, within_month, within_3months, within_6months, over_6months."
},
"fallType": {
"type": "string",
"description": "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."
},
"witnesses": {
"type": "string",
"description": "Witness status, e.g. yes_contact, yes_no_contact, no_witnesses."
},
"medicalCare": {
"type": "string",
"description": "Medical care status, e.g. yes_treated, no_cant_afford, no_not_yet."
},
"warningSign": {
"type": "string",
"description": "Whether a warning sign was present, e.g. yes_adequate, yes_inadequate, no_sign."
},
"publicPrivate": {
"enum": [
"public",
"private"
],
"type": "string",
"description": "Whether the fall was on public/government property or private property. Public property falls involve shorter government-claim deadlines in California."
},
"hazardDuration": {
"type": "string",
"description": "How long the hazard likely existed, e.g. minutes, hours, days, weeks_months, permanent."
},
"incidentReport": {
"type": "string",
"description": "Whether an incident report was created, e.g. yes, no, refused."
},
"injurySymptoms": {
"type": "array",
"items": {
"type": "string"
},
"description": "List of injury symptoms, e.g. fracture, head_injury, surgery_recommended, back_injury, nerve_damage, bruising, sprain."
},
"rentalProperty": {
"type": "string",
"description": "Whether the fall involved a rental/landlord property, e.g. yes_tenant, yes_visitor, no."
},
"staffAwareness": {
"type": "string",
"description": "Whether staff/owner were aware of the hazard, e.g. yes_definitely, told_them, should_have, no."
},
"priorComplaints": {
"type": "string",
"description": "Whether prior complaints about the hazard were made, e.g. yes_written, yes_verbal, others_complained, none."
},
"settlementOffer": {
"type": "string",
"description": "Settlement offer status, e.g. yes_accepted, yes_considering, yes_declined, none."
},
"signedDocuments": {
"type": "string",
"description": "Whether any insurance/property documents were signed, e.g. yes, no."
},
"faultQuestioning": {
"type": "string",
"description": "Whether fault has been questioned, e.g. yes_insurance, yes_both, no."
},
"recurringProblem": {
"type": "string",
"description": "Whether the hazard was a recurring problem, e.g. yes, heard, no."
},
"recordedStatement": {
"type": "string",
"description": "Insurance recorded-statement status, e.g. yes_gave, asked_not_given, not_asked."
},
"surveillanceVideo": {
"type": "string",
"description": "Whether surveillance cameras may exist, e.g. yes_cameras, maybe, no_cameras."
},
"videoPreservation": {
"type": "string",
"description": "Status of any request to preserve video, e.g. no_not_yet, requested, refused, preserved."
},
"symptomProgression": {
"type": "string",
"description": "How symptoms are progressing, e.g. worse, new_symptoms, same, improving."
}
},
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true
},
"title": "California Slip & Fall Evidence Checker"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.janoliverautomation-stack/caslipandfall-com"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.janoliverautomation-stack/caslipandfall-com"}) over MCP.
check_slip_fall_evidence ~987 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.janoliverautomation-stack%2Fcaslipandfall-com?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.janoliverautomation-stack%2Fcaslipandfall-com?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.janoliverautomation-stack%2Fcaslipandfall-com.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.janoliverautomation-stack%2Fcaslipandfall-com.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.janoliverautomation-stack%2Fcaslipandfall-com?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:bfc42377b23a02cc…, first seen 2026-10-17, included at leaf 9370 of 74,811. Version history · verify what your client received.
Compare: most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:46 UTC, the Janoliverautomation Stack Caslipandfall Com MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Janoliverautomation Stack Caslipandfall Com MCP server advertises 1 tool, including check_slip_fall_evidence.
Point your MCP client at this streamable-http endpoint: https://caslipandfall.com/api/mcp
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.