Atlas entry

`jilliondb.com`

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

Observed 12 Nov 2026, 09:10 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 12 Nov 2026, 09:10 UTC
Signed: 12 Nov 2026, 09:11 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

12 Nov 2026, 09:10 UTC0 capabilities · MCP · MCP endpoint unreachableFirst observation
Fingerprint and versions
Fingerprint
2b5372acafd67462b31f4a74c8d4f0db50e146f66ca90e963b97a32a0491e10d
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.jilliondb/jilliondb
Listed
Official MCP Registry · first listed 12 Nov 2026 · last listed 12 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:e4dc59c00f502d7de5dd89dcf5e418eed46b1ac72c519768b4460f73d3a83f86
Locator SHA-256: b41269347c1f2b1ebdd0f177553c2b7ea5dd8ae1d4f1c5c786a248031a8c093a
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.