Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
FilingDesk Data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
US LLC filing fees, annual-report deadlines and naming-rule checks, from official state sources.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http filingdesk-data-mcp https://filingdesk.com/api/mcp
# 2 — ask your agent for something these tools do
# get_llc_fees, compare_llc_costs, get_annual_report_deadline and 5 more
FilingDesk Data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FIAll 1 server
filingdesk1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http filingdesk-data-mcp https://filingdesk.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
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. Retur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| states | array | no | State codes or names to compare. Omit to rank all 50 states + DC. |
| sortBy | string | no | Which cost to sort ascending by. Defaults to firstYear (formation + one recurring period). |
| limit | integer | no | How many states to return. Defaults to 10. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
| formationDate | string | no | The LLC's formation date as ISO yyyy-mm-dd. Required for anniversary- and quarter-based states. |
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 requir
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The proposed name, e.g. "Blue Harbor Holdings LLC". |
| state | string | yes | State code or name. Full naming-rule screen: "WY", "DE". Designator check + Sunbiz link: "FL". Other states return "unsupported". |
| entityType | string | no | Defaults to llc. |
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.
No parameter schema on file.
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 neu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | "state" for where to form, "entity_type" for LLC vs S-corp vs C-corp. |
| homeState | string | no | Optional. The state the user actually lives or operates in — lets the comparison include their home-state costs, which usually matter most. |
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 subm
| Parameter | Type | Required | Notes |
|---|---|---|---|
| businessName | string | yes | Proposed company name. Does not need to be final — a specialist verifies availability. |
| state | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
| entityType | string | yes | Entity type, e.g. "LLC", "S-Corp", "C-Corp", or "Not sure" if the user hasn't decided. |
| description | string | no | One or two sentences on what the business does. Optional — the user may skip it. |
| fullName | string | yes | The customer's full name. |
| string | yes | The customer's email. Required — this is where documents go. Temporary/disposable inboxes are rejected. | |
| phone | string | yes | The customer's phone number with area code. Required — used only if the state or the specialist has a question about the filing. |
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 ha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| businessName | string | yes | Proposed company name. |
| state | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
| entityType | string | yes | Entity type, e.g. "LLC", or "Not sure". |
| description | string | no | What the business does. Optional. |
| fullName | string | yes | The customer's full name. |
| string | yes | The customer's email. | |
| phone | string | yes | The customer's phone number (required). |
| userConfirmed | boolean | yes | Must be true. Set only after the user has seen the preview_order summary and explicitly agreed to submit. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install FilingDesk Data or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.3.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digesta36c9367039d7b2e6530712f82314d70d2b0e18c683361d93c798c044a7c02ad
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_llc_fees | no tags | |
| compare_llc_costs | no tags | |
| get_annual_report_deadline | no tags | |
| check_llc_name | no tags | |
| list_filing_states | no tags | |
| compare_formation_options | no tags | |
| preview_order | no tags | |
| submit_order | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta36c9367039d7b2e
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish FilingDesk Data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.