Data Collection
caldogbiteevidence.com
Provides a California Dog Bite Evidence Checklist to guide the collection of evidence for dog bite cases.
ENDPOINT 1
https://caldogbiteevidence.com/api/mcp
MCP server metadata
- Name
- california-dog-bite-evidence-checklist
- Version
- 1.0.0
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.
Known tools 1
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.california-dog-bite-evidence-checklist]
url = "https://caldogbiteevidence.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"california-dog-bite-evidence-checklist": {
"type": "http",
"url": "https://caldogbiteevidence.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: california-dog-bite-evidence-checklist
Remote MCP URL: https://caldogbiteevidence.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"california-dog-bite-evidence-checklist": {
"url": "https://caldogbiteevidence.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"california-dog-bite-evidence-checklist": {
"type": "http",
"url": "https://caldogbiteevidence.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "california-dog-bite-evidence-checklist",
"transport": "streamable-http",
"url": "https://caldogbiteevidence.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.