Atlas entry

`mcp.cryptoquant.com`

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

Observed 12 Nov 2026, 11:06 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 12 Nov 2026, 11:06 UTC
Signed: 12 Nov 2026, 11:09 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, 11:06 UTC0 capabilities · MCP · MCP endpoint auth requiredFirst observation
Fingerprint and versions
Fingerprint
8773fcac73ce57aaa4d6ea651379cd3fbd28d57b4649c85a62f84a0d4f5ec38e
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

Majestic link rank 23,171 of the top million for cryptoquant.com. Link popularity: Majestic Million (CC BY 3.0)

com.cryptoquant/mcp-server
Listed
Official MCP Registry · first listed 18 Sep 2026 · last listed 2 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:1c5a5dadff66c202e802bc6872f341ec5b9804ce4b2e82795fbfdea53afa4a3e
Locator SHA-256: e8c0786dd16cd36e31bc8c15149fea3ac1402fa89a556ea0154475eb95845183
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.