Skip to content

California Dog Bite Evidence Checklist | JSM Injury Firm

by janoliverautomation-stack · remote · no sign-in to list tools · v1.0.0 · published by GitHub user janoliverautomation-stack

Bitten or injured by a dog in California? Use this private checklist to understand what evidence to

Changes · 1
CompareRegistry entry

1 tool: 1 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http caldogbiteevidence-com https://caldogbiteevidence.com/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Changes things 1Claude Code: ask
  • check_dog_bite_evidenceCalifornia Dog Bite Evidence Checklist.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http caldogbiteevidence-com https://caldogbiteevidence.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__caldogbiteevidence-com__check_dog_bite_evidence"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as caldogbiteevidence-com. Review it before you use it.