# Dataconto: who buys company records and code (remote · dataconto.com)

Who pays owners for company records, code and datasets, closed companies included. Sourced terms.

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

## Components

- remote · `dataconto.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-dataconto-buyers/dataconto.md), [page](https://verifymcp.io/servers/com-dataconto-buyers/dataconto)

## Channel facts

- Endpoint: `https://dataconto.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-06.

- **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 2427 tokens (~186/item across 13 items; 9 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 73/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Dataconto: who buys company records and code MCP server?

Dataconto: who buys company records and code is a hosted endpoint at https://dataconto.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-dataconto-buyers 'https://dataconto.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-dataconto-buyers": {
      "url": "https://dataconto.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-dataconto-buyers]
url = "https://dataconto.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-dataconto-buyers:
    url: "https://dataconto.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-dataconto-buyers": {
      "type": "http",
      "url": "https://dataconto.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-06 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 73, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-27 (score 73, +4)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 270 → 185
- [functional] The server now declares the “resources” capability
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: 100
- [functional] New resource “code-value”
- [functional] New resource “deletion-clock”
- [functional] New resource “estimate”
- [functional] New resource “fit-check”
- [functional] Server version: 1.0.0 → 1.2.0
- [functional] New tool “code_value”
- [functional] New tool “deletion_clock”
- [functional] New tool “estimate”
- [functional] New tool “fit_check”
- [functional] New tool “rights_check”

### 2026-10-26 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `list_buyers` (~225 tokens)

List who buys company records and code

Programs that pay owners for company records (email, chat, tickets, docs, CRM, databases) or private code, including from closed or winding-down companies. Returns each program's summary, who qualifies, published payout range or rates, countries and its Dataconto page. Programs listed on Dataconto's buyer pages come first.

Input parameters:

- `country` (string): Two-letter ISO 3166 code of the owner's country, e.g. US, GB, DE. Programs with no country limit are included.
- `kind` (string): pays_owner = the program pays the owner itself; marketplace = it places the data with buyers; invite_only = no open intake.
- `limit` (integer): Results to return, default 20.
- `listed` (boolean): true = only programs on Dataconto's buyer pages and fit check.
- `min_payout` (integer): Only programs whose published payout reaches at least this many US dollars.
- `side` (string): company = business records, code = private source code.
- `status` (string): Intake status.

### `get_buyer` (~76 tokens)

Get one buyer program

One program with its current facts: what it takes, who qualifies, payout, fees, exclusivity, payment timing and process, each quoted from the buyer's page with the date read.

Input parameters:

- `id` (string, required): Program id from list_buyers, e.g. "scale-data-partnerships". A company name also works.

### `get_market_facts` (~150 tokens)

Dated market facts on data and code buyers

Dated, sourced facts across programs: payout ranges, per-token rates, payout caps, platform fees, payment timing, eligibility. History is kept when a term changes (current=false rows). Press-only figures are flagged with source_type press.

Input parameters:

- `current` (boolean): true = only terms in force; false = only superseded ones.
- `field` (string): Kind of fact.
- `limit` (integer): Results to return, default 30.
- `program` (string): Program id from list_buyers.
- `since` (string): Observed on or after this date, YYYY-MM-DD.
- `source_type` (string): primary = quoted from the buyer's own page.

### `get_tool_terms` (~349 tokens)

What a business tool's terms say about customer data

For business tools companies keep records in (chat, email, tickets, docs, CRM, call recordings, code hosts): who owns the customer's data, whether the vendor trains AI on it (generative and other models, by plan), whether it keeps aggregated use, what can be exported on which plan and by whom, how much history the plan keeps, and how long data stays after cancellation. Each answer is quoted word for word from the vendor's own terms, AI page, data processing addendum or help article, with the date read. "The terms don't say" means every contract was read and none answers; "Not read yet" means a document is still unread. Answers marked inferred are a reading of the text, not its words. Not legal advice.

Input parameters:

- `answer` (string): Keep tools whose headline answer has this token, e.g. opt_out with field=ai_training.
- `facts` (boolean): false = headline answers only, no quoted facts. Default true.
- `field` (string): One question: ownership, ai_training, aggregate_use, export, retention or after_cancel.
- `limit` (integer): Tools to return, default 20.
- `plan` (string): A plan name as the vendor spells it, e.g. "Free", "Enterprise".
- `record_type` (string): Kind of record: slack-and-teams, email, support-tickets, jira-and-linear, crm, call-recordings, documents-and-sops.
- `tool` (string): Tool id, e.g. "slack", "microsoft-365", "google-workspace", "salesforce", "notion". Omit to list every tool.

### `fit_check` (~136 tokens)

Check which buyers fit a company's records or code

Runs Dataconto's fit check: each listed buyer's published criteria against the owner's answers. Returns, per buyer program, a verdict (strong = every criterion met, possible = none failed but some unknown, none = a criterion failed), each criterion as met, failed or unknown, the reasons for a miss, the buyer's published figure with the date checked and its Dataconto page. Unanswered questions count as unknown; `missing` lists the ones worth asking.

Input parameters:

- `answers` (object): Answer what you know; leave the rest out.
- `side` (string, required): company = business records, code = private source code.

### `estimate` (~272 tokens)

Run three buyers' published payout estimators

What micro1's, Telegraph's and Grepped's own public estimators give for a company's records, from team size, years in business and headquarters. Grepped prices from the kinds of records held, so pass records for its figure. Each range is the buyer's formula, checked against its live page on the date given; none is an offer and Dataconto adds no figure of its own. Pass offer_usd (and offer_from) to place an offer the owner received against each range and the offering buyer's published range. Also returns the other listed buyers these answers don't rule out.

Input parameters:

- `country` (string): Headquarters: us, uk, ca, au, eu4 (Ireland, Netherlands, Germany or France), eu (another EU country), in, sg, other. Default us.
- `offer_from` (string): Who made the offer.
- `offer_usd` (integer): An offer the owner received, in US dollars.
- `records` (array): Kinds of records the company still has. Grepped's estimate needs at least one; without them it returns no figure.
- `staff` (integer, required): People now, or at the peak.
- `status` (string): Default operating. micro1's estimator covers running companies only.
- `years` (integer, required): Years in business.

### `code_value` (~217 tokens)

Price private code at a buyer's published per-token rates

Counts code the way pre.dev's public script does (code files in full, text files up to 10x the code, minified and bundle-named files skipped, 4 bytes per token) and prices it at Pangea's published non-exclusive list rates per million tokens of source and of git history. Give files (path and size in bytes, e.g. from `git ls-tree -r -l HEAD`), or code_bytes and text_bytes, or source_tokens. History is optional. A list price, not an offer.

Input parameters:

- `code_bytes` (integer): Bytes of code files, if you summed them yourself.
- `files` (array): Files at HEAD, paths relative to the repo root. Skip rules (node_modules, vendor, build output) are applied here.
- `history_tokens` (integer): Git history tokens, if counted.
- `source_tokens` (integer): Source tokens, if already counted.
- `text_bytes` (integer): Bytes of text files (Markdown, JSON, YAML, HTML).

### `deletion_clock` (~186 tokens)

Last day to export from each business tool

For a company canceling its tools or closing: the last day to export from each tool once the account ends, by plan, from what each vendor's own terms say happens after cancellation (export window in days, kept with no export, or nothing). Each row quotes the vendor's words with the date read. With no plan given, the plan with the shortest window is used and flagged. Tool ids as in get_tool_terms.

Input parameters:

- `ends` (string): Day the accounts end, YYYY-MM-DD, between 2000 and 2100. Default today (UTC).
- `plans` (object): Plan per tool as the vendor spells it, e.g. {"slack": "Pro"}. Keys are tool ids.
- `tools` (array): Tool ids, e.g. ["slack", "google-workspace", "hubspot"]. Omit for every tool.

### `rights_check` (~300 tokens)

Check whether a company's records are ready to license

Dataconto's rights check: from who can sign, customer contracts, personal data, staff and contractor IP and the tools the company uses, a verdict (ready = nothing in the way, work = steps to finish before signing, not_yet = nobody known who can sign for a closing or closed company) and the steps, each with its level (block, work, note, ok) and the Dataconto page that holds its source. Unanswered questions count as not sure and are listed in `missing`. With tools, also returns what each tool's terms say on ownership, export and AI training, each quote dated. Sums up published sources; not legal advice. Tool ids as in get_tool_terms.

Input parameters:

- `contracts` (string): Whether any customer contracts limit what the company can do with their data.
- `ip` (string): Whether staff and contractor agreements assign their work to the company. gaps = not all of them; na = no documents or code in scope.
- `personal` (string): Personal data in the records. regulated = health or financial records.
- `signer` (string): Who can sign for the company now. officer = a director or officer; officeholder = an administrator, liquidator or trustee.
- `status` (string, required): operating, closing (winding down) or closed.
- `tools` (array): Tool ids the company uses, e.g. ["slack", "notion"].

## Diagnostics

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

## Score history

- 2026-11-06: 77
- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 68
- 2026-10-22: 67

## Common questions

### What is the Dataconto: who buys company records and code MCP server?

Dataconto: who buys company records and code is an MCP server listed in the public MCP registry as com.dataconto/buyers. Who pays owners for company records, code and datasets, closed companies included. Sourced terms. This page covers its hosted endpoint (https://dataconto.com/mcp).

### Is the Dataconto: who buys company records and code MCP server safe to use?

Dataconto: who buys company records and code scores 77 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 Dataconto: who buys company records and code MCP server expose?

Dataconto: who buys company records and code exposes 9 tools: list_buyers, get_buyer, get_market_facts, get_tool_terms, fit_check, and 4 more. Their descriptions and schemas cost roughly 1,911 tokens of context every time the server is loaded.

### Does the Dataconto: who buys company records and code MCP server require authentication?

No. We connected to Dataconto: who buys company records and code without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Dataconto: who buys company records and code MCP server still maintained?

Dataconto: who buys company records and code is still listed as active in the MCP registry. We last reached this channel on 6 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 Dataconto: who buys company records and code MCP server?

VerifyMCP ran 14 checks on Dataconto: who buys company records and code, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://dataconto.com/mcp
- Website: https://dataconto.com/open-data#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-dataconto-buyers/dataconto.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dataconto-buyers/dataconto/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-dataconto-buyers/dataconto.json
- HTML version of this page: https://verifymcp.io/servers/com-dataconto-buyers/dataconto