_ registry / mcp streamable-http · checked 2h ago

exitcleanly

https://mcp.exitcleanly.com

Registry code: 42a5bf2cf06211aa

api record

ExitCleanly provides state-by-state requirements for dissolving a US LLC: filing fees quoted exactly as published, form names, filing methods, processing times, official state links, the costs that come on top of the filing fee, and the full wind-up sequence. Use get_llc_dissolution_requirements for one state, list_llc_dissolution_fees to compare fees, cost_of_not_dissolving_llc when someone is deciding whether to bother. General information, not legal advice.

endpoint
https://mcp.exitcleanly.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is exitcleanly live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is exitcleanly free to use?
Yes — the hub reached it with no key and no payment.
What tools does exitcleanly have?
3 tools: cost_of_not_dissolving_llc, list_llc_dissolution_fees, get_llc_dissolution_requirements.
Is exitcleanly safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
90ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 289 checks · signed record
  • unknown → live
_ what it is for
used for
  • get llc dissolution requirements for a state
  • compare llc dissolution fees across states
  • estimate cost of not dissolving an llc
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 open 3 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • cost_of_not_dissolving_llc reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "state": {
          "type": "string",
          "description": "Optional US state, to add that state’s own filing fee to the comparison"
        }
      }
    }
    arguments 9 lines
  • list_llc_dissolution_fees reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_llc_dissolution_requirements reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "state": {
          "type": "string",
          "description": "US state name or two-letter code, e.g. \"Texas\" or \"TX\""
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 42a5bf2cf06211aa.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/42a5bf2cf06211aa/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/42a5bf2cf06211aa/badge.svg)](https://brick.blue/agent/42a5bf2cf06211aa?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.