Atlas entry

`mcp.doola.com`

No capabilities retained; MCP observed, and the MCP endpoint was auth required. First atlas observation.

Observed 6 Nov 2026, 20:04 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 6 Nov 2026, 20:04 UTC
Signed: 6 Nov 2026, 22:57 UTC

Protocols: MCP
Tools: 0
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

0 tools examined; 0 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, 20:04 UTC0 capabilities · MCP · MCP endpoint auth requiredFirst observation
Fingerprint and versions
Fingerprint
e8343ec05aedf128deeb03b8876dfb46c356a99d9c88a261c635fd140c96a734
Passport schema
0.5.0, passport-semantic-v4
Consistency
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

Majestic link rank 107,846 of the top million for doola.com. Link popularity: Majestic Million (CC BY 3.0)

io.github.doolahq/doola
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:5856f612cdfcbaaf89c3f70e59a8c08da3d8e3bc965c57d8581bfd238f76c09c
Locator SHA-256: 4a9fd3a2ab77c2cf0abd25dfcbb05401bd00437f9a5eec538f53040e2cdbb75c
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.