mcp-registry/com.dropwatchhq/compliance-radar · v1.0.0
As of 2026-10-26 19:52 UTC, the Dropwatchhq Compliance Radar MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
US small-biz & foreign-LLC filing deadlines: FinCEN BOI, IRS 5472, franchise tax, 1099 (sourced).
Point your MCP client at this streamable-http endpoint: https://compliance.dropwatchhq.com/mcp
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
7 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.dropwatchhq%2Fcompliance-radar/fixes
{
"name": "build_checklist",
"description": "Build a personalized list of likely recurring compliance obligations and their NEXT deadline dates from an entity profile (entity type + state + formation date + a few flags). Pure date arithmetic over officially-cited rules — NOT individualized legal or tax advice. Always verify against the cited sources and a licensed professional.",
"inputSchema": {
"type": "object",
"required": [
"entityType",
"state"
],
"properties": {
"state": {
"type": "string",
"description": "2-letter formation/registration state, e.g. 'DE'."
},
"entityType": {
"enum": [
"llc",
"c-corp",
"s-corp",
"sole-prop",
"partnership"
],
"type": "string"
},
"foreignOwned": {
"type": "boolean",
"description": "True if owned (>=25% or wholly) by a non-US person."
},
"hasEmployees": {
"type": "boolean"
},
"formationDate": {
"type": "string",
"description": "Entity formation date YYYY-MM-DD (drives anniversary-based deadlines)."
},
"paysContractors": {
"type": "boolean",
"description": "True if you pay $600+ to US contractors (1099 obligations)."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "create_deadline_tracker",
"description": "Save an entity profile plus an email and/or webhook URL to receive FREE recurring reminders before each upcoming compliance deadline. Returns a manage id. INFORMATIONAL reminders only — not legal or tax advice.",
"inputSchema": {
"type": "object",
"properties": {
"email": {
"type": "string",
"description": "Where to send reminders (email or webhook required)."
},
"state": {
"type": "string"
},
"webhook": {
"type": "string",
"description": "POST target for reminder JSON (email or webhook required)."
},
"entityType": {
"enum": [
"llc",
"c-corp",
"s-corp",
"sole-prop",
"partnership"
],
"type": "string"
},
"remindDays": {
"type": "number",
"description": "Days of lead time before a deadline to remind (default 30, 1-120)."
},
"foreignOwned": {
"type": "boolean"
},
"hasEmployees": {
"type": "boolean"
},
"formationDate": {
"type": "string",
"description": "YYYY-MM-DD"
},
"paysContractors": {
"type": "boolean"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "get_obligation",
"description": "Return full detail for a single obligation by id: what it is, who must file, the deadline, the penalty for missing it, and a link to the OFFICIAL government source with a dated 'verified as of'. INFORMATIONAL ONLY — not legal or tax advice.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Obligation id, e.g. 'fincen-boi', 'irs-5472', 'de-franchise-llc'."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.dropwatchhq/compliance-radar"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.dropwatchhq/compliance-radar"}) over MCP.
build_checklist ~281 tokenslist_obligations ~254 tokenscreate_deadline_tracker ~251 tokensget_obligation ~126 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.dropwatchhq%2Fcompliance-radar?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.dropwatchhq%2Fcompliance-radar?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.dropwatchhq%2Fcompliance-radar.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.dropwatchhq%2Fcompliance-radar.svg :target: https://glimind.com/server/mcp-registry%2Fcom.dropwatchhq%2Fcompliance-radar?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:124b86f2bcec1b1b…, first seen 2026-10-17, included at leaf 8691 of 75,135. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable productivity servers · most reliable compliance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 19:52 UTC, the Dropwatchhq Compliance Radar MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Dropwatchhq Compliance Radar MCP server advertises 4 tools, including build_checklist, create_deadline_tracker, get_obligation, list_obligations.
Point your MCP client at this streamable-http endpoint: https://compliance.dropwatchhq.com/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.