Kochava for Advertisers — Official MCP Server
REMOTE · ANALYTICS.MCP.KOCHAVA.COM · SCANNED AUG 3
No account needed — connect, sign up, and query mobile attribution data from any AI tool
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 743 tokens (~371/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · analytics.mcp.kochava.com
claude mcp add --transport http kochava-kochava-for-advertisers-mcp-server https://analytics.mcp.kochava.com/mcp
[mcp_servers.kochava-kochava-for-advertisers-mcp-server] url = "https://analytics.mcp.kochava.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kochava-kochava-for-advertisers-mcp-server": {
"type": "remote",
"url": "https://analytics.mcp.kochava.com/mcp",
"enabled": true
}
}
} openclaw mcp add kochava-kochava-for-advertisers-mcp-server --url https://analytics.mcp.kochava.com/mcp --transport streamable-http
mcp_servers:
kochava-kochava-for-advertisers-mcp-server:
url: "https://analytics.mcp.kochava.com/mcp" {
"mcpServers": {
"kochava-kochava-for-advertisers-mcp-server": {
"type": "http",
"url": "https://analytics.mcp.kochava.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
- Authorization: fail → unverified ▼ security
- Stability: 0.20 → fail ▼ security
- A breaking change shipped without a version bump: still 1.28.1 ▼ security
- Tool “kochava_free_app_analytics_create_acc_and_get_auth_key” was removed ▼ security
- Tool “kochava_free_app_analytics_get_tos” was removed ▼ security
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: good → unverified ▼ functional
- New tool “kochava_free_app_analytics_create_acc_and_get_auth_key” functional
- New tool “kochava_free_app_analytics_get_tos” functional
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://analytics.mcp.kochava.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.mcp.kochava.com | CN=WR3,O=Google Trust Services,C=US | 23 Jun 2026 | 21 Sept 2026 | RSA 2048 | SHA256-RSA | 586b7c1c6fe11c12101b67b69af81f75 |
| SANs: *.mcp.kochava.com, mcp.kochava.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of analytics.mcp.kochava.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kochava.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://analytics.mcp.kochava.com/mcp | Verified | 200 | |
| http (plaintext) | http://analytics.mcp.kochava.com/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
kochava_free_app_analytics_create_acc_and_get_auth_key ~663
Create a new Kochava FAA (Free App Analytics) account. IMPORTANT: The user MUST explicitly agree to the FAA Terms of Service before account creation. If tos_agreed is False, this tool will return the TOS link and stop — do NOT submit the form. Call kochava_free_app_analytics_get_tos() to retrieve and present the TOS to the user first, then call this tool again with tos_agreed=True once the user confirms agreement. DISPLAY INSTRUCTIONS: When this tool returns a successful response, you MUST display the 'next_steps' field content to the user EXACTLY as written — word-for-word, preserving ALL text, formatting, line breaks, numbering, and bullet points. Do NOT summarize, rephrase, reword, or omit any part of the 'next_steps' content. Every sentence must be shown to the user as-is. FAA Terms of Service: https://s34035.pcdn.co/wp-content/uploads/2023/08/FAA-Web-Sign-Up-TOS-8-15-23.pdf Example (after user reviews and agrees to TOS): kochava_free_app_analytics_create_acc_and_get_auth_key( first_name="Jane", last_name="Smith", email_address="[email protected]", phone_number="5551234567", company="Acme Corp", website="www.acme.com", company_address_line_1="123 Main St", company_city="Sandpoint", company_region="Idaho", company_postal_code="83864", country="United States", tos_agreed=True )
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name for the FAA account |
| company_address_line_1 | string | yes | Company street address line 1 |
| company_address_line_2 | — | — | Company street address line 2 (optional) |
| company_city | string | yes | Company city |
| company_postal_code | string | yes | Company postal/zip code |
| company_region | string | yes | Company state or region |
| country | string | yes | Country name (e.g. United States) |
| email_address | string | yes | Email address for the FAA account |
| first_name | string | yes | First name of the account holder |
| last_name | string | yes | Last name of the account holder |
| phone_number | string | yes | Phone number of the account holder |
| privacy | — | — | Privacy policy URL. Defaults to https://www.kochava.com/company/contact/ |
| subscribe | boolean | — | Whether to subscribe to Kochava marketing communications |
| title | — | — | Job title of the account holder (optional) |
| tos_agreed | boolean | — | Whether the user has agreed to the FAA Terms of Service at https://s34035.pcdn.co/wp-content/uploads/2023/08/FAA-Web-Sign-Up-TOS-8-15-23.pdf. Must be True to proceed with account creation. Use kochav… |
| website | string | yes | Company website URL (e.g. www.example.com) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
kochava_free_app_analytics_get_tos ~80
Retrieve the FAA (Free App Analytics) Terms of Service document link. Use this tool when the user wants to review the Terms of Service before creating an FAA account. Returns a clickable link to the TOS document and instructions for account creation. Example: kochava_free_app_analytics_get_tos()
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.