Logly
NPM · @LOGLY-UK/MCP · SCANNED SEP 29
Query your Logly web analytics — traffic, funnels and real-time visitors — from any MCP client.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- 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 133 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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
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
claude mcp add logly-uk-logly-mcp -- npx -y @logly-uk/mcp
{
"mcpServers": {
"logly-uk-logly-mcp": {
"command": "npx",
"args": [
"-y",
"@logly-uk/mcp"
]
}
}
} {
"servers": {
"logly-uk-logly-mcp": {
"command": "npx",
"args": [
"-y",
"@logly-uk/mcp"
]
}
}
} codex mcp add logly-uk-logly-mcp -- npx -y @logly-uk/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"logly-uk-logly-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@logly-uk/mcp"
],
"enabled": true
}
}
} openclaw mcp add logly-uk-logly-mcp --command npx --arg -y --arg @logly-uk/mcp
mcp_servers:
logly-uk-logly-mcp:
command: "npx"
args: ["-y", "@logly-uk/mcp"] {
"McpServers": {
"logly-uk-logly-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@logly-uk/mcp"
]
}
}
} assistant mcp add logly-uk-logly-mcp -t stdio -c npx -a -y @logly-uk/mcp
{
"mcpServers": {
"logly-uk-logly-mcp": {
"command": "npx",
"args": [
"-y",
"@logly-uk/mcp"
]
}
}
} 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.
- 29 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 26 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 29 Sept 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 →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
logly_breakdown ~129
Top pages, top referrers, top countries and device/browser split for a site over the given period.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set. |
| from | string | – | Range start, YYYY-MM-DD. Use together with 'to'. |
| site | string | yes | Logly site ID (slug). Call logly_list_sites to discover it. |
| to | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set. |
| from | string | – | Range start, YYYY-MM-DD. Use together with 'to'. |
| site | string | yes | Logly site ID (slug). Call logly_list_sites to discover it. |
| to | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set. |
| funnel_id | string | yes | Funnel 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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Logly 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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Logly 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).
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Logly 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days to look back: 7, 30 or 90. Defaults to 30. Ignored when 'from'/'to' are set. |
| from | string | – | Range start, YYYY-MM-DD. Use together with 'to'. |
| site | string | yes | Logly site ID (slug). Call logly_list_sites to discover it. |
| to | string | – | Range end, YYYY-MM-DD. Use together with 'from'. |
No output schema declared.
No examples provided.
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 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 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 29 September 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.