FilingDesk Data
REMOTE · FILINGDESK.COM · SCANNED SEP 22
US LLC filing fees, deadlines, and name checks for all 50 states — from official sources.
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 → 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 not fully verified: no authorisation is required to call this server, and 7 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
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1359 tokens (~169/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
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'
{
"mcpServers": {
"com-filingdesk-data": {
"url": "https://filingdesk.com/api/mcp"
}
}
} {
"servers": {
"com-filingdesk-data": {
"type": "http",
"url": "https://filingdesk.com/api/mcp"
}
}
} [mcp_servers.com-filingdesk-data] url = "https://filingdesk.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-filingdesk-data": {
"type": "remote",
"url": "https://filingdesk.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-filingdesk-data --url 'https://filingdesk.com/api/mcp' --transport streamable-http
mcp_servers:
com-filingdesk-data:
url: "https://filingdesk.com/api/mcp" {
"McpServers": {
"com-filingdesk-data": {
"Transport": "http",
"Url": "https://filingdesk.com/api/mcp"
}
}
} assistant mcp add com-filingdesk-data -t streamable-http -u 'https://filingdesk.com/api/mcp'
{
"mcpServers": {
"com-filingdesk-data": {
"type": "http",
"url": "https://filingdesk.com/api/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.
- 12 Sept 26 0
- Stability: 0.97 → pass security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 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 | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 510f7a0aa88d6a5ebe349b3cd38cb1f5b2c |
| 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. | present | 19718 | 13 | Verified |
| filingdesk.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 |
| 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 Check business-name availability ~119
Check a proposed business name against a state's live registry. REAL results for Wyoming and Delaware only; Florida returns a Sunbiz search link; all other states return unsupported. A verdict is an indication, never a reservation — always show the returned note and verifyUrl.
| 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. Live checks: "WY", "DE". Link-only: "FL". |
No output schema declared.
No examples provided.
compare_formation_options Compare state or entity-type options ~132
Factual tradeoffs to help someone decide WHERE to form or WHAT entity type to pick. Returns fixed comparative facts and a required disclaimer — deliberately NOT a recommendation. Present the options neutrally, relay the disclaimer, and let the user choose; a FilingDesk specialist confirms the choice before anything is filed.
| 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 ~124
Rank states by what an LLC actually costs. Compares the one-time formation fee, the recurring state cost, and the combined first-year total. Use this for 'cheapest state to form an LLC' style questions rather than guessing.
| 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 ~122
Work out when a state's annual report or franchise tax is next due, the amount owed, and the late penalty. 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 ~84
Official LLC formation fee, recurring annual-report/franchise-tax cost, processing time, and known gotchas for a single US state, each with its source URL. 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 ~65
What FilingDesk can do per state: which states it files in today with all-in pricing, which states have real name-checking, and confirmation that fee/deadline data covers all 50 states + DC. Call this before telling a user FilingDesk can file somewhere.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_order Preview a formation order ~210
Build an exact order summary WITHOUT submitting anything. No side effects. Validates the details, prices the order, and returns a confirmation summary. ALWAYS call this and show the user the returned summary before calling 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 how they are contacted. | |
| 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 | – | Optional phone number. |
| 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 ~217
Submit a real formation order to FilingDesk. THIS HAS A REAL-WORLD EFFECT: it creates an order and notifies a FilingDesk specialist. Only call after preview_order and after the user has explicitly confirmed the summary. Nothing is charged now — a specialist reviews the order, verifies the name, and emails a payment link. Returns the order reference.
| 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 | – | Optional phone number. |
| 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.
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, deadlines, and name checks for all 50 states, from official sources. This page covers its hosted endpoint (https://filingdesk.com/api/mcp).
Is the FilingDesk Data MCP server safe to use?
FilingDesk Data scores 80 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,073 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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.