Atlas entry

`au-holidays-mcp.donniertf.workers.dev`

3 capabilities over MCP 2025-03-26. First atlas observation.

Observed 6 Nov 2026, 18:05 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 6 Nov 2026, 18:05 UTC
Signed: 6 Nov 2026, 23:20 UTC

Protocols: MCP
Tools: 3
Declared sign-in: None declared

Effects counted AI readings, beta

Moves money: 0
Deletes or cancels records: 0
Sends messages to people: 0
Changes permissions: 0
Runs code: 0
Asks a person: 0

3 tools examined; 1 counted above a measured threshold.

Declared vs read disagreements

Declared read-only, read as writing: 0
Declared destructive, read as not writing: 0
Declared non-destructive, read as deleting: 0
Declared closed-world, read as reaching out: 0

Change since previous: First observation
Label status: Current

Atlas history

1 observation

6 Nov 2026, 18:05 UTC3 capabilities · MCP 2025-03-26 · MCP endpoint validFirst observation
Fingerprint and versions
Fingerprint
bc68439c29a96a00516c01bbc779db8ff92a077ff55f009d344b552389af23a8
Passport schema
0.5.0, passport-semantic-v4
Consistency
MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable

Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.

Declared and observed

Tool declarations are unavailable for this entry.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

About this entry

io.github.donniertf-hub/au-holidays-mcp
Listed
Official MCP Registry · first listed 6 Nov 2026 · last listed 6 Nov 2026

Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal

Identity and snapshot

Target key: sha256:f8099df0e43babb8dcc2f2958c3f15b12ae9d4f51339557f64c75da18e4e4a2f
Locator SHA-256: 3e72c842de1597eb2ae56c772ed8b6f6172a3b095a302d1832a0893f3dc20853
Snapshot generated: 11 Nov 2026, 22:36 UTC

The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.