# FilingDesk Data (remote · filingdesk.com)

US LLC filing fees, deadlines, and name checks for all 50 states — from official sources.

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `filingdesk.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-filingdesk-data/api-mcp.md), [page](https://verifymcp.io/servers/com-filingdesk-data/api-mcp)

## Channel facts

- Endpoint: `https://filingdesk.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-filingdesk-data 'https://filingdesk.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-filingdesk-data": {
      "url": "https://filingdesk.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-filingdesk-data": {
      "type": "http",
      "url": "https://filingdesk.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-filingdesk-data]
url = "https://filingdesk.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-filingdesk-data": {
      "type": "remote",
      "url": "https://filingdesk.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-filingdesk-data --url 'https://filingdesk.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-filingdesk-data:
    url: "https://filingdesk.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-filingdesk-data": {
      "Transport": "http",
      "Url": "https://filingdesk.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-filingdesk-data -t streamable-http -u 'https://filingdesk.com/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-12 (score 80, 0)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 80, +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.

### 2026-09-09 (score 79, +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.

### 2026-09-07 (score 78, +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.

### 2026-09-05 (score 77, +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.

### 2026-09-02 (score 76, +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.

### 2026-08-31 (score 75, +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.

### 2026-08-29 (score 74, +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.

## MCP tools (8)

### `get_llc_fees` (~84 tokens)

Get LLC fees for one state

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.

Input parameters:

- `state` (string, required): Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC.

### `compare_llc_costs` (~124 tokens)

Compare LLC costs across states

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.

Input parameters:

- `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.

### `get_annual_report_deadline` (~122 tokens)

Get the next annual-report deadline

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.

Input parameters:

- `formationDate` (string): The LLC's formation date as ISO yyyy-mm-dd. Required for anniversary- and quarter-based states.
- `state` (string, required): Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC.

### `check_llc_name` (~119 tokens)

Check business-name availability

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.

Input parameters:

- `entityType` (string): Defaults to llc.
- `name` (string, required): The proposed name, e.g. "Blue Harbor Holdings LLC".
- `state` (string, required): State code or name. Live checks: "WY", "DE". Link-only: "FL".

### `list_filing_states` (~65 tokens)

List coverage

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.

### `compare_formation_options` (~132 tokens)

Compare state or entity-type options

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.

Input parameters:

- `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, required): "state" for where to form, "entity_type" for LLC vs S-corp vs C-corp.

### `preview_order` (~210 tokens)

Preview a formation order

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.

Input parameters:

- `businessName` (string, required): 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.
- `email` (string, required): The customer's email. Required — this is how they are contacted.
- `entityType` (string, required): Entity type, e.g. "LLC", "S-Corp", "C-Corp", or "Not sure" if the user hasn't decided.
- `fullName` (string, required): The customer's full name.
- `phone` (string): Optional phone number.
- `state` (string, required): Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC.

### `submit_order` (~217 tokens)

Submit the formation order

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.

Input parameters:

- `businessName` (string, required): Proposed company name.
- `description` (string): What the business does. Optional.
- `email` (string, required): The customer's email.
- `entityType` (string, required): Entity type, e.g. "LLC", or "Not sure".
- `fullName` (string, required): The customer's full name.
- `phone` (string): Optional phone number.
- `state` (string, required): Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC.
- `userConfirmed` (boolean, required): Must be true. Set only after the user has seen the preview_order summary and explicitly agreed to submit.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-filingdesk-data/api-mcp#diagnostics

## Score history

- 2026-09-22: 80
- 2026-09-21: 80
- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 77
- 2026-09-05: 77
- 2026-09-04: 76
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 75
- 2026-08-31: 75
- 2026-08-30: 74
- 2026-08-29: 74
- 2026-08-28: 73
- 2026-08-27: 73
- 2026-08-26: 72
- 2026-08-25: 71
- 2026-08-24: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://filingdesk.com/api/mcp
- Website: https://filingdesk.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-filingdesk-data/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-filingdesk-data/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-filingdesk-data/api-mcp