FilingDesk Data
REMOTE · FILINGDESK.COM
US LLC filing fees, annual-report deadlines and naming-rule checks, from official state sources.
Available components
Last scanned (20 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
Recent critical change
Authorization (12 Oct 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 1967 tokens (~245/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Oct 26 +1
- Stability: fail → pass ▲ security
- 12 Oct 26 0
- Authorization: partial → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_llc_name” rewrote its description, which is the text the model reads security
- Tool “compare_formation_options” rewrote its description, which is the text the model reads security
- Tool “compare_llc_costs” rewrote its description, which is the text the model reads security
- Tool “get_annual_report_deadline” rewrote its description, which is the text the model reads security
- Tool “get_llc_fees” rewrote its description, which is the text the model reads security
- Tool “list_filing_states” rewrote its description, which is the text the model reads security
- Tool “preview_order” rewrote its description, which is the text the model reads security
- Tool “submit_order” rewrote its description, which is the text the model reads security
- Tool “submit_order” is now declared destructive security
- Schema quality: 176 → 245 ▼ functional
- Server version: 0.2.0 → 0.3.0 functional
- “check_llc_name” reworded the description of “state” cosmetic
- Tool “check_llc_name” changed its title: Check business-name availability → Screen a business name against state naming rules cosmetic
- 1 Oct 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 0.2.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- “preview_order” made “phone” required, so existing callers break ▼ functional
- “submit_order” made “phone” required, so existing callers break ▼ functional
- “preview_order” reworded the description of “email” cosmetic
- “preview_order” reworded the description of “phone” cosmetic
- “submit_order” reworded the description of “phone” cosmetic
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 21 Nov 2026 · Probed https://filingdesk.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=filingdesk.com | CN=YE2,O=Let's Encrypt,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5974211e13a70abedc04d762ce98ac4d5a2 |
| SANs: filingdesk.com, www.filingdesk.com | ||||||
| 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 filingdesk.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| filingdesk.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://filingdesk.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://filingdesk.com/api/mcp | HTTPS enforced | 301 | https://filingdesk.com/api/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. 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_llc_name Screen a business name against state naming rules ~285
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | – | Defaults to llc. |
| 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". |
No output schema declared.
No examples provided.
compare_formation_options Compare state or entity-type options ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| homeState | string | – | Optional. The state the user actually lives or operates in — lets the comparison include their home-state costs, which usually matter most. |
| topic | string | yes | "state" for where to form, "entity_type" for LLC vs S-corp vs C-corp. |
No output schema declared.
No examples provided.
compare_llc_costs Compare LLC costs across states ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many states to return. Defaults to 10. |
| sortBy | string | – | Which cost to sort ascending by. Defaults to firstYear (formation + one recurring period). |
| states | array | – | State codes or names to compare. Omit to rank all 50 states + DC. |
No output schema declared.
No examples provided.
get_annual_report_deadline Get the next annual-report deadline ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| formationDate | string | – | The LLC's formation date as ISO yyyy-mm-dd. Required for anniversary- and quarter-based states. |
| state | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
No output schema declared.
No examples provided.
get_llc_fees Get LLC fees for one state ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
No output schema declared.
No examples provided.
list_filing_states List coverage ~77
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_order Preview a formation order ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| businessName | string | yes | Proposed company name. Does not need to be final — a specialist verifies availability. |
| description | string | – | One or two sentences on what the business does. Optional — the user may skip it. |
| string | yes | The customer's email. Required — this is where documents go. Temporary/disposable inboxes are rejected. | |
| entityType | string | yes | Entity type, e.g. "LLC", "S-Corp", "C-Corp", or "Not sure" if the user hasn't decided. |
| fullName | string | yes | The customer's full name. |
| 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. |
| state | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
No output schema declared.
No examples provided.
submit_order Submit the formation order ~249
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-…).
| Name | Type | Req | Description |
|---|---|---|---|
| businessName | string | yes | Proposed company name. |
| description | string | – | What the business does. Optional. |
| string | yes | The customer's email. | |
| entityType | string | yes | Entity type, e.g. "LLC", or "Not sure". |
| fullName | string | yes | The customer's full name. |
| phone | string | yes | The customer's phone number (required). |
| state | string | yes | Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC. |
| userConfirmed | boolean | yes | Must be true. Set only after the user has seen the preview_order summary and explicitly agreed to submit. |
No output schema declared.
No examples provided.
How do I install the FilingDesk Data MCP server?
FilingDesk Data is a hosted endpoint at https://filingdesk.com/api/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 · filingdesk.com
claude mcp add --transport http com-filingdesk-data 'https://filingdesk.com/api/mcp'
What is the FilingDesk Data MCP server?
FilingDesk Data is an MCP server listed in the public MCP registry as com.filingdesk/data. US LLC filing fees, annual-report deadlines and naming-rule checks, from official state sources. This page covers its hosted endpoint (https://filingdesk.com/api/mcp).
Is the FilingDesk Data MCP server safe to use?
FilingDesk Data scores 79 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 FilingDesk Data MCP server expose?
FilingDesk Data exposes 8 tools: get_llc_fees, compare_llc_costs, get_annual_report_deadline, check_llc_name, list_filing_states, and 3 more. Their descriptions and schemas cost roughly 1,566 tokens of context every time the server is loaded.
Does the FilingDesk Data MCP server require authentication?
No. We connected to FilingDesk Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FilingDesk Data MCP server still maintained?
FilingDesk Data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the FilingDesk Data MCP server?
VerifyMCP ran 13 checks on FilingDesk Data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.