Atlas entry

`mymedi-ai.com`

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

Observed 6 Nov 2026, 15:05 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

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

6 Nov 2026, 15:05 UTC0 capabilities · MCP · MCP endpoint auth requiredFirst observation
Fingerprint and versions
Fingerprint
352439366eb5ba0f4e99ab63e5eb1c3b0522ef8527ccf802e21e05ce4c55a00c
Passport schema
0.6.0, passport-semantic-v5
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

io.github.MyMedi-AI/mcp-server
Listed
Official MCP Registry · first listed 5 Nov 2026 · last listed 5 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:a4853a8e89b9e2016e204a41c05c006445158f233ca7fb4cf08f94a4d62eb692
Locator SHA-256: ba7dea4f76bce25af2381177a3df1cccd547bbd0a9430610d501982ea238140e
Snapshot generated: 11 Nov 2026, 22:36 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.