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.

2027 Tax Brackets and Standard Deduction MCP

REMOTE · TAX-BRACKETS-STANDARD-DEDUCTION-2027-MCP.LIPMICHAL.WORKERS.DEV

2027 federal income tax brackets and standard deduction from IRS Rev. Proc. 2026-35.

+3 this week 70 Trust /100

Last scanned (21 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security63
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1012 tokens (~253/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 Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 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.

  • 12 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.

  • 10 Nov 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.

  • 8 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 63

    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 21 Nov 2026 · Probed https://tax-brackets-standard-deduction-2027-mcp.lipmichal.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lipmichal.workers.dev CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 ebf145553d5751d20e0d3cd51e3d7a94
SANs: lipmichal.workers.dev, *.lipmichal.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tax-brackets-standard-deduction-2027-mcp.lipmichal.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tax-brackets-standard-deduction-2027-mcp.lipmichal.workers.dev/mcp Verified 200
http (plaintext) http://tax-brackets-standard-deduction-2027-mcp.lipmichal.workers.dev/mcp Inconclusive 405
MCP tools · 4 exposed · ~887 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
calculate_federal_income_tax ~330

Federal income tax for tax year 2027 (or 2026) on an income, using the IRS rate schedule: subtracts the standard or itemized deduction (with the age and blindness extra), applies the brackets, returns the bracket-by-bracket breakdown, marginal and average rate, optional long-term capital gains taxed at 0, 15 or 20 percent, and the tax on the same facts under the other year. Federal income tax only; no credits, self-employment tax, NIIT, AMT or state tax.

NameTypeReqDescription
additional_deductionsnumber–Other deductions that reduce taxable income, for example the qualified business income deduction, worked out by you.
age_65_or_older_countinteger–Filers 65 or older by December 31, for the standard deduction extra.
blind_countinteger–Blind filers, for the standard deduction extra.
deductionstring–Used with income. Default standard.
filing_statusstringyes–
incomenumber–Gross income or AGI before the deduction. Give this or taxable_income.
itemized_deductionsnumber–Total itemized deductions, required when deduction is itemized.
long_term_capital_gainsnumber–Long-term capital gains and qualified dividends included in taxable income, taxed at the preferential rates.
tax_yearnumber–Tax year, 2027 or 2026. Default 2027.
taxable_incomenumber–Taxable income after the deduction. Give this or income.

No output schema declared.

No examples provided.

get_standard_deduction ~242

The standard deduction for tax year 2027 (or 2026) for a filing status from IRS Rev. Proc. 2026-35, with the additional amount for each filer who is 65 or older or blind, the dependent rule (greater of a floor or earned income plus a fixed amount), and the change from the other year.

NameTypeReqDescription
age_65_or_older_countinteger–How many filers are 65 or older by December 31 of the tax year (0 to 2, joint returns only 2). Default 0.
blind_countinteger–How many filers are blind (0 to 2, joint returns only 2). Default 0.
can_be_claimed_as_dependentboolean–True if someone else can claim this filer as a dependent. Default false.
earned_incomenumber–Earned income of the dependent filer, used only when can_be_claimed_as_dependent is true.
filing_statusstringyes–
tax_yearnumber–Tax year, 2027 or 2026. Default 2027.

No output schema declared.

No examples provided.

get_tax_amounts ~130

Other 2027 inflation-adjusted tax amounts beside 2026 from IRS Rev. Proc. 2026-35: long-term capital gains 0 and 15 percent thresholds, child tax credit, adoption credit, earned income credit table, alternative minimum tax exemptions, estate and gift tax exclusions, section 179, qualified business income thresholds, health FSA, kiddie tax and the foreign earned income exclusion.

NameTypeReqDescription
tax_yearnumber–Tax year, 2027 or 2026. Default 2027.
topicstring–One topic or all. Default all.

No output schema declared.

No examples provided.

get_tax_brackets ~185

The federal income tax rate schedule for tax year 2027 (or 2026) from IRS Rev. Proc. 2026-35: the seven brackets (10, 12, 22, 24, 32, 35, 37 percent) for single, married filing jointly, married filing separately and head of household, or estates and trusts, with the tax at the bottom of each bracket and the change in each threshold from the other year. A model cannot know the 2027 numbers from training. Thresholds apply to taxable income after the deduction.

NameTypeReqDescription
compareboolean–Include the other year for comparison. Default true.
filing_statusstring–One filing status. Omit for the four individual statuses.
tax_yearnumber–Tax year, 2027 or 2026. Default 2027.

No output schema declared.

No examples provided.

Install

How do I install the 2027 Tax Brackets and Standard Deduction MCP server?

2027 Tax Brackets and Standard Deduction MCP is a hosted endpoint at https://tax-brackets-standard-deduction-2027-mcp.lipmichal.workers.dev/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 · tax-brackets-standard-deduction-2027-mcp.lipmichal.workers.dev

# add to Claude Code
claude mcp add --transport http theluckystrike-tax-brackets-standard-deduction-2 'https://tax-brackets-standard-deduction-2027-mcp.lipmichal.workers.dev/mcp'
Common questions

What is the 2027 Tax Brackets and Standard Deduction MCP server?

2027 Tax Brackets and Standard Deduction MCP is listed in the public MCP registry as io.github.theluckystrike/tax-brackets-standard-deduction-20…. 2027 federal income tax brackets and standard deduction from IRS Rev. Proc. 2026-35. This page covers its hosted endpoint (https://tax-brackets-standard-deduction-2027-mcp.lipmichal.workers.dev/mcp).

Is the 2027 Tax Brackets and Standard Deduction MCP server safe to use?

2027 Tax Brackets and Standard Deduction MCP scores 70 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 2027 Tax Brackets and Standard Deduction MCP server expose?

2027 Tax Brackets and Standard Deduction MCP exposes 4 tools: get_tax_brackets, get_standard_deduction, calculate_federal_income_tax, get_tax_amounts. Their descriptions and schemas cost roughly 887 tokens of context every time the server is loaded.

Does the 2027 Tax Brackets and Standard Deduction MCP server require authentication?

No. We connected to 2027 Tax Brackets and Standard Deduction MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 2027 Tax Brackets and Standard Deduction MCP server still maintained?

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

What did VerifyMCP test on the 2027 Tax Brackets and Standard Deduction MCP server?

VerifyMCP ran 12 checks on 2027 Tax Brackets and Standard Deduction MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about 2027 Tax Brackets and Standard Deduction MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.