California Codes — the text of California statutes, by citation.
MCPpedia last refreshed this data
io.github.pipeworx-io/california-code is an MCP server that california Codes — the text of California statutes, by citation. Its tool list has not been published yet over http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"california-code": {
"url": "https://gateway.pipeworx.io/california-code/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
California Codes — the text of California statutes, by citation.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @pipeworx/mcp-california-code against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in legal
Korean law: statutes, precedents, ordinances, treaties and citation verification (법제처 API).
Supplier lien and notice deadlines by project scope. Public lien guides for all 50 states and DC.
Missouri Revised Statutes — state statutes by citation.
Nevada Revised Statutes — state statutes by citation.
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/california-code and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The text of California's 29 codes. Give it PEN and 187, get back the murder
statute.
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
None. Both tools are keyless.
The probe that led to this pack (docs/state-law-probe.md) found California
publishing a ~1.0 GB bulk drop daily and sized the work as a
CourtListener-style mirror. It doesn't need to be one — leginfo serves any
section directly:
?lawCode=PEN§ionNum=187 → "187. (a) Murder is the unlawful killing…"
So this is the us-code shape, not the CourtListener shape: no storage, no
recurring cost, no quarterly refresh obligation. That matters well beyond
California — it means the other 49 states are 49 small packs rather than 49
mirrors, which changes whether the long tail is worth building at all.
| Tool | Returns |
|---|---|
ca_code_section | Full statutory text, where it sits in the code, and when it was last amended |
ca_codes | The 29 codes and their subjects, filterable ("divorce" → FAM) |
ca_code_section({code: "PEN", section: "187"})
→ located_in: PART 1 → TITLE 8 → CHAPTER 1. Homicide
last_affected: Amended by Stats. 2023, Ch. 260, Sec. 14. (SB 345)
section_not_found. Treating that page as an answer would report
"no such law" as though it were the law.187(a) renders the same empty
shell upstream, so it's stripped to 187 and the response says so.last_affected is per section, which is better currency than the federal
code can offer — us-code can only tell you which annual edition the text
came from.us-code — federal statutes, the same citation-resolver shapecourt-listener — California cases interpreting these sections, with full textrecap — federal filingshttps://leginfo.legislature.ca.gov/ — California Legislative Information. California statutes are public record.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"california-code": {
"url": "https://gateway.pipeworx.io/california-code/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/california-code/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url
... [View full README on GitHub](https://github.com/pipeworx-io/mcp-california-code#readme)