Who it is for
Ad operations, revenue operations and yield teams at broadcasters and publishers.
AI Connectors · Data & Analytics
Watching That
Ad revenue and delivery investigation across a publisher ad stack
Overview
What Watching That does
Watching That reads across the systems where publisher ad revenue actually gets recorded: FreeWheel, Google Ad Manager, SpringServe, SSPs, DSPs, SSAI, Prebid, players, apps and pages. The questions it targets are the ones that normally cost an export and an afternoon of pivot tables. Why revenue moved yesterday and which SSP, deal or geo drove it. Where fill rate is slipping. Which line items or ad servers are erroring or dropping impressions. Whether what was served matches what was paid for. Drill-down runs across device, geo, SSP, deal ID, ad unit and ad server, so root cause work stays in one place.
Tool surface
Six tools for a stack that wide is a compact published surface, and the 401 on tools/list leaves the question of how they divide it unanswered.
Availability
Where Watching That is listed
Watching That is listed in the Claude connectors directory only. Watching That Ltd has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them.
The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one.
Claude listing
In the Claude connectors directory
Watching That publishes 6 tools to Claude. That is a mid-sized surface: 28.1% of the 1,253 Claude-listed connectors expose fewer.
The median Claude-listed connector filed under Data & Analytics publishes 12, so this one sits 6 tools below its bucket's median, 142nd of 198.
It falls in the 4-6 tools band, which holds 16.2% of the Claude directory.
Watching That publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally.
Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there.
- Publisher
- Watching That Ltd
- Verification
- Community-listed (61.5% of the Claude directory)
- Filed under
- Data & Analytics
- Endpoint
-
https://mcp.watchingthat.us/ - Documentation
- Publisher setup docs
- Published tools
- 6 · 4-6 tools band
- Depth rank in Data & Analytics
- 142 of 198
- Snapshot
- August 2026
Watching That is community-listed in the Claude directory, the tier 770 of 1,253 connectors sit in (61.5%). It is the default for a self-published server, and says nothing either way about quality.
In the publisher's words
How Watching That Ltd describes it
Watching That connects Claude to the systems where your ad revenue actually lives: FreeWheel, Google Ad Manager, SpringServe, your SSPs, DSPs, SSAI, Prebid, Video Players, Apps, Webpages etc. Instead of exporting reports and building pivot tables, you investigate revenue and delivery by simply having a conversation. Ask the questions you'd put to a senior analyst: • Why did revenue move yesterday, and which SSP, deal or geo drove it? • Where is fill rate slipping, and what changed? • Which line items or ad servers are erroring or dropping impressions? • Is there a discrepancy between what we served and what we were paid for? Watching That answers with the numbers behind the answer, then lets you drill across dimensions (SSP, deal ID, device, geo, ad unit, ad server) to effortlessly arrive at root-cause in minutes and not hours or days. It's built for how modern ad ops actually works: multiple SSPs, header bidding, FreeWheel, GAM and SpringServe side by side and the insights that live in the gaps between systems. Who it's for: ad operations, revenue operations, yield and monetisation teams at broadcasters, streaming and FAST platforms, pay-TV operators, and digital publishers running programmatic display and video. If you own a revenue number and it's harder to see into than it should be, this is for you, whether you're a global broadcaster or a fast-growing publisher. Watching That already monitors revenue for leading broadcasters and publishers. One major broadcaster used it to recover significant revenue that was quietly leaking; another top-tier news publisher relies on it to protect more than two million ad impressions every day. Connect your stack and ask your first question.
Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it.
Nearby
Other Data & Analytics connectors
GIS Cloud
Cloud GIS maps, spatial analysis and field data collection forms
Claude
Yogi
Consumer feedback analysis across reviews, tickets and social
Claude
Zoom Revenue Accelerator Connector
Call transcripts, deal pipeline and rep scorecards from Zoom
Claude
Evarist
Web analytics questions answered with session-level evidence
Claude
Exaforce
Query security operations data: alerts, investigations and audit logs
Claude
Zylo
SaaS portfolio spend, licenses and contracts from Zylo
Claude
This is an independent catalogue entry compiled by Node8 from Watching That's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Watching That Ltd, and inclusion here is not an endorsement.
Want your company reachable inside ChatGPT and Claude?
Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot.