ExitCleanly — LLC Dissolution by State
REMOTE · MCP.EXITCLEANLY.COM · SCANNED AUG 20
State-by-state LLC dissolution: exact fees, forms, official state links. Not legal advice.
Available components
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 →
Endpoint Security57
- 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 3 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 435 tokens (~145/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 Management30
- Stability observed for 9 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.exitcleanly.com
claude mcp add --transport http com-exitcleanly-dissolution https://mcp.exitcleanly.com/mcp
[mcp_servers.com-exitcleanly-dissolution] url = "https://mcp.exitcleanly.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-exitcleanly-dissolution": {
"type": "remote",
"url": "https://mcp.exitcleanly.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-exitcleanly-dissolution --url https://mcp.exitcleanly.com/mcp --transport streamable-http
mcp_servers:
com-exitcleanly-dissolution:
url: "https://mcp.exitcleanly.com/mcp" {
"mcpServers": {
"com-exitcleanly-dissolution": {
"type": "http",
"url": "https://mcp.exitcleanly.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Aug 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.
- 18 Aug 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.
- 16 Aug 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.
- 14 Aug 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.
- 13 Aug 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_llc_dissolution_requirements” rewrote its description, which is the text the model reads security
- Tool “list_llc_dissolution_fees” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “cost_of_not_dissolving_llc” functional
- 12 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Aug 26 61
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 20 Aug 2026 · Probed https://mcp.exitcleanly.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=exitcleanly.com | CN=WE1,O=Google Trust Services,C=US | 11 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7658d4f96121fe950ee329e2ebd0aa9e |
| SANs: exitcleanly.com, mcp.exitcleanly.com, *.mcp.exitcleanly.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 |
DNSSEC insecure
Validation of mcp.exitcleanly.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| exitcleanly.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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.exitcleanly.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.exitcleanly.com/mcp | HTTPS enforced | 301 | https://mcp.exitcleanly.com/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.
cost_of_not_dissolving_llc What an undissolved LLC keeps costing ~115
Explain what it costs to leave an LLC undissolved instead of formally closing it: annual report and franchise fees, registered agent fees, late-filing penalties, and accountant fees for zero returns, with typical yearly ranges. Use when someone asks what happens if they just stop using the company, stop filing, abandon it or let it lapse, or whether dissolving is worth the filing fee.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Optional US state, to add that state’s own filing fee to the comparison |
No output schema declared.
No examples provided.
get_llc_dissolution_requirements How to dissolve an LLC in a given state ~148
Get what it takes to dissolve (close) an LLC in a specific US state: the filing fee quoted exactly as the state publishes it, the form name, how to file, typical processing time, the official state filing office link, the costs that come on top of the filing fee (franchise tax, tax clearance, newspaper notice), and the full seven-step wind-up sequence. Use when someone asks how to close, dissolve, cancel or wind up an LLC or a business in any state, what it costs, or which form they need.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | US state name or two-letter code, e.g. "Texas" or "TX" |
No output schema declared.
No examples provided.
list_llc_dissolution_fees Dissolution filing fees for all states ~67
List the LLC dissolution filing fee for all 50 US states and DC, quoted exactly as each state publishes it, marking the states where the filing fee is not the whole cost. Use when someone compares costs across states or asks which states charge to close an LLC.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.