# Scope Analytics (io.github.wally827/scope-analytics-mcp@0.1.3) > Source: > Published: 2026-09-09 00:07:40+00:00 [← Index](/leaderboard) # Scope Analytics Install + query Scope analytics from an AI coding agent (Claude Code, Cursor, etc.). The current version, v0.1.3, was published to the official MCP registry on 2026-09-09. It is distributed as scope-analytics-mcp on PyPI, filed under Analytics by this index, and declares 2 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context. ## Using Scope Analytics in Claude, Cursor, Gemini CLI, Cline, or Zed? MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that). Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less ``` uv tool install mcpindex-gate && mcpindex-config-wire ``` [method](/methodology) Semantic screen found no manipulation pattern in the description. Conformance probe not yet run. `mcpindex.integrity.description` passINFO evidence“No malicious intent, only installation and querying”via static_description - - Semantic screen only - the deterministic conformance probe has not run on this server - - Confidence is reported but not yet calibrated (v1) - - Screen reads the tool description, not the live behavior - - advisory - - registry description only no input schema - - screen model 8b - - Still current: the description we screened is unchanged, re-checked against the registry - - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page. Own this server? [Screen its description →](/screen) ## That verdict was true at screening time (snapshot 2026-09-09). Contracts can change after screening, with no version bump. The gate pins Scope Analytics’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday. [See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold) Related: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift) People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land. ``` [Independent trust record for Scope Analytics](https://mcpindex.ai/server/io-github-wally827-scope-analytics-mcp) - screening verdict, registry provenance, and contract drift monitoring. Independent trust record for Scope Analytics - screening verdict, registry provenance, and contract drift monitoring. ``` A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does. ``` [![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-wally827-scope-analytics-mcp)](https://mcpindex.ai/server/io-github-wally827-scope-analytics-mcp) mcpindex verdict ``` `SCOPE_API_KEY` Your Scope project SECRET key (sk_...), from the Scope dashboard at https://scopeai.dev. `SCOPE_API_BASE` Scope backend base URL. Optional; defaults to https://api.scopeai.dev. [methodology](/methodology) [CreatorDBapp.creatordb/mcp](/server/app-creatordb-mcp) Creator discovery & analytics across YouTube, Instagram, TikTok (30M+) + brand/sponsor intel. [AIOProductOS MCPcom.aioproductos/mcp](/server/com-aioproductos-mcp) AIOProductOS: revenue, feedback, work and analytics on one customer record. 71 tools, 3 apps. [Umami Compassio.github.webcredo/umami-compass](/server/io-github-webcredo-umami-compass) Secure Umami Analytics MCP server for Cloud and self-hosted deployments