Atlas entry

`mcp.landingfolio.com`

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

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

Capability facts

As observed from outside, at the time below

Observed: 6 Nov 2026, 15:04 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:04 UTC0 capabilities · MCP · MCP endpoint auth requiredFirst observation
Fingerprint and versions
Fingerprint
3bfd8427c26ce7941a68915af799b7e7c80c32bdb50bb902a756290b1df3c69c
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 221,410 of the top million for landingfolio.com. Link popularity: Majestic Million (CC BY 3.0)

io.github.dannypostma/landingfolio-mcp
Listed
Official MCP Registry · first listed 6 Nov 2026 · last listed 6 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:be2695cfea2dfa42cf8863517c17e8bb29962d9f2ca785a34e589ca900b3d458
Locator SHA-256: 25fa8fe03b2099be57ea1ab72485c5df1a26c90ef76ecb3c59ffd5636d84e8c2
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.