Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Logly

NPM · @LOGLY-UK/MCP

Query your Logly web analytics — traffic, funnels and real-time visitors — from any MCP client.

Available components

0 this week 80 Trust /100

Last scanned (16 hours ago)

Scores higher than 66% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 186 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability84
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 665 tokens (~83/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 17 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 16 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 14 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 13 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@logly-uk/mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~665 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
logly_breakdown ~129

Top pages, top referrers, top countries and device/browser split for a site over the given period.

NameTypeReqDescription
daysinteger–Days to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set.
fromstring–Range start, YYYY-MM-DD. Use together with 'to'.
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.
tostring–Range end, YYYY-MM-DD. Use together with 'from'.

No output schema declared.

No examples provided.

logly_events ~128

Custom event counts for a site (events sent via logly('event', ...)) over the given period.

NameTypeReqDescription
daysinteger–Days to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set.
fromstring–Range start, YYYY-MM-DD. Use together with 'to'.
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.
tostring–Range end, YYYY-MM-DD. Use together with 'from'.

No output schema declared.

No examples provided.

logly_funnel_results ~76

Completion counts and drop-off per step for one conversion funnel.

NameTypeReqDescription
daysinteger–Days to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set.
funnel_idstringyesFunnel ID, from logly_funnels.

No output schema declared.

No examples provided.

logly_funnels ~48

List the conversion funnels defined for a site, with their IDs and step sequences.

NameTypeReqDescription
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.

No output schema declared.

No examples provided.

logly_install_snippet ~64

Return the Logly tracking snippet for a site — the single <script> tag to add to the site's <head>. Works offline, no API call.

NameTypeReqDescription
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.

No output schema declared.

No examples provided.

logly_list_sites ~36

List every website in the authenticated Logly account with its site ID. Start here to find the site ID the other tools need.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

logly_realtime ~47

Visitors currently active on a site (real-time, the last few minutes).

NameTypeReqDescription
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.

No output schema declared.

No examples provided.

logly_stats ~137

Traffic totals for a site — pageviews, sessions, visitors, bounce rate, average duration — plus a daily series and a comparison against the previous period.

NameTypeReqDescription
daysinteger–Days to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set.
fromstring–Range start, YYYY-MM-DD. Use together with 'to'.
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.
tostring–Range end, YYYY-MM-DD. Use together with 'from'.

No output schema declared.

No examples provided.

Install

How do I install the Logly MCP server?

Logly runs locally as an npm package, launched with npx -y @logly-uk/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @logly-uk/mcp

# add to Claude Code
claude mcp add logly-uk-logly-mcp -- npx -y @logly-uk/mcp
Common questions

What is the Logly MCP server?

Logly is an MCP server listed in the public MCP registry as io.github.logly-uk/logly-mcp. Query your Logly web analytics, traffic, funnels and real-time visitors, from any MCP client. This page covers its npm package (@logly-uk/mcp).

Is the Logly MCP server safe to use?

Logly scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Logly MCP server expose?

Logly exposes 8 tools: logly_list_sites, logly_stats, logly_breakdown, logly_realtime, logly_events, and 3 more. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.

Is the Logly MCP server still maintained?

Logly is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Logly MCP server under?

Logly declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Logly MCP server?

VerifyMCP ran 15 checks on Logly, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Logly: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.