California Dog Bite Evidence Checklist | JSM Injury Firm
REMOTE · CALDOGBITEEVIDENCE.COM
Bitten or injured by a dog in California? Use this private checklist to understand what evidence to
Available components
Last scanned (9 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 817 tokens (~817/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
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 71
- 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.
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://caldogbiteevidence.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=caldogbiteevidence.com | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c5c6d99effdbda950e0831ec68738801 |
| SANs: caldogbiteevidence.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 caldogbiteevidence.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| caldogbiteevidence.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://caldogbiteevidence.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://caldogbiteevidence.com/api/mcp | HTTPS enforced | 301 | https://caldogbiteevidence.com/api/mcp |
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 →
check_dog_bite_evidence ~735
California 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 relationship. Only an attorney can evaluate the facts of your specific situation.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_type | string | – | Type of incident, e.g. "Dog bite that broke the skin", "Dog knocked me down", "Dog attacked my child", "Dog attacked my pet and I was also injured", "Other animal attack". |
| injuries | array | – | Injuries present, e.g. "Facial injury", "Scarring or disfigurement", "Nerve damage/numbness", "Infection concern", "Emotional trauma/fear/anxiety". |
| insurance_contacted | string | – | Whether an insurance adjuster has contacted the user, e.g. "Yes", "No", "Not sure". |
| insurance_info | string | – | Dog-owner insurance status, e.g. "Yes", "No", "They said they have no insurance", "They are avoiding me", "They offered to pay cash", "I have not asked yet". |
| medical_care | array | – | Medical care received, e.g. "Emergency room", "Urgent care", "Primary doctor", "None yet". |
| property_involved | string | – | Whether the incident happened at a property controlled by someone other than the dog owner (landlord, apartment, business). |
| recorded_statement | string | – | Recorded statement status, e.g. "Yes", "They asked but I have not done it", "No". |
| settlement_offered | string | – | Settlement offer status, e.g. "Yes", "Insurance offer", "Informal cash offer from owner", "No". |
| signed_anything | string | – | Whether the user signed or was asked to sign anything, e.g. "Yes", "I was asked to sign", "No". |
| video_evidence | array | – | Possible video/camera evidence sources, e.g. "Ring/doorbell camera", "Business security camera", "Bystander phone video", "Not sure". |
| when_happened | string | – | When it happened, e.g. "Today", "Yesterday", "Within the last 7 days", "Within the last 30 days", "1–6 months ago", "6–24 months ago", "More than 2 years ago", "Not sure". |
| where_happened | string | – | Where it happened, e.g. "Neighbor's home", "Apartment complex", "Delivery route", "Public sidewalk or street". |
| who_injured | string | – | Who was injured, e.g. "Me", "My child", "Me and my child were injured", "A delivery worker / employee", "Multiple people were injured". |
| working | string | – | Whether the user was working (e.g. delivery/gig work) when injured, e.g. "Yes, delivering packages", "No", "Not sure". |
No output schema declared.
No examples provided.
How do I install the California Dog Bite Evidence Checklist | JSM Injury Firm MCP server?
California Dog Bite Evidence Checklist | JSM Injury Firm is a hosted endpoint at https://caldogbiteevidence.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 · caldogbiteevidence.com
claude mcp add --transport http janoliverautomation-stack-caldogbiteevidence-com 'https://caldogbiteevidence.com/api/mcp'
What is the California Dog Bite Evidence Checklist | JSM Injury Firm MCP server?
California Dog Bite Evidence Checklist | JSM Injury Firm is an MCP server listed in the public MCP registry as io.github.janoliverautomation-stack/caldogbiteevidence-com. Bitten or injured by a dog in California? Use this private checklist to understand what evidence to. This page covers its hosted endpoint (https://caldogbiteevidence.com/api/mcp).
Is the California Dog Bite Evidence Checklist | JSM Injury Firm MCP server safe to use?
California Dog Bite Evidence Checklist | JSM Injury Firm scores 71 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 Dog Bite Evidence Checklist | JSM Injury Firm MCP server expose?
California Dog Bite Evidence Checklist | JSM Injury Firm exposes 1 tool: check_dog_bite_evidence. Their descriptions and schemas cost roughly 735 tokens of context every time the server is loaded.
Does the California Dog Bite Evidence Checklist | JSM Injury Firm MCP server require authentication?
No. We connected to California Dog Bite Evidence Checklist | JSM Injury Firm without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the California Dog Bite Evidence Checklist | JSM Injury Firm MCP server still maintained?
California Dog Bite Evidence Checklist | JSM Injury Firm 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.