Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

us.artificl/hooddue

REMOTE · HOODDUE.ARTIFICL.US · SCANNED AUG 19

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

+4 this week 68 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 229 tokens (~45/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · hooddue.artificl.us

# add to Claude Code
claude mcp add --transport http us-artificl-hooddue https://hooddue.artificl.us/mcp
# ~/.codex/config.toml
[mcp_servers.us-artificl-hooddue]
url = "https://hooddue.artificl.us/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "us-artificl-hooddue": {
      "type": "remote",
      "url": "https://hooddue.artificl.us/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add us-artificl-hooddue --url https://hooddue.artificl.us/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  us-artificl-hooddue:
    url: "https://hooddue.artificl.us/mcp"
// mcp.json
{
  "mcpServers": {
    "us-artificl-hooddue": {
      "type": "http",
      "url": "https://hooddue.artificl.us/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 19 Aug 2026 · Probed https://hooddue.artificl.us/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hooddue.artificl.us CN=WR3,O=Google Trust Services,C=US 6 Aug 2026 4 Nov 2026 RSA 2048 SHA256-RSA b0f111bc660a78dc104ccc52546826b7
SANs: hooddue.artificl.us
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
DNSSEC insecure

Validation of hooddue.artificl.us. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
us. present 59017 8 Verified
artificl.us. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hooddue.artificl.us/mcp Verified 200
http (plaintext) http://hooddue.artificl.us/mcp HTTPS enforced 302 https://hooddue.artificl.us/mcp
MCP tools · 5 exposed · ~229 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
export_compliance_log ~32

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_compliance_summary ~37

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_services_due ~54

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

NameTypeReqDescription
daysnumberLook-ahead window in days (default 30).

No output schema declared.

No examples provided.

list_overdue_services ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_services ~72

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

NameTypeReqDescription
querystringText to match against area or service (case-insensitive; shorthand like "Ansul" or "liquor license" works). Omit to list everything.

No output schema declared.

No examples provided.