Atlas entry

`api.savvly.com`

16 capabilities over MCP 2025-11-25. First atlas observation.

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

Capability facts

As observed from outside, at the time below

Observed: 13 Nov 2026, 07:05 UTC
Signed: 13 Nov 2026, 07:05 UTC

Protocols: MCP
Tools: 8
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

8 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, 07:05 UTC16 capabilities · MCP 2025-11-25 · MCP endpoint truncated · 1 incomplete inventory groupFirst observation
Fingerprint and versions
Fingerprint
f3ab6370b582af0657e3b29fa514c4e2d0c50fd31ae1b910b4812c2013b382bc (incomplete)
Passport schema
0.5.0, passport-semantic-v4
Consistency
MCP_PROMPTS_ADVERTISEMENT_LIST: indeterminate · MCP_RESOURCES_ADVERTISEMENT_LIST: match · MCP_TOOLS_ADVERTISEMENT_LIST: match · 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

com.savvly/savvly
Listed
Official MCP Registry · first listed 12 Nov 2026 · last listed 12 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:eea9b8e627a83a155534c1d15e695dd4bc135122b514ce9185fdf48ce95e70cf
Locator SHA-256: da49abfe267c3ad2efcb73139102b080e49be0640ddf252084cbeaf825c99785
Snapshot generated: 13 Nov 2026, 07:05 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.