Atlas entry

`nocodeexits.com`

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

Observed 13 Nov 2026, 20:25 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 13 Nov 2026, 20:25 UTC
Signed: 13 Nov 2026, 21:47 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: Baseline for labelled observation
Label status: Current

Atlas history

1 observation

13 Nov 2026, 20:25 UTC0 capabilities · MCP · MCP endpoint unreachableFirst observation
Fingerprint and versions
Fingerprint
9ad2573c06b4cd4507b2874335ab7a77e00f990bd56dcca7fe3ed4e209be8e6b
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

com.nocodeexits/nocodeexits
Listed
Official MCP Registry · first listed 23 Sep 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:67f7a1ebca3a9e23951afc6ea2b3ed09ef3aa01aafb5bccb7805412150440618
Locator SHA-256: 3dc01e667c917be6a518d7a749aa22c3d90adeba3b45b104c9c3dbf285f5b2f4
Snapshot generated: 14 Nov 2026, 08:50 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.