Atlas entry

`cryptopulse.pythonanywhere.com`

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

Observed 13 Nov 2026, 10:05 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 13 Nov 2026, 10:05 UTC
Signed: 13 Nov 2026, 10:06 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

13 Nov 2026, 10:05 UTC0 capabilities · MCP · MCP endpoint not mcpFirst observation
Fingerprint and versions
Fingerprint
70a89e9ce6b838c1f9416abd0fdea3cb546df1a3d3a8b34759db06b4e42f0810
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 10,548 of the top million for pythonanywhere.com. Link popularity: Majestic Million (CC BY 3.0)

com.pythonanywhere.cryptopulse/mcp
Listed
Official MCP Registry · first listed 24 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:cdb615fce6027c6a2e4e04107a01c149bb7604e0ed1cd88c4a486071699e48b6
Locator SHA-256: 17e607ebcc36a093fa83756c4ab47b99a336f3ddbc46f280f4525f3ee6e1b0a0
Snapshot generated: 13 Nov 2026, 10:41 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.