US Sales Tax Economic Nexus Check
REMOTE · US-SALES-TAX-NEXUS.NEROLABS.WORKERS.DEV
Which US states must a remote seller register in for sales tax? Every state's nexus rule. Sourced.
Available components
Last scanned (13 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 743 tokens (~185/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 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 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 13 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.
- 12 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Oct 26 57
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 · Probed https://us-sales-tax-nexus.nerolabs.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=nerolabs.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6f7f02a43942bb2aca3c411aec703cf0dc1 |
| SANs: *.nerolabs.workers.dev, nerolabs.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of us-sales-tax-nexus.nerolabs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://us-sales-tax-nexus.nerolabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://us-sales-tax-nexus.nerolabs.workers.dev/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 →
check_economic_nexus ~383
Checks which US states a remote seller (no office, staff or stock in the state) must register in to collect sales tax, from its sales into each state. Give sales_by_state with the dollar sales and number of transactions (orders) per state, the period those figures cover, and whether they include sales made through marketplaces such as Amazon or Etsy. Returns states where the seller is over the economic nexus threshold (must register), states close to it (80 percent or more), states under it, and for each the threshold, the measurement period the state uses, what sales count (gross, retail or taxable only), whether marketplace sales count, when registration must happen, and the state revenue department source. Unclear cases give the SAFE answer (treated as over) with what it depends on. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The date to check the rules on, YYYY-MM-DD. Defaults to today. Thresholds changed in several states; past dates use the rule then in force. |
| includes_marketplace_sales | boolean | – | True (default) if the sales and transactions figures include sales made through marketplace facilitators. Many states exclude those sales when testing a remote seller's threshold. |
| period | string | – | What period the figures cover: last_12_months (default), previous_calendar_year or current_calendar_year (year to date). |
| sales_by_state | array | yes | One item per state the seller ships into: {"state":"CA","sales":612000,"transactions":3400}. Optional per item: marketplace_sales and marketplace_transactions (the part made through marketplace facil… |
| show_all_states | boolean | – | True to also list every sales tax state the seller did not report sales for. Default false. |
No output schema declared.
No examples provided.
list_capabilities ~47
Lists coverage (45 sales tax states plus DC, and the 5 states with no statewide sales tax), the date the data was last checked, and related Nero Labs Rules servers. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_nexus_thresholds ~101
Lists the economic nexus threshold of every US sales tax state (or one state) on a date: dollar and transaction thresholds, and/or logic, measurement period, what counts, marketplace rules, when to register and the official source. Also lists the states with no statewide sales tax. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD, default today. |
| state | string | – | Optional two-letter code or name. All states when left out. |
No output schema declared.
No examples provided.
list_upcoming_nexus_changes ~88
Lists economic nexus threshold changes in a date window (for example states dropping the 200 transaction test), soonest first, with the old and new rule and source. Use a past from_date to see recent changes. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | 1 to 1460, default 365. |
| from_date | string | – | YYYY-MM-DD, default today. |
No output schema declared.
No examples provided.
How do I install the US Sales Tax Economic Nexus Check MCP server?
US Sales Tax Economic Nexus Check is a hosted endpoint at https://us-sales-tax-nexus.nerolabs.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 · us-sales-tax-nexus.nerolabs.workers.dev
claude mcp add --transport http nero-engine-us-sales-tax-nexus 'https://us-sales-tax-nexus.nerolabs.workers.dev/mcp'
What is the US Sales Tax Economic Nexus Check MCP server?
US Sales Tax Economic Nexus Check is an MCP server listed in the public MCP registry as io.github.Nero-Engine/us-sales-tax-nexus. Which US states must a remote seller register in for sales tax? Every state's nexus rule. Sourced. This page covers its hosted endpoint (https://us-sales-tax-nexus.nerolabs.workers.dev/mcp).
Is the US Sales Tax Economic Nexus Check MCP server safe to use?
US Sales Tax Economic Nexus Check scores 60 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 US Sales Tax Economic Nexus Check MCP server expose?
US Sales Tax Economic Nexus Check exposes 4 tools: list_capabilities, check_economic_nexus, list_nexus_thresholds, list_upcoming_nexus_changes. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Does the US Sales Tax Economic Nexus Check MCP server require authentication?
No. We connected to US Sales Tax Economic Nexus Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the US Sales Tax Economic Nexus Check MCP server still maintained?
US Sales Tax Economic Nexus Check 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.