Lodd MCP Server

@lodd/mcp-server npm v0.1.18

Published by @lodd — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

First-party web analytics for AI agents. Add a script, query your own traffic over MCP.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 43

Each tool and what it can reach — statically extracted from the published source.

  • get_pagesingests untrusted input
  • get_performanceingests untrusted input
  • authenticateno sensitive capability
  • create_annotationno sensitive capability
  • create_api_keyno sensitive capability
  • create_siteno sensitive capability
  • create_trackable_linkno sensitive capability
  • exclude_my_ipno sensitive capability
  • get_active_actorsno sensitive capability
  • get_actor_activityno sensitive capability
Show 33 more tools ↓
  • get_actor_retentionno sensitive capability
  • get_ai_trafficno sensitive capability
  • get_analyticsno sensitive capability
  • get_bot_reportno sensitive capability
  • get_content_groupsno sensitive capability
  • get_conversion_pagesno sensitive capability
  • get_countriesno sensitive capability
  • get_dropoff_destinationsno sensitive capability
  • get_entry_exit_pagesno sensitive capability
  • get_event_countsno sensitive capability
  • get_event_sequencesno sensitive capability
  • get_event_timeseriesno sensitive capability
  • get_eventsno sensitive capability
  • get_funnelno sensitive capability
  • get_link_clicksno sensitive capability
  • get_realtimeno sensitive capability
  • get_session_pathsno sensitive capability
  • get_session_scoresno sensitive capability
  • get_snapshotno sensitive capability
  • get_source_conversionsno sensitive capability
  • get_tech_breakdownno sensitive capability
  • get_timeseriesno sensitive capability
  • get_traffic_sourcesno sensitive capability
  • get_usageno sensitive capability
  • list_annotationsno sensitive capability
  • list_api_keysno sensitive capability
  • list_membersno sensitive capability
  • list_sitesno sensitive capability
  • list_trackable_linksno sensitive capability
  • remove_memberno sensitive capability
  • revoke_api_keyno sensitive capability
  • share_siteno sensitive capability
  • verify_codeno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.18 latest A 96/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/lodd-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/lodd-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/lodd-mcp-server"><img src="https://mcptrustchecker.com/registry/lodd-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/lodd-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @lodd/mcp-server --online

Use the free API → How scoring works

More in Analytics & Monitoring