io.github.christianclaudio/taxcode
PYPI · MCP-SERVER-TAXCODE · 2 COMPONENTS
MCP server for US Federal, territorial, and state tax law and compliance.
Available components
Last scanned (9 hours ago)
Scores higher than 79% of PyPI servers
Category Finance and Payments
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 Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to christianclaudio/mcp-server-taxcode). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1074 tokens (~119/item across 9 items; 8 tools + 1 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 8% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 18 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Schema quality: 82 → 99 ▼ functional
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 8% ▲ functional
- Tool coverage: 0% → 6% ▲ functional
- Package version: 0.6.0 → 0.7.1 functional
- Package version: 0.6.0 → 0.7.0 functional
- Package version: 0.6.0 → 0.6.1 functional
- 16 Oct 26 +15
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.5.0 → 0.6.0 functional
- Package version: 0.5.0 → 0.5.1 functional
- 15 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.3 → 0.5.0 functional
- 14 Oct 26 +13
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fair functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 0 functional
- 13 Oct 26 48
First indexed and scored.
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 18 Oct 2026 · Analysed pypi/mcp-server-taxcode@0.7.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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | christianclaudio/mcp-server-taxcode |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/christianclaudio/mcp-server-taxcode/.github/workflows/release.yml@refs/tags/v0.7.1 |
| Rekor log index | 3297367270 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:19f554ee21708129e00be29b86d203b8b36ff21ba0b77c52ff0454609a302314 |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
| build_hook | unreviewed | tool.hatch.version.source |
Background: Why install scripts are a supply-chain risk →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compliance_calculate_built_in_gain_sourcing Compliance Calculate Built In Gain Sourcing ~105
Calculate US vs PR capital gain sourcing under Treas. Reg. § 1.937-2(f) (10-year rule).
| Name | Type | Req | Description |
|---|---|---|---|
| adjusted_basis | – | – | – |
| days_held_as_resident | – | – | – |
| fmv_on_residency_date | – | – | – |
| is_marketable | boolean | yes | – |
| total_days_held | – | – | – |
| total_gain | number | yes | – |
| years_since_residency | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compliance_evaluate_georgia_residency Compliance Evaluate Georgia Residency ~171
Evaluate Georgia statutory residency criteria under O.C.G.A. § 48-7-1(10) and Ga. Comp. R. & Regs. r. 560-7-3-.01, and compute state income tax.
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | – | – |
| days_present_ga | integer | yes | – |
| federal_agi | number | – | – |
| filing_status | string | – | – |
| ga_driver_license_active | boolean | – | – |
| ga_homestead_exemption_claimed | boolean | – | – |
| ga_voter_registration_active | boolean | – | – |
| is_domiciled_in_ga | boolean | – | – |
| maintains_permanent_abode_ga | boolean | – | – |
| retirement_income | number | – | – |
| tax_year | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compliance_evaluate_pr_bona_fide_residency Compliance Evaluate Pr Bona Fide Residency ~162
Evaluate statutory criteria for PR bona fide residency under IRC § 937 and 26 CFR § 1.937-1. Its reporting_requirements say when IRS Form 8898 must be filed: in the tax year you became or stopped being a bona fide PR resident, if your worldwide gross income is more than $75,000 (IRS Instructions for Form 8898).
| Name | Type | Req | Description |
|---|---|---|---|
| closer_connection_jurisdiction | string | – | – |
| days_present_pr | integer | yes | – |
| days_present_us | integer | yes | – |
| has_us_tax_home | boolean | – | – |
| prior_year_1_pr_days | integer | – | – |
| prior_year_2_pr_days | integer | – | – |
| tax_year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compliance_evaluate_state_residency Compliance Evaluate State Residency ~169
Evaluate individual statutory residency, domicile nexus, and state tax liability across all 50 US states and District of Columbia.
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | – | – |
| capital_gains | number | – | – |
| days_in_state | integer | yes | – |
| federal_agi | number | – | – |
| filing_status | string | – | – |
| has_active_driver_license | boolean | – | – |
| has_active_homestead_exemption | boolean | – | – |
| has_active_voter_registration | boolean | – | – |
| is_domiciled | boolean | – | – |
| jurisdiction | string | yes | – |
| maintains_permanent_abode | boolean | – | – |
| retirement_income | number | – | – |
| tax_year | integer | – | – |
| telecommuting_days_out_of_state | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
statutes_list_publications Statutes List Publications ~103
List administrative circulars, tax guidance publications, and bulletins.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | Optional publication category. Valid values: boletin-informativo, carta-circular, determinacion-administrativa, irs-publication, policy-bulletin. Case, spaces, hyphens and underscores are ignored ('c… |
| limit | integer | – | – |
| since_date | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
statutes_lookup_statute Statutes Lookup Statute ~110
Retrieve exact statutory language, temporal version, and metadata by citation, section code, or the record id from statutes_search_tax_code (pass a result's id as citation_or_section to get its full text).
| Name | Type | Req | Description |
|---|---|---|---|
| citation_or_section | string | yes | Citation ('26 U.S.C. § 933'), section code ('933'), or a record id from statutes_search_tax_code results ('us-irc-933'). |
| jurisdiction | – | – | – |
| lang | string | – | – |
| tax_year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
statutes_search_tax_code Statutes Search Tax Code ~218
Keyword and concept search across Federal and State statutory corpora. Multi-word queries match individual terms: rows with the whole phrase rank first, then by how many terms match, then newer effective year first (empty or non-numeric years last), then id. Each result is a short snippet (up to 300 characters around the first matched term) with its id, citation, title, jurisdiction, year, validity and content labels, not the full text: call statutes_lookup_statute with citation_or_section set to the result's id to read the full text.
| Name | Type | Req | Description |
|---|---|---|---|
| corpus | – | – | Optional corpus code, e.g. 'IRC', 'RCW', 'LEY60'. A jurisdiction code or name ('washington') is also accepted and filters by jurisdiction. |
| jurisdiction | – | – | Optional jurisdiction code or full name, e.g. 'WA' or 'Washington', 'PR' or 'Puerto Rico', 'US' or 'federal'. |
| limit | integer | – | – |
| query | string | yes | – |
| tax_year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
system_get_health_status System Get Health Status ~24
Check the operational health of the taxcode server and DuckDB storage.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.christianclaudio/taxcode MCP server?
io.github.christianclaudio/taxcode runs locally as a PyPI package, launched with uvx mcp-server-taxcode. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-server-taxcode
claude mcp add christianclaudio-taxcode -- uvx mcp-server-taxcode
What is the io.github.christianclaudio/taxcode MCP server?
io.github.christianclaudio/taxcode is an MCP server listed in the public MCP registry as io.github.christianclaudio/taxcode. MCP server for US Federal, territorial, and state tax law and compliance. This page covers its PyPI package (mcp-server-taxcode).
Is the io.github.christianclaudio/taxcode MCP server safe to use?
io.github.christianclaudio/taxcode scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. 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 io.github.christianclaudio/taxcode MCP server expose?
io.github.christianclaudio/taxcode exposes 8 tools: system_get_health_status, statutes_lookup_statute, statutes_search_tax_code, statutes_list_publications, compliance_evaluate_pr_bona_fide_residency, and 3 more. Their descriptions and schemas cost roughly 1,062 tokens of context every time the server is loaded.
Is the io.github.christianclaudio/taxcode MCP server still maintained?
io.github.christianclaudio/taxcode is still listed as active in the MCP registry. We last reached this channel on 18 October 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 io.github.christianclaudio/taxcode MCP server under?
io.github.christianclaudio/taxcode declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.