Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

California Tax Appeals

NPM · @PIPEWORX/MCP-CALIFORNIA-TAX-APPEALS · 2 COMPONENTS

California Office of Tax Appeals (OTA) opinions — search by statute section/topic across issued…

+3 this week 81 Trust /100

Last scanned (7 hours ago)

Scores higher than 69% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-california-tax-appeals). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 753 tokens (~376/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +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.

  • 1 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 +1
    • Security disclosure: fail → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 78

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-california-tax-appeals@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-california-tax-appeals
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-california-tax-appeals/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606664354
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7c514bc379a35713a5df4daf2916a7180cee25a66cf229ef5c1224ee7302716337e82a7f6a09b5d0d6a7176edf70fb9f8f12054c845079992c7efe82d

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~694 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ca_ota_opinion_lookup ~187

Look up a California Office of Tax Appeals opinion by its OTA citation (e.g. "2020-OTA-263P" for a Precedential opinion, "2020-OTA-374" for a Nonprecedential one) -- fetches the opinion PDF live and returns the full text, exact date issued, OTA's internal case number, tax category, precedential status, OTA's issue tag, and statute citations found in the text (best-effort, R&TC/Cal. Code Regs./IRC shapes). Sourced from ota.ca.gov.

NameTypeReqDescription
citestringyesOTA opinion citation, e.g. "2020-OTA-263P", "2022-OTA-375P", "2020-OTA-374". Case- and spacing-insensitive; the trailing "P" (precedential marker) may be omitted.

No output schema declared.

No examples provided.

ca_ota_search ~507

Find California Office of Tax Appeals (OTA) opinions by statute citation or topic keyword (e.g. "residency", "innocent spouse", "17014", "17951-4", "generative AI") -- returns citation, title, date, tax category (Franchise/Income vs Business Tax), precedential status, and OTA's own one-line issue/statute tag, most recent first with an exact phrase match ranked above a looser match. Matches every word of `query` (any order), with a small bidirectional synonym table for OTA's own shorthand (e.g. "GenAI" <-> "generative AI" <-> "AI" <-> "artificial intelligence"). Use `year` for "opinions from 2026" rather than putting the year in `query` text -- it almost never appears inside an opinion's title or Issues tag. PARTIAL: this searches opinion titles and OTA's published "Issues" tag only, not full opinion text (OTA publishes no full-text search). For full text and all cited provisions of a specific opinion, use ca_ota_opinion_lookup. Sourced from ota.ca.gov's own opinion listing pages.

NameTypeReqDescription
categorystring–Optional filter: "fit" (Franchise and Income Tax, FTB-administered) or "bt" (Business Tax, CDTFA-administered: sales/use, excise, etc).
limitnumber–Max opinions to return, default 25, max 100.
precedential_onlyboolean–If true, only return opinions OTA has designated Precedential (binding on future OTA panels). Default false (returns both).
querystring–A topic keyword (e.g. "residency", "penalties", "innocent spouse", "generative AI") or a statute citation/number (e.g. "17014" or "R&TC 19045"). May be omitted if you only need `year`/`category`/`pre…
yearnumber–Optional filter: only opinions issued in this calendar year, e.g. 2026. Prefer this over putting the year inside `query` -- OTA's own title/Issues tag almost never repeats the year.

No output schema declared.

No examples provided.

Install

How do I install the California Tax Appeals MCP server?

California Tax Appeals runs locally as an npm package, launched with npx -y @pipeworx/mcp-california-tax-appeals. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-california-tax-appeals

# add to Claude Code
claude mcp add pipeworx-io-california-tax-appeals -- npx -y @pipeworx/mcp-california-tax-appeals
Common questions

What is the California Tax Appeals MCP server?

California Tax Appeals is an MCP server listed in the public MCP registry as io.github.pipeworx-io/california-tax-appeals. California Office of Tax Appeals (OTA) opinions, search by statute section/topic across issued… This page covers its npm package (@pipeworx/mcp-california-tax-appeals).

Is the California Tax Appeals MCP server safe to use?

California Tax Appeals scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Tax Appeals MCP server expose?

California Tax Appeals exposes 2 tools: ca_ota_search, ca_ota_opinion_lookup. Their descriptions and schemas cost roughly 694 tokens of context every time the server is loaded.

Is the California Tax Appeals MCP server still maintained?

California Tax Appeals is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the California Tax Appeals MCP server under?

California Tax Appeals declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.