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

Logly

NPM · @LOGLY-UK/MCP · SCANNED AUG 3

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

Available components

+20 this week 66 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @logly-uk/mcp

# add to Claude Code
claude mcp add logly-uk-logly-mcp -- npx -y @logly-uk/mcp
# add to Codex CLI
codex mcp add logly-uk-logly-mcp -- npx -y @logly-uk/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "logly-uk-logly-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@logly-uk/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add logly-uk-logly-mcp --command npx --arg -y --arg @logly-uk/mcp
# ~/.hermes/config.yaml
mcp_servers:
  logly-uk-logly-mcp:
    command: "npx"
    args: ["-y", "@logly-uk/mcp"]
// mcp.json
{
  "mcpServers": {
    "logly-uk-logly-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@logly-uk/mcp"
      ]
    }
  }
}
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.

  • 3 Aug 26 +46
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Security disclosure: unverified → fail functional
    • Schema quality: unverified → excellent functional
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Licence: MIT functional
  • 2 Aug 26 −1
    • Malware scan: unverified → pass security
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 46

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/@logly-uk/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

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.

Tool Tokens
logly_breakdown ~129

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

NameTypeReqDescription
daysintegerDays to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set.
fromstringRange start, YYYY-MM-DD. Use together with 'to'.
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.
tostringRange 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
daysintegerDays to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set.
fromstringRange start, YYYY-MM-DD. Use together with 'to'.
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.
tostringRange 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
daysintegerDays 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
daysintegerDays to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set.
fromstringRange start, YYYY-MM-DD. Use together with 'to'.
sitestringyesLogly site ID (slug). Call logly_list_sites to discover it.
tostringRange end, YYYY-MM-DD. Use together with 'from'.

No output schema declared.

No examples provided.