# MyDataHub (remote · mydatahub.emailmovers.com)

UK B2B contact counts, quotes and lists, by Emailmovers

- Trust score: 72/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mydatahub.emailmovers.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-emailmovers-mydatahub/mydatahub.md), [page](https://verifymcp.io/servers/com-emailmovers-mydatahub/mydatahub)

## Channel facts

- Endpoint: `https://mydatahub.emailmovers.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5176 tokens (~199/item across 26 items; 22 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 5/100
  - Stability check failed: schema churn in the 12 days we've observed: 12 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the MyDataHub MCP server?

MyDataHub is a hosted endpoint at https://mydatahub.emailmovers.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-emailmovers-mydatahub 'https://mydatahub.emailmovers.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-emailmovers-mydatahub": {
      "url": "https://mydatahub.emailmovers.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-emailmovers-mydatahub": {
      "type": "http",
      "url": "https://mydatahub.emailmovers.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-emailmovers-mydatahub]
url = "https://mydatahub.emailmovers.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-emailmovers-mydatahub": {
      "type": "remote",
      "url": "https://mydatahub.emailmovers.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-emailmovers-mydatahub --url 'https://mydatahub.emailmovers.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-emailmovers-mydatahub:
    url: "https://mydatahub.emailmovers.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-emailmovers-mydatahub": {
      "Transport": "http",
      "Url": "https://mydatahub.emailmovers.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-emailmovers-mydatahub -t streamable-http -u 'https://mydatahub.emailmovers.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-emailmovers-mydatahub": {
      "type": "http",
      "url": "https://mydatahub.emailmovers.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 1 to 5.

### 2026-11-13 (score 71, −1)

- [security regression] Stability: 0.10 → fail
- [security regression] Tool “available_selection_categories” was removed
- [security regression] Tool “available_selection_values” was removed
- [security regression] Tool “clear_search” was removed
- [security regression] Tool “create_data_extract” was removed
- [security regression] Tool “create_search” was removed
- [security regression] Tool “get_count” was removed
- [security regression] Tool “get_credits” was removed
- [security regression] Tool “get_pack_details” was removed
- [security regression] Tool “get_packs” was removed
- [security regression] Tool “get_saved_selections” was removed
- [security regression] Tool “save_selections” was removed
- [security regression] Tool “search_discrete_values” was removed
- [functional regression] Schema quality: 176 → 199

### 2026-11-11 (score 72, +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.

### 2026-11-10 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 71)

First indexed and scored.

## MCP tools (22)

### `get_plans` (~157 tokens)

Plans and prices

Returns the plans of MyDataHub by Emailmovers, the UK B2B count engine: credit packs, credit rules, licence terms, the bounce warranty and the free trial, in GBP excluding VAT. Use it when the user asks what a list costs or which plan fits; it is free and needs no account. One credit buys one complete UK record at the same price in the app, the API and here. Call get_account for the caller's own balance, or count_audience to size a list. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Output parameters:

- `action_path` (array): How to buy: quote_order for a machine quote, create_order with a confirmation, and the top-up page when the balance is short.
- `credit_definition` (string)
- `credit_packs` (array)
- `credit_rules` (array)
- `currency` (string)
- `guarantee` (object)
- `licence` (array)
- `meters` (array): What agents and code are metered on, in credits, the same on every surface.
- `plans` (array)
- `price_scale`
- `promises` (array)
- `trial` (object)
- `valid_from` (string)
- `vat_treatment` (string)
- `version` (string)

### `get_account` (~131 tokens)

Account and balance

Returns the organisation's credit balance by source, plan, per-action prices and rate limit, and for an agent key its monthly budget and per-order cap. Use it before quoting a large order, or when a spend is refused, to see what remains. Free; it needs a token with account:read. Top-ups happen on mydatahub.emailmovers.com, never inside a tool. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Output parameters:

- `account_manager`: The named person behind Talk to us.
- `agreements` (object): The Terms of Sale (accepted at sign-up; accepted: null for an organisation Emailmovers set up), the Data Licence and Sharing Agreement (the licence: accepted with every order, or with an agent key th…
- `balance` (object): Credits by source.
- `demo`: A demo organisation: everything runs in test mode, nothing is charged, order records are invented, and it stops working at expires_at. null for a real account.
- `gbp_per_credit` (number): Your plan's price per credit, excluding VAT.
- `key`: The calling key and, for an agent key, its budget; null for a person.
- `mode` (string): live keys (mdh_live_) spend real credits; test keys (mdh_test_) return synthetic data and never charge.
- `organisation` (object)
- `plan` (object)
- `prices` (array): What each action costs in credits.
- `rate_limit`
- `user`: The signed-in person; null when the caller is an API key.

### `list_filters` (~171 tokens)

Filter catalogue

Lists every filterable field of the audience definition (mydatahub.audience/1) with its group, type, operators, value count and default, plus the datasets. Use it first to learn field names such as company.employee_band or site.town before building an audience by hand. Free and needs no account; the same catalogue is the mydatahub://catalogue resource. Call search_filter_values to find the codes for one field. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `dataset` (string): The dataset an audience draws from. uk_contacts is live; ie_contacts and global_contacts are listed but not yet served.

Output parameters:

- `dataset` (string): The dataset an audience draws from. uk_contacts is live; ie_contacts and global_contacts are listed but not yet served.
- `dataset_version` (string): The immutable weekly build a count is bound to, such as 2026-W39. The last 52 stay queryable.
- `datasets` (array)
- `fields` (array)
- `operators` (array)

### `search_filter_values` (~228 tokens)

Search filter values

Searches the values of one field by text, such as towns matching leeds, and returns each code with its contact and company counts plus did_you_mean for near misses. Use the returned code in a filter rather than guessing one. Free and needs no account; results are paged with next_cursor. Call count_audience once the filters are chosen. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `cursor` (string): An opaque cursor from next_cursor. Pass it back unchanged.
- `dataset` (string): The dataset an audience draws from. uk_contacts is live; ie_contacts and global_contacts are listed but not yet served.
- `dimension` (string, required): A field name from list_filters, such as site.town or company.sic_2007.
- `limit` (integer): Items per page, 1 to 100. Default 25.
- `q` (string): Text to search for.

Output parameters:

- `data` (array)
- `dataset_version` (string): The immutable weekly build a count is bound to, such as 2026-W39. The last 52 stay queryable.
- `did_you_mean` (array)
- `disclosure`
- `field` (string)
- `has_more` (boolean)
- `next_cursor`

### `expand_job_titles` (~264 tokens)

Expand job titles

Expands title keywords into every matching title (plurals, department synonyms, ampersands, abbreviations such as CEO), each with a count, or shows what a bundle such as sdm resolves to. Use it before counting so the user can see and edit which titles a keyword covers; nothing is expanded silently. Free and needs no account. Put the returned filter into the audience, then call count_audience. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `bundle` (string): A title bundle to show: sdm, manager_and_above or owner_managed.
- `dataset` (string): The dataset an audience draws from. uk_contacts is live; ie_contacts and global_contacts are listed but not yet served.
- `expand` (array): Expansion sets to apply, each once. Left out, the four default sets apply.
- `mode` (string): contains (the default) matches titles containing a term, starts_with matches titles beginning with it, exact takes verbatim titles with no expansion.
- `terms` (array): Title keywords to expand, such as marketing manager.

Output parameters:

- `bundle`
- `dataset_version` (string): The immutable weekly build a count is bound to, such as 2026-W39. The last 52 stay queryable.
- `disclosure`
- `expand` (array)
- `filter`: A ready matches filter for the terms, or null for a bundle.
- `mode` (string): contains (the default) matches titles containing a term, starts_with matches titles beginning with it, exact takes verbatim titles with no expansion.
- `terms` (array)
- `total_contacts`

### `resolve_location` (~205 tokens)

Resolve a location

Turns free text such as 20 miles of Leeds, Yorkshire or LS1 into region, county, town, postcode or radius filters, each with a count and a ready filter. Ambiguous places come back as candidates with a question, so ask the user which they meant rather than choosing. Free and needs no account, though a radius under 5 miles needs an account. Add the chosen filter to the audience, then call count_audience. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `dataset` (string): The dataset an audience draws from. uk_contacts is live; ie_contacts and global_contacts are listed but not yet served.
- `radius_miles` (number)
- `text` (string, required): Free text such as "20 miles of Leeds", "Yorkshire" or "SW1".

Output parameters:

- `ambiguous` (boolean): True when more than one candidate fits; ask the person which they meant.
- `candidates` (array)
- `disclosure`
- `question` (string|null)
- `text` (string)

### `compile_audience` (~199 tokens)

Compile a brief

Compiles a plain English brief, such as 300 finance directors at law firms in Manchester, into an audience definition with a one-sentence readback, editable chips and any questions to answer first. Use it first for a request in words, read the readback to the user and settle the questions before counting. Words that match no filter come back in unrecognised, never guessed. Free and needs no account; pass the audience to count_audience next. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `brief` (string, required): A plain English brief, such as "300 finance directors at law firms in Manchester".
- `dataset` (string): The dataset an audience draws from. uk_contacts is live; ie_contacts and global_contacts are listed but not yet served.

Output parameters:

- `audience`
- `chips` (array)
- `quantity`: A quantity named in the brief, such as 300, for quote_order limit.
- `questions` (array)
- `readback` (string): The audience in one sentence, to confirm with the person.
- `unrecognised` (array): Words of the brief that matched no filter, shown rather than guessed.

### `count_audience` (~271 tokens)

Count an audience

Counts UK contacts and companies matching an audience, inline or a saved aud_ id, and returns Total, New to you and Emailable, up to three breakdowns, quality, the compliance summary, a price estimate and a count id. Use it whenever a filter changes, and before preview_records or quote_order, which both take the count id. Free and needs no account; anonymous and trial callers see counts under 100 and breakdown cells rounded to the nearest 5 (disclosure says which), and exact small counts need a paid plan. It returns no contact details, and over MCP a cross-tab holds at most 200 cells (truncated true; GET /v1/counts/{id} has the rest). Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `audience` (string|object, required)
- `breakdown_by` (array): Up to three fields to break the count down by, each once, such as industry by seniority by region. Returns the top 50 cells per field plus other.
- `level` (string): contact (the default) or company. Contacts and companies come back together either way.

Output parameters:

- `all_records` (integer): All records: every matching contact with the audience's top-level premium filters taken out (a premium filter inside any or not stays), so the premium figure always has the full figure beside it. The…
- `as_of` (string): The date the dataset version was built, for as-of statements.
- `breakdowns` (array)
- `companies` (integer)
- `compliance_summary`
- `contacts` (integer): Total: every matching contact.
- `created_at` (string)
- `credits_per_record` (number): Credits, to one decimal place: whole at 1 credit a record, fractional only where a rule is (0.1 company-only, 1.8 outright, both proposed).
- `crosstab`
- `current`: On a replay: the same audience on the current dataset version.
- `dataset` (string): The dataset an audience draws from. uk_contacts is live; ie_contacts and global_contacts are listed but not yet served.
- `dataset_version` (string): The immutable weekly build a count is bound to, such as 2026-W39. The last 52 stay queryable.
- `defaults` (array): Every default with the number behind its toggle: dissolved and insolvent, generic emails, individual subscribers, TPS and CTPS registered.
- `disclosure`
- `effective_audience`: The definition after defaults and bundles, as hashed into the id.
- `emailable` (integer): A named email scoring 70 or more at a corporate subscriber.
- `engine_rules_version` (string): The engine rules (title expansion, defaults, geography sets) the count ran under; part of what the count id hashes, such as 2026.09.1.
- `estimate`
- `expanded_terms` (array): Every title a matches filter covered, with a count per term.
- `expires_at` (string): The id replays until then (12 months).
- `id` (string): Format: a count id: cnt_ followed by 20 base32 characters (A to Z and 2 to 7), such as cnt_7K2PQ4MAXN3R6TBY5WDZ.
- `level` (string): contact (the default) or company. Contacts and companies come back together either way.
- `new_to_you`: Excludes your earlier orders and CRM overlap; null when signed out.
- `plan`
- `premium`: Premium: the contacts of all_records that are premium records (contact.premium true). At launch, a premium record is in the premium export of a stated date. Null when the dataset version carries no p…
- `premium_note` (string): What premium means on this dataset version, or why premium is null: no premium data on the version, or withheld because the premium records are at a single company.
- `quality`
- `removed_since` (integer): On a replay: records since removed by objections and erasure.
- `views`
- `warnings` (array)

### `preview_records` (~219 tokens)

Preview sample records

Returns up to 25 masked sample rows (10 by default) for an audience or a count id, each with verification badges, why it matches and a provenance card. Use it after count_audience to show the user what the records look like before quoting. Free: emails and phones are masked on the server, a repeat returns the same rows, and no rows come back when the count is under 25. Call quote_order next to price the records. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `audience` (string|object)
- `count_id` (string): A count id instead of an audience.
- `limit` (integer): Rows to return, 1 to 25. Default 10.
- `shuffle` (boolean): Draw a new seed. Counts against your rate budget and is logged. Default false, so a repeat returns the same rows.

Output parameters:

- `count` (integer): The count the rows were drawn from, rounded as disclosure says.
- `count_id` (string): Format: a count id: cnt_ followed by 20 base32 characters (A to Z and 2 to 7), such as cnt_7K2PQ4MAXN3R6TBY5WDZ.
- `created_at` (string)
- `dataset_version` (string): The immutable weekly build a count is bound to, such as 2026-W39. The last 52 stay queryable.
- `disclosure`
- `id` (string): Format: a preview id: prv_ followed by a 26 character ULID in upper case Crockford base32, such as prv_01JB4H3M7Q2V7XN3M9R6T1Y5W8.
- `masked` (boolean)
- `rows` (array)
- `seed` (string): The seed the rows came from; the same audience gives the same seed.
- `watermark` (string|null): The account id watermarked into sample CSVs; null when signed out.
- `withheld`: Rows held back: all of them when the count is under 25, or rows whose title fewer than 10 people hold.

### `save_audience` (~174 tokens)

Save an audience

Saves an audience definition under a name, shared across the organisation, or updates a saved one when audience_id is given. Use it when the user wants to keep, share or recount a list later; saving is free and needs audiences:write. Repeating the same call returns the same saved audience. Call list_audiences to find it again, or count_audience with its aud_ id. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `audience` (object)
- `audience_id` (string): A saved audience to update. Leave it out to save a new one.
- `brief`
- `name` (string)

Output parameters:

- `audience`
- `brief` (string|null): The brief it was compiled from, if any.
- `created_at` (string)
- `created_by` (string): Format: a user id: usr_ followed by a 26 character ULID in upper case Crockford base32, such as usr_01JA0Q3V7XN3M9R6T1Y5W8ZAK8.
- `current_count`
- `id` (string): Format: an audience id: aud_ followed by a 26 character ULID in upper case Crockford base32, such as aud_01JB4H2K9V6XN3M9R6T1Y5W8ZA.
- `last_refreshed_at`
- `name` (string)
- `updated_at` (string)
- `url` (string): The audience in the app, mydatahub.emailmovers.com/audiences/{id}.

### `list_audiences` (~161 tokens)

List saved audiences

Lists the organisation's saved audiences with their current counts and last refresh, newest first, optionally filtered by name. Use it to find an aud_ id to count, quote or share. Free; it needs audiences:read. Pass an aud_ id to count_audience for a fresh count. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `cursor` (string): An opaque cursor from next_cursor. Pass it back unchanged.
- `limit` (integer): Items per page, 1 to 100. Default 25.
- `q` (string): Filter by name.

Output parameters:

- `data` (array)
- `has_more` (boolean): Whether another page follows.
- `next_cursor`: Pass as cursor to fetch the next page; null on the last page.

### `list_field_sets` (~151 tokens)

List field sets

Lists the field sets an order can deliver, such as standard or standard_telephone, with their exact columns. Every field set costs 1 credit a record, with no telephone, download or API surcharge. Use it to pick the field_set for quote_order; it is free and needs no account. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `cursor` (string): An opaque cursor from next_cursor. Pass it back unchanged.
- `limit` (integer): Items per page, 1 to 100. Default 25.

Output parameters:

- `data` (array)
- `has_more` (boolean): Whether another page follows.
- `next_cursor`: Pass as cursor to fetch the next page; null on the last page.

### `quote_order` (~330 tokens)

Quote an order

Creates a machine quote for a count: the records you would receive after removing ones already held and suppressed, the credits and GBP price, the licence, the warranty and any blockers. The quote_id lasts 24 hours and is bound to the dataset version; it is not a human sales quote, which is a 14 day PDF made in the app. Free and needs no account, and nothing is charged. Show the credits and price to the user, then call create_order with the quote_id. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `connection_id` (string): The CRM connection to check, only with dedupe_against crm or previous_orders_and_crm.
- `count_id` (string, required): A count id from POST /v1/counts or count_audience. Either case is accepted; responses use upper case.
- `dedupe_against` (string): Remove records you already hold: from earlier orders, from a connected CRM, or both. Default previous_orders when signed in. crm and previous_orders_and_crm need connection_id.
- `field_set` (string, required): A field set id from GET /v1/field-sets, such as standard.
- `licence` (string): multi_use_12m (12 month multi-use, every plan) or outright (1.8 credits a record, proposed).
- `limit` (integer): Records to buy; left out, the whole count.

Output parameters:

- `balance_after` (number|null): credits_available less credits_required; negative means a top-up is needed; null when signed out.
- `blockers` (array)
- `count_id` (string): The count the quote was priced from.
- `created_at` (string)
- `credits_available`: Your balance; null when signed out.
- `credits_per_record` (number): 1 for a complete UK record; 1.8 outright (proposed).
- `credits_required` (number): records times credits_per_record (creditsFor).
- `dataset` (string): The dataset an audience draws from. uk_contacts is live; ie_contacts and global_contacts are listed but not yet served.
- `dataset_version` (string): The immutable weekly build a count is bound to, such as 2026-W39. The last 52 stay queryable.
- `expires_at` (string): 24 hours after creation.
- `field_set` (string)
- `gbp_ex_vat` (number): What credits_required cost bought the cheapest way, at the per-contact scale or with credit packs, excluding VAT. The same for every caller; purchase says what this caller needs to buy.
- `id` (string): Format: a quote id: qte_ followed by a 26 character ULID in upper case Crockford base32, such as qte_01JB4M2R6T1Y5W8ZAK8Q2V7XN3.
- `kind` (string)
- `licence`
- `organisation_id`: The organisation the quote belongs to; create_order settles it only there. null for a quote made without an account, which the first organisation to confirm it takes.
- `purchase`
- `records` (integer): Records after overlap and suppression; what you would receive.
- `removed` (object): Records left out and never charged.
- `signature`
- `warranty`

### `create_order` (~366 tokens)

Create an order (spends credits)

Spends 1 credit per complete UK record against a live machine quote from quote_order, and queues the order. It needs the quote_id and an idempotency_key to reuse on any retry, so a retry never charges twice; a flag set by a model is never consent. Where the host supports elicitation the user confirms the spend in a form or on mydatahub.emailmovers.com; otherwise an agent key must cover it within its per-order cap and monthly budget. If neither applies nothing is charged: the result is a confirmation-required error with an approval_url to give the user, so keep the quote_id; a short balance returns a top_up_url. Call get_order until the status is ready, then fetch_order_records. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `confirmation_token` (string): The token the approval page on mydatahub.emailmovers.com returns once the signed-in person approves. It is bound to that person (their sub), this spend (the machine quote_id, or the enrichment or pus…
- `delivery` (array): api (fetch records), csv (signed download) and google_sheets. Default api.
- `idempotency_key` (string, required): Any unique string, such as a V4 UUID. Reuse it when retrying the same order so it is never charged twice; a different order needs a new key.
- `name` (string)
- `quote_id` (string, required): A live machine quote from quote_order. Without one nothing is charged.

Output parameters:

- `buyer_kit`
- `confirmed_by`
- `cost_gbp` (number): The charge in GBP excluding VAT at your plan's rate.
- `count_id` (string): The count the machine quote was priced from.
- `created_at` (string)
- `credits_charged` (number): Credits, to one decimal place: whole at 1 credit a record, fractional only where a rule is (0.1 company-only, 1.8 outright, both proposed).
- `credits_remaining` (number): The balance right after this order was charged.
- `dataset_version` (string): The immutable weekly build a count is bound to, such as 2026-W39. The last 52 stay queryable.
- `delivery` (array)
- `download_url` (string): 302 to a single-use signed URL that lives 5 minutes.
- `failure` (string|null)
- `field_set` (string)
- `id` (string): Format: an order id: ord_ followed by a 26 character ULID in upper case Crockford base32, such as ord_01JB4N9S3W2X6Y7Z8A1B2C3D4E.
- `licence`
- `licence_expires_at`: When the licence ends; null for outright ownership.
- `name` (string)
- `quote_id` (string): The machine quote the order settled.
- `ready_at`
- `receipt_url` (string): A path on https://mydatahub.emailmovers.com starting /v1/. Resolve it against the origin (RFC 3986), not by appending it to the server URL.
- `records` (integer)
- `records_url` (string): A path on https://mydatahub.emailmovers.com starting /v1/. Resolve it against the origin (RFC 3986), not by appending it to the server URL.
- `status` (string): queued, building, verifying, ready; failed if processing failed; cancelled (only while queued).
- `test` (boolean): A test mode order (a test key, or anyone in a demo organisation): no credits were charged, the records are invented and no licence is granted. Absent on a live order.
- `validation_report`: Present once the order is ready.
- `verification` (object): The real-time check at delivery, such as 4,102 checked, 4,071 passed.

### `get_order` (~218 tokens)

Get order status

Returns one order's status (queued, building, verifying, ready, failed or cancelled), counts, charges, licence and links to its records, download and receipt, or the recent orders when order_id is left out. Use it after create_order to wait for ready, or rely on the order.ready webhook. Free; it needs orders:read. Call fetch_order_records once the status is ready. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `cursor` (string): An opaque cursor from next_cursor. Pass it back unchanged.
- `limit` (integer): Items per page, 1 to 100. Default 25.
- `order_id` (string): The order to return. Leave it out for the recent orders, newest first.
- `status` (string): queued, building, verifying, ready; failed if processing failed; cancelled (only while queued).

### `fetch_order_records` (~248 tokens)

Fetch order records

Returns a page of an order's delivered records (50 by default, up to 100) with the licence block on every page, as JSON or, on request, as CSV. Pages stay under about 8,000 tokens, with approx_tokens on each; pass next_cursor to continue. Fetching again under licence costs 0 credits; it needs records:read. Call check_suppression before any send, and get_compliance_receipt for proof of screening. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `cursor` (string): An opaque cursor from next_cursor. Pass it back unchanged.
- `fields` (array): Columns to return; default the order's field set.
- `format` (string): json (default) or csv.
- `limit` (integer): Records per page, 1 to 100 over MCP so a result stays under about 8,000 tokens. Default 50.
- `order_id` (string, required): The order whose records to fetch. It must be ready.

### `push_to_crm` (~370 tokens)

Push an order to a CRM

Pushes an order's records to a connected CRM such as HubSpot or Salesforce, keyed on mydatahub_record_id, as record operations only: nothing is ever sent to the contacts. dry_run defaults to true and reports what would be created, updated or skipped; a live push needs the user's confirmation or an agent key allowed push_to_crm on that connection, or it returns confirmation-required. Free; it needs pushes:write and a connection made in the app. Show the dry run to the user before a live push. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `confirmation_token` (string): The token the approval page on mydatahub.emailmovers.com returns once the signed-in person approves. It is bound to that person (their sub), this spend (the machine quote_id, or the enrichment or pus…
- `connection_id` (string, required): Format: a CRM connection id: conn_ followed by a 26 character ULID in upper case Crockford base32, such as conn_01JB3Y2X6Y7Z8A1B2C3D4E5F6G.
- `dry_run` (boolean): Default true: report what would change without writing. A live push needs approval: a person's confirmation, or an agent key allowed push_to_crm on this connection.
- `order_id` (string, required): The order whose records to push.
- `update_existing` (boolean): Update records already in the CRM, matched on mydatahub_record_id. Default true.

Output parameters:

- `completed_at`
- `connection_id` (string): Format: a CRM connection id: conn_ followed by a 26 character ULID in upper case Crockford base32, such as conn_01JB3Y2X6Y7Z8A1B2C3D4E5F6G.
- `created_at` (string)
- `dry_run` (boolean)
- `errors` (array)
- `id` (string): Format: a CRM push id: psh_ followed by a 26 character ULID in upper case Crockford base32, such as psh_01JB4NC3W2X6Y7Z8A1B2C3D4E5.
- `order_id` (string): Format: an order id: ord_ followed by a 26 character ULID in upper case Crockford base32, such as ord_01JB4N9S3W2X6Y7Z8A1B2C3D4E.
- `property_group` (array): The MyDataHub property group written on every record (CrmPropertyGroup).
- `sample`: On a dry run: the property group the first record would carry.
- `status` (string)
- `summary` (object)

### `lookup_company` (~187 tokens)

Look up a company

Looks up one company by Companies House number, domain or name and returns its Companies House fields and compliance facts, and for a signed-in caller the contacts held there by job level. It returns no contact details: use enrich_contact for one known person, or count_audience for everyone at the company. Free and needs no account, though the contacts held are a single company count that needs an account (null when signed out). Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `company_number` (string): Eight characters in upper case, such as 05046417 or SC123456.
- `domain` (string)
- `name` (string)
- `town` (string): Narrows a name search.

Output parameters:

- `company` (object)
- `compliance`
- `contacts_by_level`: The same count by job level, most senior first, with Level not known last; null when signed out.
- `contacts_held`: Contacts we hold at the company: a single-company count, so signed-in callers only (null otherwise) and logged. Trial callers see it rounded.
- `credits_charged` (number)
- `dataset_version` (string): The immutable weekly build a count is bound to, such as 2026-W39. The last 52 stay queryable.
- `disclosure`
- `match_confidence` (number)

### `enrich_contact` (~323 tokens)

Enrich a contact (spends credits)

Returns the full record for one known person, matched by email or by name with a company name, number or domain. It spends 1 credit only on a confident match, and 0 on no match or when you already hold the record under licence, so a repeat never charges twice. Like create_order it needs the user's confirmation (a form, or the confirmation_token from an approval_url) or an agent key whose allowed_tools include enrich_contact within its per-order cap and monthly budget; otherwise nothing is charged and it returns confirmation-required or agent-budget-exceeded. It needs enrich:write; use it for a single named person, and the result gives credits_charged and the balance left. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `company_name` (string)
- `company_number` (string): Eight characters in upper case, such as 05046417 or SC123456.
- `confirmation_token` (string): The token the approval page on mydatahub.emailmovers.com returns once the signed-in person approves. It is bound to that person (their sub), this spend (the machine quote_id, or the enrichment or pus…
- `domain` (string)
- `email` (string)
- `first_name` (string)
- `last_name` (string)

Output parameters:

- `already_licensed` (boolean): True when you already hold the record, so it costs 0.
- `cost_gbp` (number): Pounds sterling excluding VAT, to two decimal places.
- `credits_charged` (number): 1 on a confident match, otherwise 0.
- `credits_remaining` (number): Credits, to one decimal place: whole at 1 credit a record, fractional only where a rule is (0.1 company-only, 1.8 outright, both proposed).
- `licence_expires_at`
- `match_confidence`
- `matched` (boolean)
- `record`

### `check_suppression` (~130 tokens)

Check suppression

Checks the suppression status of up to 1,000 delivered records by record id, as of now, and names the lists that suppress each. Use it before every send, because objections reach records after delivery. Free; it needs suppressions:read. Leave suppressed records out of the send, and call report_objection when someone objects. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `record_ids` (array, required)

Output parameters:

- `checked_at` (string)
- `results` (array)

### `report_objection` (~291 tokens)

Report an objection

Records an objection to direct marketing for one record, by record id or email hash. Scope licensee suppresses it for your organisation at once; scope emailmovers suppresses it database-wide within one working day and tells every licensee holding it. Free; it needs suppressions:write, and repeating the same objection returns the same suppression. Call it whenever a contact objects, in any channel. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `channel` (string, required)
- `email_sha256` (string): SHA-256 of the trimmed, lower cased address, when the record id is not known.
- `note` (string)
- `received_at` (string, required): RFC 3339 date and time, with Z or an offset such as +01:00.
- `record_id` (string): Format: a contact id: contact_ followed by a 26 character ULID in upper case Crockford base32, such as contact_01JA9X2V7XN3M9R6T1Y5W8ZAK8.
- `scope` (string, required): licensee suppresses the record for your organisation at once; emailmovers suppresses it database-wide within one working day.

Output parameters:

- `effective_by` (string)
- `record_id`
- `scope` (string)
- `status` (string): suppressed now, or pending until the database-wide overlay applies.
- `suppressed_at`
- `suppression_id` (string): The list the record now sits on.

### `get_compliance_receipt` (~162 tokens)

Get a compliance receipt

Returns an order's signed compliance receipt: an ES256 JWS with its decoded claims and a PDF link, covering records delivered, suppression removals, subscriber classes, TPS screening, Article 14 status, the licence and the file hash. Use it to prove to the user, a colleague or another agent that a list is licensed and screened; anyone can verify it with POST /v1/compliance/receipts/verify. Free; it needs orders:read. Lawful basis is UK GDPR Article 6(1)(f) legitimate interests; email audiences include corporate subscribers only by default (PECR), so sole traders and ordinary partnerships are left out unless the toggle is changed.

Input parameters:

- `order_id` (string, required): The order the receipt covers.

Output parameters:

- `alg` (string)
- `claims`
- `id` (string): Format: a compliance receipt id: rcpt_ followed by a 26 character ULID in upper case Crockford base32, such as rcpt_01JB4NA2Q5W8ZAK8Q2V7XN3M9R.
- `jwks_url` (string)
- `jws` (string): The receipt as a compact JWS signed with ES256.
- `kid` (string): The signing key id in jwks_url.
- `order_id` (string): Format: an order id: ord_ followed by a 26 character ULID in upper case Crockford base32, such as ord_01JB4N9S3W2X6Y7Z8A1B2C3D4E.
- `pdf_url` (string): The PDF twin at mydatahub.emailmovers.com/receipts/{id}.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-emailmovers-mydatahub/mydatahub#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 72
- 2026-11-11: 72
- 2026-11-10: 71
- 2026-11-09: 71

## Common questions

### What is the MyDataHub MCP server?

MyDataHub is an MCP server listed in the public MCP registry as com.emailmovers/mydatahub. UK B2B contact counts, quotes and lists, by Emailmovers. This page covers its hosted endpoint (https://mydatahub.emailmovers.com/mcp).

### Is the MyDataHub MCP server safe to use?

MyDataHub scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MyDataHub MCP server expose?

MyDataHub exposes 22 tools: get_plans, get_account, list_filters, search_filter_values, expand_job_titles, and 17 more. Their descriptions and schemas cost roughly 4,956 tokens of context every time the server is loaded.

### Does the MyDataHub MCP server require authentication?

No. We connected to MyDataHub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MyDataHub MCP server still maintained?

MyDataHub is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the MyDataHub MCP server?

VerifyMCP ran 13 checks on MyDataHub, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mydatahub.emailmovers.com/mcp
- Website: https://emailmovers.com/mydatahub/
- Changelog RSS feed: https://verifymcp.io/servers/com-emailmovers-mydatahub/mydatahub.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-emailmovers-mydatahub/mydatahub/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-emailmovers-mydatahub/mydatahub.json
- HTML version of this page: https://verifymcp.io/servers/com-emailmovers-mydatahub/mydatahub
