Skip to content

FilingDesk Data MCP server

com.filingdesk/datafilingdesk.comstreamable-httpv0.3.0Scanned

US LLC filing fees, annual-report deadlines and naming-rule checks, from official state sources.

8 tools: 1 can delete or cancel things, 1 change things and 6 only read.

Tools: 1 delete, 0 irreversible, 1 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the FilingDesk Data MCP server can do

The FilingDesk Data MCP server is published by filingdesk.com, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: submit_order) and create or change data (1 tool: check_llc_name). 6 tools only read.

2 tools read private data (get_annual_report_deadline and list_filing_states); 1 tool brings in text other people can write (submit_order).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 1Claude Code: deny
  • submit_orderSubmits a formation order to FilingDesk.Reads text others writeNo findings

    Why it is in this group

    • The name "submit_order" says "submit": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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-…).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 1Claude Code: ask
  • check_llc_nameScreens a proposed business name against state naming rules.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • compare_formation_optionsReturns 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 …No findings

    Why it is in this group

    • The name "compare_formation_options" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • compare_llc_costsRanks US states by LLC cost: the one-time formation fee, the recurring state fee, or the first-year total (formation plus one recurring period).No findings

    Why it is in this group

    • The name "compare_llc_costs" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_annual_report_deadlineCalculates 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 data…Reads private dataNo findings

    Why it is in this group

    • The name "get_annual_report_deadline" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_llc_feesReturns 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,…No findings

    Why it is in this group

    • The name "get_llc_fees" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_filing_statesLists 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 +…Reads private dataNo findings

    Why it is in this group

    • The name "list_filing_states" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • preview_orderValidates and prices a formation order and returns the exact summary that would be submitted, WITHOUT submitting anything (no side effects).No findings

    Why it is in this group

    • The name "preview_order" says "preview": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://filingdesk.com/api/mcp: tools/list returned 8 tools to an anonymous client, including submit_order (destructive), check_llc_name (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.3.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__data__get_llc_fees",
      "mcp__data__compare_llc_costs",
      "mcp__data__get_annual_report_deadline",
      "mcp__data__list_filing_states",
      "mcp__data__compare_formation_options",
      "mcp__data__preview_order"
    ],
    "ask": [
      "mcp__data__check_llc_name"
    ],
    "deny": [
      "mcp__data__submit_order"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as data. Review it before you use it.

Capability tags behind 3 rules
  • mcp__data__get_annual_report_deadline private-data
  • mcp__data__list_filing_states private-data
  • mcp__data__submit_order untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.filingdesk/data/verify?hash=3427b89ac7108871c6aefa79730c05065785b4583c8ce998950a59becb65d64e" | jq -e '.changed == false'

Pinned hash 3427b89ac710, from Nov 13, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.filingdesk/data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.filingdesk/data
[![Anlyon Radar](https://radar.anlyon.com/badge/com.filingdesk/data.svg)](https://radar.anlyon.com/servers/com.filingdesk/data)

Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.

FilingDesk Data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FilingDesk Data MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FilingDesk Data MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: submit_order.

Can the FilingDesk Data MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FilingDesk Data MCP server have?

8 tools: 1 destructive, 1 write, 6 read. submit_order, check_llc_name, get_llc_fees, compare_llc_costs, get_annual_report_deadline, list_filing_states, compare_formation_options and preview_order.

Does the FilingDesk Data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FilingDesk Data MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FilingDesk Data MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.