io.github.MCPKit-RU/yandex-direct-mcp
MCPKit — Yandex Direct MCP
Is the MCPKit MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-09.
Review Yandex Direct reports and manage supported campaign settings in ChatGPT.
needs auth probed 2026-11-14 · unchanged since 2026-11-09 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized"}- Endpoint
- https://mcpkit.ru/mcp-yandex-direct/mcp (streamable-http)
- Host
- mcpkit.ru
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcpkit.ru/mcp-yandex-direct/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mcpkit.ru, PKCE S256, grants authorization_code, refresh_token.
Scopes direct:mcp.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://mcpkit.ru/mcp-yandex-direct?utm_source=official_mcp_registry&utm_medium=mcp_registry&utm_campaign=yandex_direct
- Registry
- active, updated 2026-11-08 · registry entry
Compare this server with others.
More servers
Other registry entries on mcpkit.ru.
- MCPKit — Yandex Metrica MCP io.github.MCPKit-RU/yandex-metrika-mcp · needs auth
- MCPKit — Yandex Wordstat MCP io.github.MCPKit-RU/yandex-wordstat-mcp · needs auth
Servers that mention direct.
- 1325.AI ai.1325/mcp · needs auth
- ai.agentrapay/agentra · needs auth
- Agentic Terminal Directory ai.agenticterminal/directory · alive
- Project Desk ai.atlier/project-desk · needs auth
- Boolsai Directory ai.boolsai/directory · no DNS
- Cofound ai.cofoundagent/cofound · needs auth
- DirectCase Legal Search ai.directcase/directcase · needs auth
- Duami ai.duami/intent-exchange · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.