Estimate My Paycheck
REMOTE · ESTIMATEMYPAYCHECK.COM
US take-home pay after federal, FICA and state taxes, all 50 states and DC.
Available components
Last scanned (22 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 634 tokens (~211/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 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.
- 2 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.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 64
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 4 Nov 2026 · Probed https://estimatemypaycheck.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=estimatemypaycheck.com | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c160c9aa053d05f31332d5a5af8ecb78 |
| SANs: estimatemypaycheck.com, *.estimatemypaycheck.com | ||||||
| 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 estimatemypaycheck.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| estimatemypaycheck.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://estimatemypaycheck.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://estimatemypaycheck.com/api/mcp | Inconclusive | 405 |
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 →
calculate_bonus_tax Bonus after taxes ~127
What a bonus check pays after the flat 22% federal supplemental withholding, FICA and state tax, and how much of the federal withholding comes back (or is still owed) at tax time, on top of a salary, 2026 rules (IRS Pub. 15).
| Name | Type | Req | Description |
|---|---|---|---|
| bonus | number | yes | Bonus in dollars. |
| filing_status | string | – | Default single. |
| salary | number | yes | Annual gross salary in dollars. Give this or hourly_rate. |
| state | string | yes | Two-letter state code or name: TX, CA, new-york, DC. |
No output schema declared.
No examples provided.
calculate_paycheck Calculate take-home pay ~284
Compute a US paycheck for 2026: gross, each tax and pre-tax deduction, and take-home pay per paycheck and per year, for a salary or an hourly rate (overtime over 40 hours at 1.5 times) in any state or DC. Federal withholding follows the annual tax on wages; local city and county taxes are not included (the answer names them when material).
| Name | Type | Req | Description |
|---|---|---|---|
| filing_status | string | – | Default single. |
| health_per_paycheck | number | – | Pre-tax health premium per paycheck, dollars. Default 0. |
| hourly_rate | number | – | Hourly rate in dollars, instead of salary. |
| hours_per_week | number | – | Hours a week with hourly_rate (over 40 paid at 1.5 times). Default 40. |
| k401_percent | number | – | Pre-tax 401(k) contribution, percent of gross. Default 0. |
| pay_frequency | string | – | Default biweekly. |
| residency | string | – | resident (default), nonresident (e.g. H-1B first year: taxed as single), student (F/J/M/Q nonresident: no FICA). |
| salary | number | – | Annual gross salary in dollars. Give this or hourly_rate. |
| state | string | yes | Two-letter state code or name: TX, CA, new-york, DC. |
No output schema declared.
No examples provided.
compare_states Compare take-home pay in every state ~113
Take-home pay for the same salary in the 50 states and DC in 2026, sorted from the highest. Useful to answer "which state lets me keep the most" or to price a move.
| Name | Type | Req | Description |
|---|---|---|---|
| filing_status | string | – | Default single. |
| k401_percent | number | – | Pre-tax 401(k) contribution, percent of gross. Default 0. |
| pay_frequency | string | – | Default biweekly. |
| salary | number | yes | Annual gross salary in dollars. Give this or hourly_rate. |
No output schema declared.
No examples provided.
How do I install the Estimate My Paycheck MCP server?
Estimate My Paycheck is a hosted endpoint at https://estimatemypaycheck.com/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 · estimatemypaycheck.com
claude mcp add --transport http com-estimatemypaycheck-paycheck 'https://estimatemypaycheck.com/api/mcp'
What is the Estimate My Paycheck MCP server?
Estimate My Paycheck is an MCP server listed in the public MCP registry as com.estimatemypaycheck/paycheck. US take-home pay after federal, FICA and state taxes, all 50 states and DC. This page covers its hosted endpoint (https://estimatemypaycheck.com/api/mcp).
Is the Estimate My Paycheck MCP server safe to use?
Estimate My Paycheck scores 67 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 Estimate My Paycheck MCP server expose?
Estimate My Paycheck exposes 3 tools: calculate_paycheck, compare_states, calculate_bonus_tax. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.
Does the Estimate My Paycheck MCP server require authentication?
No. We connected to Estimate My Paycheck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Estimate My Paycheck MCP server still maintained?
Estimate My Paycheck is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.