Atlas entry
app. leadsranger. com
No capabilities retained; MCP observed, and the MCP endpoint was auth required. First atlas observation.
Atlas history
1 observation
- 0 capabilities · MCP · MCP endpoint auth requiredFirst observation
Fingerprint and versions
- Fingerprint
eb1fe9761d2f1e412b2ca4e45e3e093cafd7cada2e0224313cacd0f81185eb3e- 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
com.leadsranger/leads-rangerListedOfficial MCP Registry · first listed 3 Nov 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:52eedce7165a31e8882741864896712795946bddaed983c281116d1c749857a6- Locator SHA-256
4528d0a2a45b991c8c318886d0ebee32a90371ec6b62e119b0d99fa69fc77154- 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.

