Atlas entry

`uproar.chat`

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

Observed 14 Nov 2026, 04:01 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 14 Nov 2026, 04:01 UTC
Signed: 14 Nov 2026, 04:01 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

14 Nov 2026, 04:01 UTC0 capabilities · MCP · MCP endpoint auth requiredFirst observation
Fingerprint and versions
Fingerprint
323d0dada6a9f7bd9f422e4c19583c2a4a67890225cdf615e1a23cb918dc453a
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

chat.uproar/uproar
Listed
Official MCP Registry · first listed 16 Sep 2026 · last listed 31 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:ac2adfe43e2860e5033159bc5ad4390d044febb38b107084455e419fd8bfed1e
Locator SHA-256: b03dc472e6feecfdf1a1433d98e9d8dee718275cc6759dc253a326e4d13243d7
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.