# 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

- Trust score: 65/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `caldogbiteevidence.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/janoliverautomation-stack-caldogbiteevidence-com/api-mcp.md), [page](https://verifymcp.io/servers/janoliverautomation-stack-caldogbiteevidence-com/api-mcp)

## Channel facts

- Endpoint: `https://caldogbiteevidence.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 53/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http janoliverautomation-stack-caldogbiteevidence-com 'https://caldogbiteevidence.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "janoliverautomation-stack-caldogbiteevidence-com": {
      "url": "https://caldogbiteevidence.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "janoliverautomation-stack-caldogbiteevidence-com": {
      "type": "http",
      "url": "https://caldogbiteevidence.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.janoliverautomation-stack-caldogbiteevidence-com]
url = "https://caldogbiteevidence.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "janoliverautomation-stack-caldogbiteevidence-com": {
      "type": "remote",
      "url": "https://caldogbiteevidence.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add janoliverautomation-stack-caldogbiteevidence-com --url 'https://caldogbiteevidence.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  janoliverautomation-stack-caldogbiteevidence-com:
    url: "https://caldogbiteevidence.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "janoliverautomation-stack-caldogbiteevidence-com": {
      "Transport": "http",
      "Url": "https://caldogbiteevidence.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add janoliverautomation-stack-caldogbiteevidence-com -t streamable-http -u 'https://caldogbiteevidence.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "janoliverautomation-stack-caldogbiteevidence-com": {
      "type": "http",
      "url": "https://caldogbiteevidence.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 58, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (1)

### `check_dog_bite_evidence` (~735 tokens)

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.

Input parameters:

- `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".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/janoliverautomation-stack-caldogbiteevidence-com/api-mcp#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 64
- 2026-09-17: 63
- 2026-09-16: 63
- 2026-09-15: 62
- 2026-09-14: 62
- 2026-09-13: 61
- 2026-09-12: 61
- 2026-09-11: 60
- 2026-09-10: 60
- 2026-09-09: 60
- 2026-09-08: 59
- 2026-09-07: 59
- 2026-09-06: 58
- 2026-09-05: 58
- 2026-09-04: 57

## Common questions

### 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 65 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://caldogbiteevidence.com/api/mcp
- Website: https://caldogbiteevidence.com/
- Changelog RSS feed: https://verifymcp.io/servers/janoliverautomation-stack-caldogbiteevidence-com/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/janoliverautomation-stack-caldogbiteevidence-com/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/janoliverautomation-stack-caldogbiteevidence-com/api-mcp