MCP server for Yandex Audience API: segments (CRM, lookalike, pixel), pixels, grants.
The current version, v1.1.1, was published to the official MCP registry on 2026-08-18. It is distributed as mcp-yandex-audience on npm, filed under CRM & Sales by this index, and declares 4 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 put this record in context.
Using Yandex Audience MCP 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
Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.description
passINFOevidence“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
-
- 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 →
That verdict was true at screening time (snapshot 2026-08-18). #
Contracts can change after screening, with no version bump. The gate pins Yandex Audience MCP’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 →
Related: how to trust an MCP server · screen before install · 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 Yandex Audience MCP](https://mcpindex.ai/server/io-github-a1-x-tech-mcp-yandex-audience) - screening verdict, registry provenance, and contract drift monitoring.
<a href="https://mcpindex.ai/server/io-github-a1-x-tech-mcp-yandex-audience">Independent trust record for Yandex Audience MCP</a> - 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.
[](https://mcpindex.ai/server/io-github-a1-x-tech-mcp-yandex-audience)
<a href="https://mcpindex.ai/server/io-github-a1-x-tech-mcp-yandex-audience"><img src="https://mcpindex.ai/api/v1/badge/io-github-a1-x-tech-mcp-yandex-audience" alt="mcpindex verdict" height="20" /></a>
YANDEX_AUDIENCE_TOKEN
Yandex OAuth token, sent as Authorization: OAuth …. Treat it as a secret.
YANDEX_AUDIENCE_API_HOST
API host override (https://api-audience.yandex.com for international accounts).
YANDEX_AUDIENCE_TIMEOUT_MS
Per-request timeout in milliseconds.
YANDEX_AUDIENCE_MAX_RETRIES
Retries on 429 (5xx/network retried for GET only).
Provar MCP Serverio.github.ProvarTesting/provar
Provar MCP: AI-powered Salesforce test automation. Generate, validate, migrate, and run tests.
BoondManager MCP Serverio.github.fauguste/boondmanager-mcp-server
MCP Server for BoondManager API - 180 tools, 11 prompts, 22 resources (ERP/CRM)
io.github.Anirudhx7/suitecrm-mcpio.github.Anirudhx7/suitecrm-mcp
Open-source MCP gateway for SuiteCRM - 24 CRM tools, OAuth2/OIDC auth, multi-entity, observability.