Koskamo

HoodDue MCP

HoodDue is a restaurant fire-safety and service-interval tracking tool for NFPA 96/17A compliance. The MCP server provides read-only access to live records, allowing AI assistants to query due dates, overdue items, and contractor details to answer compliance questions.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

HoodDue MCP logo, by ArtificlVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Artificl
MCP endpoint (Streamable HTTP)
https://hooddue.artificl.us/mcp
Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (5)

5 of 5 have a description · 0 of 5 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to artificl.us ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Query when specific hood systems are next due for cleaning
  • Identify overdue inspections that could affect insurance claims
  • Check contractor insurance certificate status
  • Verify compliance status before a fire marshal visit

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: us.artificl/hooddue@1.0.0Project website

Protocol and capabilities

Server
hooddue 0.1.0
MCP protocol negotiated in check
2025-11-25
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

5 advertised

search_services
Advertised by the server during the last successful anonymous check.

Search kitchen compliance intervals by area, system, service type, or permit. Returns matching records with next due date and status.

search_services input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "query": {
      "type": "string",
      "description": "Text to match against area or service (case-insensitive; shorthand like \"Ansul\" or \"liquor license\" works). Omit to list everything."
    }
  }
}
list_overdue_services
Advertised by the server during the last successful anonymous check.

List overdue fire safety and health compliance intervals — the ones that create insurance and inspection exposure right now. Most serious first.

list_overdue_services input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
get_services_due
Advertised by the server during the last successful anonymous check.

List services and permits due within the next N days (default 30), including hood cleanings, suppression inspections, and permit renewals.

get_services_due input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "days": {
      "type": "number",
      "description": "Look-ahead window in days (default 30)."
    }
  }
}
get_compliance_summary
Advertised by the server during the last successful anonymous check.

Get the kitchen compliance summary: totals for tracked intervals, not scheduled, overdue with policy risk, due this week, and awaiting tags.

get_compliance_summary input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
export_compliance_log
Advertised by the server during the last successful anonymous check.

Export the full kitchen compliance log as CSV text (area, service, next due, status, chase history).

export_compliance_log input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
384 ms
95th percentile latency
384 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 384 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http hooddue-mcp https://hooddue.artificl.us/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add hooddue-mcp --url https://hooddue.artificl.us/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable hooddue-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "hooddue-mcp": {
      "url": "https://hooddue.artificl.us/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "hooddue-mcp": {
      "type": "streamableHttp",
      "url": "https://hooddue.artificl.us/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start hooddue-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "hooddue-mcp": {
      "type": "http",
      "url": "https://hooddue.artificl.us/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http hooddue-mcp https://hooddue.artificl.us/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://hooddue.artificl.us/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "hooddue-mcp": {
      "serverUrl": "https://hooddue.artificl.us/mcp"
    }
  }
}

Let your agent find its tools

Find servers like HoodDue MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,453

Do you run HoodDue MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing