INDIVIDUAL MCP TOOL

read_outcomes

The brand's outcome data over a UTC day range — the closed loop from AI visibility to business results: leads recorded through the brand's inbound lead webhook with their UTC day and attribution fields, plus the aggregate counts that tie lead flow back to the tracked visibility.

useheading.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.useheading.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for read_outcomes and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

useheading.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.heading]
url = "https://mcp.useheading.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "heading": {
      "type": "http",
      "url": "https://mcp.useheading.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: heading
Remote MCP URL: https://mcp.useheading.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "heading": {
      "url": "https://mcp.useheading.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "heading": {
      "type": "http",
      "url": "https://mcp.useheading.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "heading",
  "transport": "streamable-http",
  "url": "https://mcp.useheading.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

list_properties — The brands this API key can read: each one's id, name and domain.
read_visibility_summary — The brand's headline visibility numbers over a UTC day range: the overall visibility percentage (the share of tracked prompt-and-platform answers in which AI mentions this brand), the per-platform breakdown of that percentage, the count of prompts and answers measured, and the delta against the equal-length prior period where one is measurable.
read_visibility_series — The day-by-day visibility series for the brand over a UTC day range: one point per UTC day with that day's visibility percentage, optionally restricted to a single AI platform.
read_leaderboard — The share-of-voice leaderboard over a UTC day range: this brand and every tracked competitor ranked by the share of AI answers that mention each of them, with each row's mention share and rank.
read_platform_responses — The verbatim AI platform answers behind the visibility scores: for each collected response in the UTC day range, the platform, the prompt it answered, the UTC day it was fetched, whether this brand was mentioned, and the answer text itself.
read_prompts — The brand's prompt portfolio — the questions being tracked in AI platforms: every prompt with its id, exact text, status (active means tracked daily, suggested means awaiting approval, inactive means paused), quality score, latest visibility percentage, estimated search volume, and tags (branded/non-branded, intents, subjects).
read_prompt_portfolio — The brand's prompt portfolio as the composite Portfolio score measures it: the 0-100 composite score, and each of the six balance factors (tier balance, specificity, buying stage, question types, conversational tone, competitor coverage) with its score, its numeric balance target, the measured actual, which side of the target the active set sits on (over, under, or on-target — the score measures distance from the target, so overshoot is penalised exactly like undershoot), and the guidance sentence for moving toward that target.
read_prompt_changelog — The prompt portfolio change log over a UTC day range, netted to one diff per UTC day: which prompts were added to, removed from, paused in, or reactivated in the tracked set that day, plus the active-prompt count after each day's changes.