LIVE · adtech-mcp-v2 · 11 READ-ONLY TOOLS

Your agent gets
objects, not a feed.

BrunoSan exposes AdTech developments as stable objects with evidence, source URLs, relationships and timestamps. Missing values remain missing. Unsupported analysis returns an explicit status instead of a confident invention.

Start free — 50 calls Inspect all 11 tools

THE DIFFERENCE

Others aggregate text.
We publish an evidence graph.

NEWS AGGREGATOR

Documents and keywords

Useful for reading. Weak as a deterministic operating layer for agents.

GENERIC LLM ANSWER

Fluent synthesis

Variable citation depth, implicit relationships and a tendency to fill missing values.

BRUNOSAN ADTECH MCP

Addressable objects

Stable IDs, explicit relations, attached evidence, timestamps and honest unavailable states.

RUNTIME STATUS CONTRACT

Available means available.
Unavailable means exactly that.

7Domain tools available

1Snapshot-only tool

1Requires V2 history

1Not modeled in AP4 V2

Plus 1 available system-routing tool. The live contract does not borrow legacy data to make incomplete functions look finished.

CURRENT SYSTEM SNAPSHOT

Proof at three different scopes.

4Verified eventsCurrent V2 snapshot · evt_*

25Independent analysesCurrent V2 snapshot · art_*

4Evidence objectsCurrent V2 snapshot · evd_*

13Active selected sourcesCurrent verified window

225Company registryRegistry scope · comp_*

5,593Article indexSearchable corpus · not a daily event count

Snapshot 2026-07-25. Published object pages: 54. Known-value events: 0 — because no amount and currency were disclosed in this window.

WHAT YOUR AGENT CAN DO NOW

Operate on structure,
not on persuasive prose.

Traverse explicit entity relations

Use entity_intel and entity_graph to connect comp_* objects through canonical events and evidence — not raw co-mentions.

Watch regulatory evidence

Return regulatory_enforcement events with evt_* and evd_* identifiers, confidence and source URLs.

Track disclosed deal facts

The tracker exposes values only with their disclosed currency. The current zero known-value count is a trust signal, not a fabricated financial total.

ACCESS

Start with one domain.
Connect the whole picture.

One transparent price per domain. LENS connects them. Full Intelligence unlocks everything.

TRIALNO CARD

Free Trial

€0

Prove the value with real BrunoSan intelligence.

50 MCP calls
One selected intelligence domain
Real objects, sources and relationships
No credit card required

Get your trial key

ONE DOMAINFOUNDING PRICE

Domain Access

€19.95

/ month

Monthly billing

Go deep in the domain that matters now.

Choose any current intelligence domain
All MCP tools available in that domain
90-day history
Unlimited within fair use
Priority support

Choose your domain

BEST VALUELENS INCLUDED

Full Intelligence

€199

/ month

Save €50.40/month vs. individual access

Your agent sees every relevant domain—not only the one you expected.

All 11 intelligence domains
LENS cross-domain connection layer
All 12 MCP endpoints
Cross-domain entity intelligence
90-day history across all domains
Unlimited within fair use

Get Full Intelligence

ENTERPRISECUSTOM

Enterprise

Custom

Deploy BrunoSan around your data, controls and operating model.

Private LibertyOS instance
Dedicated EU deployment
Custom entity tracking
RBAC, SLA and DPA
White-label or on-premise options

Book an enterprise demo

Founding price protection Founding customers keep their subscription price for at least 24 months.

LENS downgrade rule If fewer than two domains remain active, LENS stays available until the current billing period ends and will not renew.

Bundle logic Individual value: €249.40/month. Full Intelligence saves 20.2% and adds complete coverage.

QUALITY IS THE PRODUCT

Every response carries
its operating contract.

01contract_version

02snapshot_date

03object IDs

04sources & evidence

READ-ONLY SQLITE · DETERMINISTIC ENVELOPES · EXPLICIT WARNINGS · NULL REMAINS NULL

LIVE MCP TOOLSET

Eleven tools.
No hidden capability claims.

Names, status, parameters and descriptions below are generated from the live Runtime V2 contract and server source.

01adtech_daily_briefVerified daily briefavailable+

THE QUESTION

What changed in AdTech, and which objects and sources prove it?

Returns the validated adtech-brief-v2 snapshot or selected canonical sections.

Contract: adtech-mcp-v2 · Category: standard · Objects: evt_*, art_*, comp_*, evd_*

Honest scope: Available in the live Runtime V2 contract.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_daily_brief",
    "arguments": {
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`date`	Optional[str]	null	Date YYYY-MM-DD; default latest valid V2 brief
`sections`	Optional[list[str]]	null	headline \| summary \| events \| analysis \| entities \| evidence \| segments \| deals \| regulatory \| privacy \| walled_gardens \| geographies \| quality \| archive \| clusters (compatibility alias)
`api_key`	str	""	BrunoSan API Key

02adtech_searchObject-aware searchavailable+

THE QUESTION

Find the relevant articles and attach event and evidence relations only when they exist.

Searches the article index and exposes only explicit V2 relations.

Contract: adtech-mcp-v2 · Category: standard · Objects: art_*, eva_*, evt_*, evd_*

Honest scope: Available in the live Runtime V2 contract.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_search",
    "arguments": {
      "query": "privacy sandbox",
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`query`	str	required	Search term
`days`	int	30	Article publication lookback
`limit`	int	20	Maximum results
`segment`	Optional[str]	null
`event_type`	Optional[str]	null
`api_key`	str	""	BrunoSan API Key

03adtech_top_clustersCanonical event rankingavailable+

THE QUESTION

Which verified events matter most in the current snapshot?

Compatibility tool name; returns canonical evt_* event objects, never legacy clusters.

Contract: adtech-mcp-v2 · Category: compatibility · Objects: evt_*, cls_*, evd_*

Honest scope: Compatibility name only. The canonical output object is evt_*, ranked on AP4 importance_score 0–100.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_top_clusters",
    "arguments": {
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`date`	Optional[str]	null	Date YYYY-MM-DD; default latest V2 snapshot
`n`	int	10	Top N canonical event objects
`min_score`	float	0.0	Minimum AP4 importance_score, 0–100
`segment`	Optional[str]	null
`event_type`	Optional[str]	null
`api_key`	str	""	BrunoSan API Key

04adtech_segment_radarSegment snapshotsnapshot only+

THE QUESTION

Which AdTech segments are active in the verified snapshot?

Summarises the current V2 snapshot without pretending a historical trend exists.

Contract: adtech-mcp-v2 · Category: standard · Objects: evt_*, art_*

Honest scope: The requested days parameter is preserved for compatibility; the effective scope is the current V2 snapshot.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_segment_radar",
    "arguments": {
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`segment`	Optional[str]	null
`days`	int	30	Compatibility parameter; current V2 runtime has one snapshot
`api_key`	str	""	BrunoSan API Key

05adtech_entity_intelCompany intelligenceavailable+

THE QUESTION

Show the current events, evidence and article relations for one canonical company.

Combines comp_* registry objects with explicit V2 event and evidence relations.

Contract: adtech-mcp-v2 · Category: intelligence · Objects: comp_*, evt_*, art_*, evd_*

Honest scope: Available in the live Runtime V2 contract.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_entity_intel",
    "arguments": {
      "entity_name": "Criteo",
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`entity_name`	str	required	Canonical company name or comp_* ID
`days`	int	30	Compatibility parameter; current event relations use one V2 snapshot
`api_key`	str	""	BrunoSan API Key

06adtech_entity_graphExplicit relation graphavailable+

THE QUESTION

Which companies are connected by the same verified events?

Builds graph edges from explicit event relations, not from guessed co-mentions.

Contract: adtech-mcp-v2 · Category: intelligence · Objects: comp_*, evt_*, evd_*

Honest scope: Available in the live Runtime V2 contract.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_entity_graph",
    "arguments": {
      "entity_name": "Criteo",
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`entity_name`	str	required	Canonical company name or comp_* ID
`days`	int	30	Compatibility parameter; current graph uses one V2 snapshot
`max_edges`	int	20	Maximum explicit company relations
`api_key`	str	""	BrunoSan API Key

07adtech_power_shiftPower-shift contractrequires V2 history+

THE QUESTION

Can the system prove winners and losers across comparable V2 snapshots?

Returns an honest unavailable state until comparable V2 history exists.

Contract: adtech-mcp-v2 · Category: intelligence · Objects: comp_*

Honest scope: No legacy history fallback. The tool returns not_available until comparable V2 snapshots exist.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_power_shift",
    "arguments": {
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`region`	Optional[str]	null
`days`	int	30	Comparison window requested
`top_n`	int	20	Requested result limit
`api_key`	str	""	BrunoSan API Key

08adtech_deal_trackerDisclosed-value trackeravailable+

THE QUESTION

Which deal-like events disclose a value and currency?

Returns disclosed values only; never invents USD amounts or converts currencies.

Contract: adtech-mcp-v2 · Category: intelligence · Objects: evt_*, evd_*

Honest scope: Current known-value event count: 0. Amount and currency remain null when not disclosed.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_deal_tracker",
    "arguments": {
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`event_type`	Optional[str]	null	acquisition \| funding_round \| ipo \| partnership \| contract_win
`days`	int	30	Compatibility parameter; current data uses one V2 snapshot
`min_value_usd`	float	0.0	Only applies to explicitly disclosed USD values
`limit`	int	50	Maximum events
`api_key`	str	""	BrunoSan API Key

09adtech_regulatory_watchRegulatory evidence streamavailable+

THE QUESTION

Which regulatory-enforcement events are evidenced in the current snapshot?

Returns canonical regulatory events with stable IDs, evidence and source URLs.

Contract: adtech-mcp-v2 · Category: intelligence · Objects: evt_*, evd_*

Honest scope: Available in the live Runtime V2 contract.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_regulatory_watch",
    "arguments": {
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`regulator`	Optional[str]	null
`days`	int	90	Compatibility parameter; current data uses one V2 snapshot
`limit`	int	50	Maximum events
`api_key`	str	""	BrunoSan API Key

10adtech_privacy_signal_flowPrivacy-model statusnot modeled in AP4 V2+

THE QUESTION

Is this privacy signal currently modeled by AP4 V2?

Returns the actual modeling status and never substitutes legacy profiles.

Contract: adtech-mcp-v2 · Category: intelligence · Objects: routing metadata

Honest scope: No legacy privacy-profile fallback. The tool returns the current AP4 V2 modeling status.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adtech_privacy_signal_flow",
    "arguments": {
      "signal": "third_party_cookies",
      "api_key": "YOUR_BRUNOSAN_API_KEY"
    }
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description
`signal`	str	required
`days`	int	90	Requested history window
`api_key`	str	""	BrunoSan API Key

11get_related_intelligenceCross-domain routingavailable+

THE QUESTION

Which BrunoSan intelligence domains can the agent connect next?

Returns current cross-vertical routes in the same V2 envelope.

Contract: adtech-mcp-v2 · Category: system · Objects: routing metadata

Honest scope: Available in the live Runtime V2 contract.

REQUEST OBJECT

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_related_intelligence",
    "arguments": {}
  }
}

LIVE INPUT SCHEMA

Parameter	Type	Default	Runtime description

STREAMABLE HTTP

Connect once.
Inspect the schemas first.

ENDPOINTLIVE

https://adtech.mcp.brunosan.de/mcp

The runtime publishes tools/list schemas before your agent calls any tool.

adtech-mcp-v2

ACCESSKEY-GATED

One verifiable contract

Free Trial starts with 50 calls. Plan CTAs and prices come directly from the central Intelligence pricing manifest.

mailto:access@brunosan.de

FAQ

Technical honesty,
before the sales claim.

Does adtech_top_clusters still return legacy clusters?

No. The name is retained for client compatibility; the canonical output is a ranked list of evt_* event objects.

Why is Power Shift unavailable?

A defensible shift requires comparable V2 snapshots. The runtime will not substitute old cluster history.

Why does Privacy Signal Flow return not_available?

AP4 V2 does not currently model that signal flow. The runtime exposes that state rather than returning legacy profiles.

Is zero deal value the same as a €0 deal?

No. Known-value event count is zero. Total value and currency remain null because nothing was disclosed.

Where do prices come from?

The full pricing block is extracted from the current BrunoSan MCP reference and validated against intelligence_pricing.json.

Can an agent inspect the inputs?

Yes. The runtime publishes an inputSchema for every one of the eleven tools through tools/list.

Your agent getsobjects, not a feed.

Others aggregate text.We publish an evidence graph.

Documents and keywords

Fluent synthesis

Addressable objects

Available means available.Unavailable means exactly that.

Proof at three different scopes.

Operate on structure,not on persuasive prose.

Start with one domain.Connect the whole picture.

Free Trial

Domain Access

Full Intelligence

Enterprise

Every response carriesits operating contract.

Eleven tools.No hidden capability claims.

What changed in AdTech, and which objects and sources prove it?

Find the relevant articles and attach event and evidence relations only when they exist.

Which verified events matter most in the current snapshot?

Which AdTech segments are active in the verified snapshot?

Show the current events, evidence and article relations for one canonical company.

Which companies are connected by the same verified events?

Can the system prove winners and losers across comparable V2 snapshots?

Which deal-like events disclose a value and currency?

Which regulatory-enforcement events are evidenced in the current snapshot?

Is this privacy signal currently modeled by AP4 V2?

Which BrunoSan intelligence domains can the agent connect next?

Connect once.Inspect the schemas first.

https://adtech.mcp.brunosan.de/mcp

One verifiable contract

Technical honesty,before the sales claim.

Your agent gets
objects, not a feed.

Others aggregate text.
We publish an evidence graph.

Available means available.
Unavailable means exactly that.

Operate on structure,
not on persuasive prose.

Start with one domain.
Connect the whole picture.

Every response carries
its operating contract.

Eleven tools.
No hidden capability claims.

Connect once.
Inspect the schemas first.

Technical honesty,
before the sales claim.