Kochava MCP server
2 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Kochava's own remote MCP server lets an agent sign up for Kochava's Free App Analytics with no key, and with a Kochava API key gives it the app analytics, campaigns, trackers and segments of that account. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 2 tools
| Tool | Counted as |
|---|---|
kochava_free_app_analytics_create_acc_and_get_auth_key | Changes things |
kochava_free_app_analytics_get_tos | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://analytics.mcp.kochava.com/mcp.
Recent changes
22 Oct 2026, 09:40 UTC, after a check on 21 Oct 2026, 09:26 UTC
The server's own labels changed on kochava_free_app_analytics_create_acc_and_get_auth_key, kochava_free_app_analytics_get_tos.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Kochava's tools change.
One email when Kochava's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- With no key, one of its two tools creates a Free App Analytics account and returns its API key in the conversation. Kochava's MCP server README
- With a key, its tools can create and update campaigns and segments, and create, update and delete trackers. Kochava's MCP server README
How to limit it
With Kochava's own settings, as its documentation describes them. Stackduke has not tested them.
- Kochava's setup examples put the API key in plain text in client configuration files, so we recommend limiting who can read those files. Kochava's MCP server README
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.