Skip to main content
Glama

Dataconto: who buys company records and code

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 9 tools

Disambiguation3/5

Most tools have clearly scoped jobs (code_value, deletion_clock, get_tool_terms, rights_check), but four tools surface buyer payout information at different granularities — list_buyers, get_buyer, get_market_facts and estimate — so an agent must read carefully to pick the right one. fit_check and rights_check also both produce verdicts with `missing` questions, which invites misselection despite the long descriptions.

Naming Consistency3/5

All names are snake_case and readable, but the conventions are mixed: get_buyer/get_market_facts/get_tool_terms/list_buyers use verb_noun, while code_value, deletion_clock, fit_check and rights_check are noun compounds and `estimate` is a bare verb. There is no single predictable pattern to infer a new tool's name from.

Tool Count4/5

Nine tools is a good fit for the scope and each maps to a real step in the workflow (discover buyers, price records, check fit, check rights, check vendor terms). The only slack is the partly overlapping buyer-fact tools, which could arguably be consolidated.

Completeness4/5

The surface covers the full evaluation path: buyer discovery and detail, market facts, estimator ranges, fit and rights verdicts, vendor term and post-cancellation export answers, plus code pricing. Gaps are minor but real — nothing for submitting or tracking an offer, recording owner answers/decisions, or producing an export/submission plan.

Available Tools

9 tools
code_valuePrice private code at a buyer's published per-token ratesA
Read-onlyIdempotent
Inspect

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.

Inputs: files, code_bytes, text_bytes, source_tokens, +1 more.

deletion_clockLast day to export from each business toolA
Read-onlyIdempotent
Inspect

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.

Inputs: ends, plans, tools.

estimateRun three buyers' published payout estimatorsA
Read-onlyIdempotent
Inspect

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.

Inputs: staff (required), years (required), status, country, +3 more.

fit_checkCheck which buyers fit a company's records or codeA
Read-onlyIdempotent
Inspect

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, and questions gives every question for this owner with its choices and the answer so far (the card view asks the open ones itself). Where the card shows, it is the answer: write one short sentence before it and nothing after. Don't repeat the companies, figures or questions in text, and don't promise a sale or a price: each company decides after reviewing.

Inputs: side (required), answers.

get_buyerGet one buyer programA
Read-onlyIdempotent
Inspect

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.

Inputs: id (required).

get_market_factsDated market facts on data and code buyersA
Read-onlyIdempotent
Inspect

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.

Inputs: field, limit, since, current, +2 more.

get_tool_termsWhat a business tool's terms say about customer dataA
Read-onlyIdempotent
Inspect

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. Without a tool id it returns a short index (each tool's headline answers and its Dataconto page); name a tool for the quoted facts. Not legal advice.

Inputs: plan, tool, facts, field, +3 more.

list_buyersList who buys company records and codeA
Read-onlyIdempotent
Inspect

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.

Inputs: kind, side, limit, listed, +3 more.

rights_checkCheck whether a company's records are ready to licenseA
Read-onlyIdempotent
Inspect

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.

Inputs: status (required), ip, tools, signer, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources