California Dog Bite Evidence Checklist | JSM Injury Firm

io.github.janoliverautomation-stackPublished by GitHub account janoliverautomation-stackv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A remote MCP endpoint from a California injury firm that walks an assistant through a dog bite evidence checklist.

What you can do
The server is a remote endpoint at caldogbiteevidence.com offered by JSM Injury Firm. Its stated purpose is to help someone bitten or injured by a dog in California understand what evidence to gather, presented as a private checklist. No tools are listed in the manifest, so the exact operations the assistant can call are not documented here.
When to use it
Consider it when a user in California has been bitten or injured by a dog and wants guidance on what evidence to collect. It is a narrow, single-topic resource rather than a general-purpose tool.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to the provider's endpoint. No authentication, environment variables, or headers are declared.
Before you install
The endpoint is operated by an injury law firm, so the checklist may be oriented toward that firm's services and could function as a lead-generation channel; treat its output as general information, not legal advice. No credentials are requested, and no write, send, or delete actions are described.

Installation

In SourceWeft

  1. Open California Dog Bite Evidence Checklist | JSM Injury Firm in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.janoliverautomation-stack%2Fcaldogbiteevidence-com/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "california-dog-bite-evidence-checklist-j": {
      "type": "http",
      "url": "https://caldogbiteevidence.com/api/mcp"
    }
  }
}

Tools

1

check_dog_bite_evidence

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.

Parametersworkinginjurieswho_injuredmedical_careincident_typewhen_happenedinsurance_infovideo_evidencewhere_happenedsigned_anythingproperty_involvedrecorded_statement+2 more

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.