GitHub repo analytics: stars, trending, code search, contributor maps for project research.
Free
Nothing to run from here
Clamp Sh is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Analytics MCP server for Clamp Analytics. Gives Claude, Cursor, VS Code, Windsurf, and Cline tools for traffic, pages, events, revenue, errors, funnels, cohorts, and alerts. Stdio + hosted Remote MCP.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @clamp-sh/mcp
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> Analytics MCP server for Clamp Analytics. Gives Claude, Cursor, VS Code, Windsurf, and Cline tools for traffic, pages, events, revenue
Publishernot claimed
CLAll 1 server
@clamp-sh1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Clamp Sh as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add clamp-sh-mcp -- npx -y @clamp-sh/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
33 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all Clamp projects this credential can access. Returns each project
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Lists custom events (user-defined). Excludes all $-prefixed system and canonical revenue events (\
Takes no parameters.
Example callreturns →
Return what
Takes no parameters.
Example callreturns →
Top distinct *values* a string-typed property has taken on a specific event in the period, ranked by occurrence count. Useful when you need to know the value space before filtering — e.g. cohort definitions, segment filters,
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
One call that returns the canonical revenue dashboard. Bundles every KPI tile + per-plan + per-product rollup + prior-period comparison into one round-trip. Use this for
Takes no parameters.
Example callreturns →
Cohort revenue retention. Anchors each customer at their first cohort event (default: \
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Errors deduplicated by server-computed fingerprint, with counts and first/last-seen timestamps. The triage view: which bugs are firing most often, affecting the most users, or showing up newly in the period. Each group is one fingerprint (a bug). \
Takes no parameters.
Example callreturns →
Error count over time, bucketed hourly or daily. Optionally scoped to one fingerprint. Use this to spot regressions (
Takes no parameters.
Example callreturns →
Breadcrumbs leading to one error: the events from the same session, before the error timestamp, in chronological order. The
Takes no parameters.
Example callreturns →
Traffic metrics over time as date buckets. Returns [{ date, count }] sorted ascending, where \
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Retrieve and re-evaluate a previously created funnel against current data for the specified period. Without a \
Takes no parameters.
Example callreturns →
Delete a saved funnel by name. Irreversible — the agent should confirm intent with the user before calling this. The underlying event data isn
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List saved cohorts for the project. With \
Takes no parameters.
Example callreturns →
Compute the retention curve for a saved cohort. For each requested window (e.g. day 1, 7, 14, 30 after the cohort
Takes no parameters.
Example callreturns →
Compare 2–10 saved cohorts side-by-side on retention. Returns each cohort
Takes no parameters.
Example callreturns →
Delete a saved cohort by name. Irreversible — the agent should confirm intent with the user before calling this. The underlying event data isn
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List all alerts configured for a project. Returns each alert
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Aggregate visitors and pageviews grouped by a single dimension. The \
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Aggregate (entry_page → exit_page) session pairs. Returns the top pairs with how many sessions followed each path, average pages per session, average duration in seconds, and a bounce flag. Use to answer
Takes no parameters.
Example callreturns →
Per-page metrics with a selectable detail level. The \
Takes no parameters.
Example callreturns →
Google Search Console query metrics — the pre-click side of search. Returns the search terms that drove clicks to the site, with clicks, impressions, CTR (0–1), and average position (1 = top of results), over the period. Sourced from the project
Takes no parameters.
Example callreturns →
The pre-click → post-click join: Search Console metrics per landing page, joined to what those organic-search visitors actually did. For each page that gets search traffic, returns clicks / impressions / average position (from Search Console) alongside \
Takes no parameters.
Example callreturns →
See who is on the site in the last N minutes. Returns the active visitor count plus top pages, top referrers, and top countries within that window. Defaults to 5 minutes; max 60. Use during incidents (
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Startermost installed
$19 / month
- 15,000 calls a month, included
- 180 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Growth
$49 / month
- 75,000 calls a month, included
- 900 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Scale
$99 / month
- 300,000 calls a month, included
- 3,600 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $19 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 99 / 100
Release 5.5.2 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digesta137761583639154875e14961da82ef30c4be59b96be652354102d28f2f28fa1
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (33 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| projects.list | no tags | |
| traffic.overview | no tags | |
| events.list | no tags | |
| events.observed_schema | no tags | |
| events.property_values | no tags | |
| revenue.sum | no tags | |
| revenue.summary | no tags | |
| revenue.retention | no tags | |
| users.journey | no tags | |
| errors.list | no tags | |
| errors.groups | no tags | |
| errors.timeline | no tags | |
| errors.context | no tags | |
| traffic.timeseries | no tags | |
| funnels.create | no tags | |
| funnels.list | no tags | |
| funnels.delete | no tags | |
| cohorts.create | no tags | |
| cohorts.list | no tags | |
| cohorts.retention | no tags | |
| cohorts.compare | no tags | |
| cohorts.delete | no tags | |
| alerts.create | no tags | |
| alerts.list | no tags | |
| alerts.delete | no tags | |
| traffic.breakdown | no tags | |
| traffic.compare | no tags | |
| sessions.paths | no tags | |
| pages.engagement | no tags | |
| search.queries | no tags | |
| search.landing_pages | no tags | |
| traffic.live | no tags | |
| docs.search | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta137761583639154
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 5.5.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
5.5.2
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Clamp Sh in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.