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

filingdesk-data

https://filingdesk.com

Registry code: 3a74fbfee6a71f32

api record

FilingDesk Data: reference data for forming a US LLC, plus human-reviewed

formation order intake.

endpoint
https://filingdesk.com/api/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 filingdesk-data live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is filingdesk-data free to use?
Yes — the hub reached it with no key and no payment.
What tools does filingdesk-data have?
8 tools: preview_order, submit_order, get_llc_fees, check_llc_name, compare_formation_options, get_annual_report_deadline, compare_llc_costs, list_filing_states.
Is filingdesk-data 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
99.6%

90 days 99.7%· all time 99.7%

latency
544ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 340 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • compare llc formation costs by state
  • check llc name availability
  • get annual report deadlines
  • submit an llc formation order
takes → gives
text → data
tools
7 reads1 moves money
_ 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 8 tools
2 open 6 never probed 2 of 8 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.

  • compare_llc_costs reads open 6h ago

    Ranks US states by LLC cost: the one-time formation fee, the recurring state fee, or the first-year total (formation plus one recurring period). Use when the user asks which state is cheapest to form or maintain an LLC in, or wants LLC costs compared across specific states. Covers all 50 states + DC. State fees only — registered-agent fees, service fees, and revenue-based taxes are excluded. Returns figures only, without source URLs; get_llc_fees returns a state's official sources.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 51,
          "minimum": 1,
          "description": "How many states to return. Defaults to 10."
        },
        "sortBy": {
          "enum": [
            "formation",
            "recurring",
            "firstYear"
          ],
          "type": "string",
          "description": "Which cost to sort ascending by. Defaults to firstYear (formation + one recurring period)."
        },
        "states": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "State codes or names to compare. Omit to rank all 50 states + DC."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • list_filing_states reads open 6h ago

    Lists FilingDesk's coverage: the states it files formations in today with all-in prices, the states its naming-rule screen supports, and fee/deadline data coverage (all 50 states + DC). Use when the user asks which states FilingDesk can file in, or before stating that FilingDesk can file in a particular state.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • preview_order reads unknown never probed

    Validates and prices a formation order and returns the exact summary that would be submitted, WITHOUT submitting anything (no side effects). Use when the user wants FilingDesk to form their LLC or corporation and has provided the business name, state, entity type, and their name, email, and phone. The returned summary is meant to be shown to the user verbatim, and this step is required before submit_order.

    mcp-tool

    {
      "type": "object",
      "required": [
        "businessName",
        "state",
        "entityType",
        "fullName",
        "email",
        "phone"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "The customer's email. Required — this is where documents go. Temporary/disposable inboxes are rejected."
        },
        "phone": {
          "type": "string",
          "description": "The customer's phone number with area code. Required — used only if the state or the specialist has a question about the filing."
        },
        "state": {
          "type": "string",
          "description": "Two-letter state code or full state name, e.g. \"WY\" or \"Wyoming\". All 50 states + DC."
        },
        "fullName": {
          "type": "string",
          "description": "The customer's full name."
        },
        "entityType": {
          "type": "string",
          "description": "Entity type, e.g. \"LLC\", \"S-Corp\", \"C-Corp\", or \"Not sure\" if the user hasn't decided."
        },
        "description": {
          "type": "string",
          "description": "One or two sentences on what the business does. Optional — the user may skip it."
        },
        "businessName": {
          "type": "string",
          "description": "Proposed company name. Does not need to be final — a specialist verifies availability."
        }
      },
      "additionalProperties": false
    }
    arguments 42 lines
  • submit_order moves money unknown never probed

    Submits a formation order to FilingDesk. THIS HAS A REAL-WORLD EFFECT: it records the order, notifies a FilingDesk specialist, and may send an automatic order-confirmation email to the customer's email address. The specialist then reviews the order, confirms name availability and the price, and emails a payment link. Nothing is charged at submission. Call only after preview_order, once the user has explicitly confirmed that summary (userConfirmed: true). Returns the order reference (FD-…).

    mcp-tool

    {
      "type": "object",
      "required": [
        "businessName",
        "state",
        "entityType",
        "fullName",
        "email",
        "phone",
        "userConfirmed"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "The customer's email."
        },
        "phone": {
          "type": "string",
          "description": "The customer's phone number (required)."
        },
        "state": {
          "type": "string",
          "description": "Two-letter state code or full state name, e.g. \"WY\" or \"Wyoming\". All 50 states + DC."
        },
        "fullName": {
          "type": "string",
          "description": "The customer's full name."
        },
        "entityType": {
          "type": "string",
          "description": "Entity type, e.g. \"LLC\", or \"Not sure\"."
        },
        "description": {
          "type": "string",
          "description": "What the business does. Optional."
        },
        "businessName": {
          "type": "string",
          "description": "Proposed company name."
        },
        "userConfirmed": {
          "type": "boolean",
          "description": "Must be true. Set only after the user has seen the preview_order summary and explicitly agreed to submit."
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • get_llc_fees reads unknown 24h ago

    Returns one US state's LLC formation fee, its recurring annual-report or franchise-tax cost and cadence, online processing time, and known gotchas such as publication requirements, plus a labeled list of the official state source URLs the figures were taken from (dataset verified 2026). Use when the user asks what it costs to form or keep an LLC in a specific state. Covers all 50 states + DC.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "state": {
          "type": "string",
          "description": "Two-letter state code or full state name, e.g. \"WY\" or \"Wyoming\". All 50 states + DC."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_llc_name reads unknown 24h ago

    Screens a proposed business name against state naming rules. It does NOT search any state registry and cannot tell whether a name is already taken. Wyoming and Delaware: the entity designator where the statute requires one (such as "LLC"), words that are restricted or need agency approval (such as "Bank"; in Wyoming also "Trust" or "University"), and other state-specific rules. Florida: the required designator only. Other states and DC return verdict "unsupported" with a note pointing to the state's official name search. Verdicts: "conflict" means the name as written breaks a rule that blocks filing, including a missing required designator (reasons include a "Try:" suggestion where one applies); "uncertain" means no blocking rule was found (reasons may still list warnings) and availability is unverified. Wyoming, Delaware, and Florida results include verifyUrl, the state's official name search. Use when the user proposes a name for a new LLC or corporation in Wyoming, Delaware, or Florida.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "state"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The proposed name, e.g. \"Blue Harbor Holdings LLC\"."
        },
        "state": {
          "type": "string",
          "description": "State code or name. Full naming-rule screen: \"WY\", \"DE\". Designator check + Sunbiz link: \"FL\". Other states return \"unsupported\"."
        },
        "entityType": {
          "enum": [
            "llc",
            "corp"
          ],
          "type": "string",
          "description": "Defaults to llc."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • compare_formation_options reads unknown 24h ago

    Returns fixed, factual tradeoffs for deciding WHERE to form (topic "state": the home state versus Wyoming, Delaware, and Nevada, including the cost of foreign-qualifying back into the home state) or WHAT entity type to use (topic "entity_type": LLC versus the S-corp tax election versus C-corp), plus a required disclaimer. Deliberately not a recommendation: the options are meant to be presented neutrally with the disclaimer, leaving the choice to the user. Use when the user asks which state to form in, whether to form out of state, or which entity type suits their business.

    mcp-tool

    {
      "type": "object",
      "required": [
        "topic"
      ],
      "properties": {
        "topic": {
          "enum": [
            "state",
            "entity_type"
          ],
          "type": "string",
          "description": "\"state\" for where to form, \"entity_type\" for LLC vs S-corp vs C-corp."
        },
        "homeState": {
          "type": "string",
          "description": "Optional. The state the user actually lives or operates in — lets the comparison include their home-state costs, which usually matter most."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • get_annual_report_deadline reads unknown 6h ago

    Calculates when an LLC's next annual report or franchise tax is due in a given state and the amount owed, and returns the state's rule text, late-filing consequences where the dataset has them (penaltyAndNotes), and the official state source URLs. Use when the user asks when their LLC's annual report is due, how often it is filed, or what happens if it is late. States that key the deadline to the formation anniversary or quarter need formationDate; without it the tool says so instead of guessing a date.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "state": {
          "type": "string",
          "description": "Two-letter state code or full state name, e.g. \"WY\" or \"Wyoming\". All 50 states + DC."
        },
        "formationDate": {
          "type": "string",
          "description": "The LLC's formation date as ISO yyyy-mm-dd. Required for anniversary- and quarter-based states."
        }
      },
      "additionalProperties": false
    }
    arguments 17 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 3a74fbfee6a71f32.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3a74fbfee6a71f32/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/3a74fbfee6a71f32/badge.svg)](https://brick.blue/agent/3a74fbfee6a71f32?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
100%

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.