Pass-through tax rules
REMOTE · PASS-THROUGH-TAX-RULES.VERCEL.APP
Cited, tax-year-dated rules for state PTET, the federal SALT cap, and bonus-depreciation conformity.
Available components
Last scanned (8 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 545 tokens (~136/item across 4 items; 4 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 Management40
- Stability observed for 12 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Tool “coverage” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.2.0 functional
- “bonus_conformity” reworded the description of “state” cosmetic
- “bonus_conformity” reworded the description of “tax_year” cosmetic
- “ptet_rules” reworded the description of “state” cosmetic
- “ptet_rules” reworded the description of “tax_year” cosmetic
- 24 Oct 26 73
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 5 Nov 2026 · Probed https://pass-through-tax-rules.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pass-through-tax-rules.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pass-through-tax-rules.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://pass-through-tax-rules.vercel.app/api/mcp | HTTPS enforced | 308 | https://pass-through-tax-rules.vercel.app/api/mcp |
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 →
bonus_conformity Bonus depreciation conformity ~110
Whether a state conforms to IRC 168(k) bonus depreciation and IRC 179 for a tax year, its IRC conformity date, and the add-back or subtraction in plain terms. Unverified fields are null. Unknown states and years are not_covered.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Postal code or full state name. The District of Columbia is DC. New York City is NYC. |
| tax_year | number|string | yes | Tax year, such as 2026. Files are tax-year specific. |
No output schema declared.
No examples provided.
coverage Coverage ~63
List jurisdictions and tax years in this dataset. elective_ptet_2026 counts only 2026 files with an elective PTET. no_elective_ptet_2026 and not_effective_2026 are separate and are not PTET states for 2026.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ptet_rules Pass-through entity tax ~109
Elective pass-through entity tax for one state and tax year: eligibility, who elects, deadline, rate, owner credit or exclusion, estimates, and sunset. Returns not_covered when this server has no file. Informational, not tax advice.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Postal code or full state name. The District of Columbia is DC. New York City is NYC. |
| tax_year | number|string | yes | Tax year, such as 2026. Files are tax-year specific. |
No output schema declared.
No examples provided.
salt_cap Federal SALT cap ~208
Compute the federal SALT deduction cap under 26 USC 164(b)(6) and (b)(7) for a tax year, filing status, and modified adjusted gross income. Returns the cap and the steps, not the deduction. Years before 2018 are not_covered. MAGI is used to compute and is not written to the usage log.
| Name | Type | Req | Description |
|---|---|---|---|
| filing_status | string | yes | single, married_filing_jointly, married_filing_separately, head_of_household, or qualifying_surviving_spouse. Aliases: mfj, mfs, hoh, qss. |
| magi | number|string | yes | Modified adjusted gross income: AGI plus IRC 911, 931, and 933 exclusions. Integer or decimal string, at most 8 decimal places. |
| tax_year | number|string | yes | Tax year. 2018 through 2024 use the prior flat cap. 2025 and later use section 164(b)(7). |
No output schema declared.
No examples provided.
How do I install the Pass-through tax rules MCP server?
Pass-through tax rules is a hosted endpoint at https://pass-through-tax-rules.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pass-through-tax-rules.vercel.app
claude mcp add --transport http app-vercel-pass-through-tax-rules-pass-through-t 'https://pass-through-tax-rules.vercel.app/api/mcp'
What is the Pass-through tax rules MCP server?
Pass-through tax rules is an MCP server listed in the public MCP registry as app.vercel.pass-through-tax-rules/pass-through-tax-rules. Cited, tax-year-dated rules for state PTET, the federal SALT cap, and bonus-depreciation conformity. This page covers its hosted endpoint (https://pass-through-tax-rules.vercel.app/api/mcp).
Is the Pass-through tax rules MCP server safe to use?
Pass-through tax rules scores 78 out of 100 on VerifyMCP. 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 Pass-through tax rules MCP server expose?
Pass-through tax rules exposes 4 tools: ptet_rules, salt_cap, bonus_conformity, coverage. Their descriptions and schemas cost roughly 490 tokens of context every time the server is loaded.
Does the Pass-through tax rules MCP server require authentication?
No. We connected to Pass-through tax rules without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pass-through tax rules MCP server still maintained?
Pass-through tax rules 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.