io.github.Surface-ops/server-track-lab
NPM · SERVER-TRACK-LAB-MCP
Send server-side conversions to Meta CAPI (live); Google validate-only, LinkedIn dry-run.
Available components
Last scanned (4 hours ago)
Scores higher than 36% of npm servers
Category Marketing and SEO
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
- 30 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 356 tokens (~118/item across 3 items; 3 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 Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "track_event" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 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
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.
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.
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 47
First indexed and scored.
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 25 Oct 2026 · Analysed npm/server-track-lab-mcp@0.1.0
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 | 30 |
| 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 →
get_stats Get usage stats ~45
This month's accepted, deduplicated and failed events for the workspace, plan and free allowance, and the usage split between human/app and agent/bot traffic (both billed the same).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
test_meta_connection Test the Meta connection ~54
Send one synthetic Lead to Meta Events Manager → Test events using the workspace's saved Meta pixel, token and test_event_code. Returns sent/skipped/failed with Meta's error and a hint. Does not affect production data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
track_event Send a conversion event ~257
Send one server-side conversion (lead, signup, purchase, subscribe...) to server-track-lab, which normalizes, SHA-256 hashes and dedupes it, then forwards it: Meta Conversions API live (with the workspace's own pixel/token), Google Data Manager API validate-only preview (nothing recorded), LinkedIn dry-run (not sent). Reuse the same event_id on retries; duplicates are free and not re-sent. Counts as billed usage (first 1,000/month free, then CA$2 per 1,000).
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217, required with value |
| destinations | array | – | – |
| event_id | string | yes | Stable unique id for this conversion (also used by Meta for Pixel dedup) |
| event_name | string | yes | e.g. lead, sign_up, purchase, subscribe, demo_booked |
| event_source_url | string | – | – |
| test | boolean | – | Mark as a test event |
| timestamp | string | – | ISO 8601; defaults to now |
| user | object | yes | At least one identifier (email, phone, external_id, fbp/fbc, gclid...) |
| value | number | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.Surface-ops/server-track-lab MCP server?
io.github.Surface-ops/server-track-lab runs locally as an npm package, launched with npx -y server-track-lab-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 · server-track-lab-mcp
claude mcp add surface-ops-server-track-lab -- npx -y server-track-lab-mcp
What is the io.github.Surface-ops/server-track-lab MCP server?
io.github.Surface-ops/server-track-lab is an MCP server listed in the public MCP registry as io.github.Surface-ops/server-track-lab. Send server-side conversions to Meta CAPI (live); Google validate-only, LinkedIn dry-run. This page covers its npm package (server-track-lab-mcp).
Is the io.github.Surface-ops/server-track-lab MCP server safe to use?
io.github.Surface-ops/server-track-lab scores 62 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 25 October 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 io.github.Surface-ops/server-track-lab MCP server expose?
io.github.Surface-ops/server-track-lab exposes 3 tools: track_event, test_meta_connection, get_stats. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Is the io.github.Surface-ops/server-track-lab MCP server still maintained?
io.github.Surface-ops/server-track-lab is still listed as active in the MCP registry. We last reached this channel on 25 October 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 io.github.Surface-ops/server-track-lab MCP server under?
io.github.Surface-ops/server-track-lab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.