# Leadbay (io.github.leadbay/leadbay-mcp@0.37.0) > Source: > Published: 2026-09-10 00:13:45+00:00 [← Index](/leaderboard) # Leadbay AI lead discovery, qualification, and outreach prep on your Leadbay account. The current version, v0.37.0, was published to the official MCP registry on 2026-09-10. It is distributed as @leadbay/mcp on npm and as a hosted remote over streamable-http, filed under Other by this index, and declares 5 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 Leadbay 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 instructions found”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-10). Contracts can change after screening, with no version bump. The gate pins Leadbay’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 Leadbay](https://mcpindex.ai/server/io-github-leadbay-leadbay-mcp) - screening verdict, registry provenance, and contract drift monitoring. Independent trust record for Leadbay - 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-leadbay-leadbay-mcp)](https://mcpindex.ai/server/io-github-leadbay-leadbay-mcp) mcpindex verdict ``` `LEADBAY_TOKEN` Bearer token, set by the installer. Run `npx -y -p @leadbay/mcp@latest installer` and sign in with your browser. `LEADBAY_REGION` us or fr - Leadbay backend that owns your account. `LEADBAY_MCP_WRITE` Set to 0 to hide composite write tools (default: 1, ON). `LEADBAY_MCP_ADVANCED` Set to 1 to expose granular API tools. `LEADBAY_TELEMETRY_ENABLED` Product-usage telemetry (PostHog/Sentry). Set to false to opt out. On a local/stdio install this env var is the ONLY way to stop telemetry — the account-level toggle (leadbay_set_telemetry) governs the hosted connector, not a local process (default: true). [methodology](/methodology) [AgentRoamai.agentroam/agentroam](/server/ai-agentroam-agentroam) Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order. [Authoryzeai.authoryze/authoryze](/server/ai-authoryze-authoryze) Give your AI agent a spending limit: approval controls and single-use virtual cards. [io.github.leadpipe-com/leadpipeio.github.leadpipe-com/leadpipe](/server/io-github-leadpipe-com-leadpipe) Official MCP server for Leadpipe intent and data APIs.