Quorum MCP
Quorum MCP exposes 16 public tools on this MCP endpoint.
https://mcp.quorum.live/Opens ChatGPT on the web or desktop and asks it to use the WebMCP tools available here.
Connect straight to this server’s public endpoint.
https://mcp.quorum.live/mcpWe add this server to your workspace, then open Studio — saved access, one connection to many servers, with a history of what ran.
Last probed Sep 14, 2026 · mcp.quorum.live
16tools discovered
Quorum Overview
Discover what Quorum knows about a subject, and what you can ask — the best first call. Cheap, fast lookup (no heavy scan). Given a brand name, Quorum advertiser_id, or pixel domain, returns whether Quorum has data on it and a summary — for a brand: devices observed, top DMAs, and top cross-shop brands; for an advertiser: whether resolved household/coverage data is available — plus suggested follow-up questions (grade traffic, cross-shop, enrich a list). Use this to decide w
Quorum Grade Traffic
Grade the real-world quality of a paid traffic source — is it real, resolvable, and clean? Deterministic, privacy-safe, honestly-scoped quality view of impressions bought against an advertiser, DSP campaign, or pixel domain, via Quorum's household identity graph. Args: source_type: "advertiser_id" | "dsp_campaign_id" | "pixel_domain". source: the identifier value. window_days: trailing window (default 30); auto-clamps to the household-enriched sub-window.
Quorum Cross Shop
Who does a brand's audience also visit? — competitive set / conquest targets / affinities. Returns the brands a given brand's real-world visitors most overlap with (device-overlap %), from Quorum's nationwide cross-shop graph. Aggregate only. Use for competitive analysis, conquest targeting, and partnership/affinity questions. Args: brand: brand name (free text; resolved to the canonical library brand). limit: number of cross-shop brands to return (default 15, m
Quorum Visitor Geography
Where a brand's real-world visitors live — home ZIP codes or census blocks. ZIP grain ranks home ZIPs by visitor devices (with population + a per-1k-residents concentration rate). Census-block grain is THROTTLED to the brand's top-N ZIPs and ranked by affinity (visitors per resident), since blocks are highly granular. Resolves the brand against the CORE public library (Brand library + LotLinx autos), so it answers even when the brand is missing from the cross-shop aggregates
Quorum Foot Traffic
How much real-world foot traffic does a brand get? — executed, k-anonymous aggregates. THE verb for "foot traffic for <brand>", "how busy is <brand> in <place>", "visits to <brand> stores". Runs the visit scan and returns aggregate results directly (never SQL): per-store visits when a city/zip is given, total tracked locations + trailing-30d library visits, distinct visitor devices over the window, and a ~6-month monthly device trend — optionally scoped to a DMA and/or a cit
Quorum Nearby
Competitor locations near an arbitrary lat/lon — public lead-gen geo search. Anchor on any point (geocode an address client-side, pass the coordinates). Returns nearby POIs in a category, ranked by distance, from the CORE public library only (Brand library + LotLinx autos); gated agencies are never exposed. Visit/household counts are k-anon-suppressed below the platform floor (the POI itself still returns). Aggregate, no PII. Args: lat, lon: anchor coordinates (
Quorum Brand Graph
Cosmograph-ready brand network: nodes (brands sized by real-world reach, colored by category) + edges (each brand's strongest cross-shop affinities). Visualize the real-world universe around a brand (seed=...), within a category (category=...), or the top brands overall. Aggregate, no PII. Args: seed: center an ego-network on this brand (the brand + the brands its audience also visits). category: restrict to a library category (e.g., "Restaurants - QSR"). lim
Quorum Enrich List
Enrich a list of device IDs (MAIDs) you already have against Quorum's real-world behavior. The bring-your-own-data on-ramp: no pixel needed. Matches your device IDs to households, then surfaces where that cohort actually goes — top brands and categories visited — as AGGREGATE cohorts only. Great for a CRM/visitor/impression-log list you want profiled instantly. Args: device_ids: list of mobile advertising IDs (MAIDs). Pseudonymous; no individuals are returned. w
Quorum Grade List
Grade whether a traffic source is real — bring a sample of the device IDs it delivered. The public "is this traffic real?" check: paste a sample of the MAIDs from a click/impression feed (any source — Google, Meta, CTV, display, streaming audio) and Quorum reports what share deterministically resolves to real, opt-in households, with a verdict vs the ~29% benchmark for genuine consumer traffic. No pixel or account needed. Honest by design: an unresolved ID is unverified, not
Quorum Enrich Audience
Profile your own site's visitors — who they are, where they shop, and paid-traffic quality. Resolves the households that fired your web pixel and returns: visitor resolution rate; paid-vs-organic traffic quality (real-household share by source/medium — answers "is my paid web traffic real?"); the brands/categories those visitors also shop (cross-shop cohorts); and geo. Aggregate + k-anon — seed/lookalike-ready (e.g. for Meta). Works even with no physical stores. Scoped to th
Quorum Measure Attribution
Closed-loop attribution — of the households that saw this advertiser's ads, how many then visited a tracked store, how fast, which brands, and which DSP drove it. The convergence verb: joins ad-exposure households to physical store-visit households at the household grain (≤ attribution window). Returns exposed_households, attributed_visit_households, visit_rate_pct, a modeled total (× disclosed coverage multiplier), a time-to-visit curve, and breakdowns by visited brand and
Quorum Issue Pixel
Generate a ready-to-install Quorum pixel — correct-by-construction (no macro inversions). kind="web": a paste-ready JS snippet (only agid/adid vary) — or use the GTM template. kind="impression": the per-DSP macro mapping for `platform`, assembled from Quorum's canonical master-template map (never hand-typed), with pt= code, plus an inversion guard that surfaces the hierarchy mapping and warns on historically-swapped DSPs (DV360/Adelphic/Xandr/DCM). Args: agency_id:
Quorum Pixel Status
Is the web pixel live? — instant "you're live" check on the near-real-time pixel feed. For confirming a fresh install: reads the raw web-pixel log (minutes of latency, not the daily transform) and reports events in the last 5 min / 1h / 24h / 7d, when it was first seen, and a per-event breakdown — scoped to the caller's agency + this advertiser. Use right after someone installs the pixel to confirm it's firing, or to debug "is my pixel working?". Args: advertiser_id
Quorum Build Audience
Build a deliverable device-ID audience of a brand's real-world visitors → CSV. Returns a ready device-id SELECT plus CSV export: download from Snowsight, or COPY INTO the existing Snowflake→S3 unload stage (the CSV is device MAIDs for platform upload — Meta/TikTok/etc.). Grounded on the curated geofence-only location library. The actual run/export is a paste (the MCP is read-only) — this hands you the exact SQL + commands. Internal (operator) callers only — the response is
Quorum Deliver Audience
Audience-delivery status + propose a refresh (basic connection to the live pipeline). The pipeline runs today: registry → REBUILD_AUDIENCES() → TTD/LiveRamp (Meta via LiveRamp fan-out). With no audience_id, returns pipeline status (active audiences, destinations, recent delivery health). With an audience_id, returns that audience's delivery state. Both include a propose-paste `refresh` command — it does NOT push anything itself (the refresh is a production write). Operator-s
Quorum Usage Stats
Show how the Quorum MCP is being used — calls, billing units, est. cost, latency, and a per-advertiser (source) breakdown — scoped to the caller's agency. Reads OPERATIONS.API_USAGE_LOG (the metered log behind Quorum's usage dashboard + tiered-CPM billing). Answers "how much is the MCP being used / what's it billing / which advertisers drive usage." Token-limited callers see only their authorized advertisers.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Directory coverage for brandsQuorum MCP exposes 16 public tools on this MCP endpoint.
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate Quorum MCP? Verify ownership to take over this directory entry.
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles probed 16 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
No provider sign-in was required during MCPBundles' probe. Your client may still need MCPBundles credentials depending on how you connect.
MCPBundles is an independent platform built on the open Model Context Protocol standard. Not affiliated with Anthropic PBC or Claude.