https://caldogbiteevidence.com/api/mcp ↗
Bitten or injured by a dog in California? Use this private checklist to understand what evidence to
California Dog Bite Evidence Checklist | JSM Injury Firm is a remote MCP server published at caldogbiteevidence.com. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 642 ms, a delay an agent will notice. It offers a narrow, focused set of 1 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
check_dog_bite_evidence — Parameters are all optional with no required fields specifiedcheck_dog_bite_evidence — Parameter names lack contextual specificity (e.g., 'insurance_info' is vague)check_dog_bite_evidence — No error handling or validation rules documented| Run | Era | Modern |
|---|
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
check_dog_bite_evidenceCalifornia Dog Bite Evidence Checklist. Given a plain-language description of a dog bite or animal attack in California (how it happened, who was injured, when/where, dog-owner and insurance situation, injuries and medical care, and what evidence exists), returns a personalized, educational checklist: evidence to preserve now, what to avoid, plain-language questions that may be worth attorney review, and an educational urgency indicator. Educational evidence-preservation support only. This tool does NOT provide legal advice, does NOT assess liability or fault, does NOT determine whether you have a valid claim or case, does NOT estimate case value, does NOT predict the probability of winning, and does NOT guarantee compensation or any legal outcome. It does not create an attorney-client rel
incident_typestringwho_injuredstringwhen_happenedstringwhere_happenedstringinsurance_infostringproperty_involvedstringinjuriesarraymedical_carearrayvideo_evidencearrayinsurance_contactedstringrecorded_statementstringsettlement_offeredstringsigned_anythingstringworkingstringDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-janoliverautomation-stack-caldogbiteevidence-com)<a href="https://mcpmetrics.io/servers/io-github-janoliverautomation-stack-caldogbiteevidence-com"><img src="https://mcpmetrics.io/badge/io.github.janoliverautomation-stack/caldogbiteevidence-com/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Not sure what to do after a slip and fall in California? Use this free evidence checker to find out
Bitcoin research for AI agents: free answers, claim verification, evidence, and timelines.
Chinese supplier verification via Remote MCP; free resolve, paid Basic/Full evidence via x402.
Your personal action-item list — what you owe and what you're owed. AI proposes; you approve.
Signed citation-integrity reports + retraction-checked evidence packs, paid per call via x402/USDC.
Read-only observable merchant evidence for people and agents, without scores or safety verdicts.
| ms |
|---|
| Legacy |
|---|
| ms |
|---|
| Versions |
|---|
| 2026-09-13 01:33:33 | Legacy | 200 | 708 | 200 | 642 | 2024-11-05 |
| 2026-09-12 23:31:36 | Legacy | 200 | 642 | 200 | 629 | 2024-11-05 |
| 2026-09-12 21:29:15 | Legacy | 200 | 257 | 200 | 629 | 2024-11-05 |
| 2026-09-12 19:27:29 | Legacy | 200 | 690 | 200 | 642 | 2024-11-05 |
| 2026-09-12 17:24:09 | Legacy | 200 | 606 | 200 | 651 | 2024-11-05 |
| 2026-09-12 15:21:42 | Legacy | 200 | 719 | 200 | 698 | 2024-11-05 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.