Dataconto: who buys company records and code

com.datacontoPublished by dataconto.comOfficial publisherv1.0.0Updated Oct 28, 2026

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

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Dataconto server that lets an assistant look up programs paying owners for company records, private code and datasets, with sourced, dated terms.

What you can do
  • List buyer programs that pay for company records, chat, email, tickets, docs, CRM data, databases or private code, including from closed companies
  • Read one program's current facts: what it takes, eligibility, payout, fees, exclusivity and payment timing, quoted with the date read
  • Compare dated, sourced market facts across programs such as payout ranges, per-token rates, caps, platform fees and eligibility, with history of changed terms
  • Check business tool terms: who owns customer data, whether the vendor trains AI on it, aggregation, export options and plan limits
When to use it
Useful when someone is weighing selling or monetizing company data, code or datasets and wants to compare buyer programs, payouts and terms, or when checking what a business tool's terms say about data ownership, AI training and export.
Requirements
Remote streamable HTTP endpoint at dataconto.com; no authentication, environment variables or headers are declared. A client that supports remote MCP endpoints is needed.
Before you install
The server only returns published, sourced information; any actual sale, transfer or deletion of company records or code happens elsewhere and should be reviewed against the quoted buyer terms, including exclusivity, fees and data ownership. Figures marked as press-only may differ from actual offers.

Installation

In SourceWeft

  1. Open Dataconto: who buys company records and code in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.dataconto%2Fbuyers/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dataconto-who-buys-company-records-and-c": {
      "type": "http",
      "url": "https://dataconto.com/mcp"
    }
  }
}

Tools

4

list_buyers

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.

Parameterskindsidelimitlistedstatuscountrymin_payout

get_buyer

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.

Parametersidrequired

get_market_facts

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.

Parametersfieldlimitsincecurrentprogramsource_type

get_tool_terms

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.

Parametersplantoolfactsfieldlimitanswerrecord_type

Version history

1
  1. v1.0.0LatestOct 22, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.