Home / MCP registry index / com.ducktax/ducktax
Duck Tax
com.ducktax/ducktax in the official MCP registry.
Endpoint https://ducktax.com/api/mcp.
The registry describes it as: Check micro-entity company accounts: raw figures in, validated balance sheet and deadlines out.
We read its 20 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
check_accounts dormant_figures totals_to_figures late_filing_penalty list_jurisdictions sample_accounts lookup_company search_companies get_prior_year_figures explain_accounts categorise_transactions check_filing_extension draft_extension_reason list_saved_filings save_filing delete_filing track_company_deadlines list_tracked_companies untrack_company_deadlines server_status
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-ducktax-ducktax)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.