mcpbeat Sign in

Hooddue MCP Server

answering

Hooddue is answering right now. Last checked 1 min ago. It exposes 5 tools.

Restaurant fire-safety & service-interval tracking (NFPA 96/17A) — read-only demo tools.

Uptime history 22 days of history
22 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
245 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Hooddue every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add hooddue --transport http https://hooddue.artificl.us/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "hooddue": {
      "url": "https://hooddue.artificl.us/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.hooddue]
url = "https://hooddue.artificl.us/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "hooddue": {
      "url": "https://hooddue.artificl.us/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "hooddue": {
      "url": "https://hooddue.artificl.us/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

services
get_services_due
List services and permits due within the next N days (default 30), including hood cleanings, suppression inspections, and permit renewals.
search_services
Search kitchen compliance intervals by area, system, service type, or permit. Returns matching records with next due date and status.
compliance
get_compliance_summary
Get the kitchen compliance summary: totals for tracked intervals, not scheduled, overdue with policy risk, due this week, and awaiting tags.
export
export_compliance_log
Export the full kitchen compliance log as CSV text (area, service, next due, status, chase history).
overdue
list_overdue_services
List overdue fire safety and health compliance intervals — the ones that create insurance and inspection exposure right now. Most serious first.

Endpoints

URLTransportStateLatencyChecked
https://hooddue.artificl.us/mcp streamable-http answering 220 ms 1 min ago

Alternatives to Hooddue

same job, measured the same way
Subproof
by artificl

Subcontractor COI & paperwork tracking for general contractors — read-only demo tools.

5 tools answering
Vendorping
by artificl

Vendor document & expiry tracking for septic operators — read-only live demo board tools.

5 tools answering
Credcycle
by artificl

Provider credentialing & payer-enrollment tracking for medical practices — read-only demo tools.

5 tools answering
Driverfile
by artificl

DOT driver qualification file tracking for small motor carriers — read-only demo tools.

5 tools answering
Deawatch
by artificl

DEA registration & controlled-substance authority tracking for prescribers — read-only demo.

5 tools answering
Weeek MCP
by yolkins

Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools.

118 installs/wk local only
Com
by com-muovi

Read-only MCP server for Muovi, Argentina's trust-first local services marketplace (6 tools).

114 installs/wk 6 tools answering
Eds MCP Server
by focusgts

41 tools for Adobe Edge Delivery Services: read, audit, track, monitor, fix, publish, undo — safely.

131 installs/wk local only

Hooddue — questions

Answers built from our own checks of this server.

What can Hooddue do?
It exposes 5 tools, read directly from the server on our last check. Among them: export_compliance_log, get_compliance_summary, get_services_due, list_overdue_services, search_services. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Hooddue working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 245 ms. The bar chart above shows every period we have measured.
How do I connect Hooddue?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Hooddue need an API key?
No. Hooddue completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Hooddue?
It answers our handshake in 245 ms on average, which is faster than 65% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.