Atlas entry

`observable-backend-stack-generator.getvda.ai`

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

Observed 7 Nov 2026, 11:04 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

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

7 Nov 2026, 11:04 UTC0 capabilities · MCP · MCP endpoint protocol errorFirst observation
Fingerprint and versions
Fingerprint
956f96d1150dabec2728f2397a344b36fe52b81dcc684fc1936e314d5e1d9629
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

ai.getvda/observable-backend-stack-generator
Listed
Official MCP Registry · first listed 12 Sep 2026 · last listed 23 Oct 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:25bbf1d161908060a8521201842072002f396f9dcf0165ea56779173e8fa4f9e
Locator SHA-256: 36bbcbd28c25401017300c32f471fe0ebdd734912dd2238aafb3d9c4a9f032f2
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.