Atlas entry

`robotsgate.mike-tusa.workers.dev`

4 capabilities over MCP 2026-07-28. First atlas observation.

Observed 12 Nov 2026, 15:14 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 12 Nov 2026, 15:14 UTC
Signed: 12 Nov 2026, 17:06 UTC

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

4 tools examined; 3 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

12 Nov 2026, 15:14 UTC4 capabilities · MCP 2026-07-28 · MCP endpoint validFirst observation
Fingerprint and versions
Fingerprint
5e1217c3b3311e1916456a2d8df1c9d564d3f8812bad62af6774f004bff2353e
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

dev.workers.mike-tusa.robotsgate/robotsgate
Listed
Official MCP Registry · first listed 3 Nov 2026 · last listed 3 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:f10abe2959a5a7b628bf67224a686c93b8f6ce3a24dc30b8eef025aff3d2fd71
Locator SHA-256: 59c4b6e3af0b6c9c2361ebfb3bcd0be5401f1fcfa443b65b7e31a309ad4c0935
Snapshot generated: 13 Nov 2026, 00:06 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.