Atlas entry

`api.notecube.app`

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

Observed 13 Nov 2026, 17:01 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 13 Nov 2026, 17:01 UTC
Signed: 13 Nov 2026, 17:02 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, 17:01 UTC0 capabilities · MCP · MCP endpoint auth requiredFirst observation
Fingerprint and versions
Fingerprint
f19efa2521d1aef3c05c4eaf9a8f78a0f433ac3a06c2d41af64584d5184dba7a
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

app.notecube/notecube
Listed
Official MCP Registry · first listed 28 Oct 2026 · last listed 28 Oct 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:a960f88f181dbc4350bad630b54db8a1b2805768f5e864cbd5fe64525251149e
Locator SHA-256: 5c50119434f2cc2578a28f6625732e26caf2a1fe1a711c9a31109426e8481b61
Snapshot generated: 13 Nov 2026, 19:02 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.