site
Server Details
EntitySearch HQ: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
The dataset_* family splits cleanly by retrieval mode (exact row, substring search, multi-value compare, ranked top, aggregate stats, schema, provenance), with descriptions that clarify edge cases like case-insensitivity and ordering. The enquiry trio is also distinct (explainer, field schema, submit). Mild overlap remains between dataset_row, dataset_search and dataset_compare, which an agent could occasionally pick wrongly for a lookup.
Seven tools share a clean dataset_noun pattern and two share enquiry_noun, so the set reads predictably. The outlier is submit_enquiry, which uses verb_noun instead of the enquiry_ prefix, breaking the otherwise consistent scheme.
Ten tools is well within the ideal band for a read-only dataset Q&A plus a form-submission server. Each dataset access pattern (schema, provenance, exact, search, compare, stats, top) earns its place and nothing feels padded.
Dataset coverage is strong for question answering (schema discovery, provenance/attribution, row lookup, search, ranking, statistics, comparisons) and the enquiry lifecycle is covered end-to-end including a consent-gated confirm step. Gaps are minor: no multi-column grouping/aggregation or combined-filter queries, and no way to inspect an existing enquiry after submission.
Available Tools
10 toolsdataset_columnsDataset columns and shapeAInspect
The columns, which of them are numeric, the row count and the provenance banner of the EntitySearch HQ dataset. Call this first to learn the schema.
Inputs: no named parameters.
dataset_compareCompare rows side by sideBInspect
The rows of the EntitySearch HQ dataset whose column is any of the given values, in the order given, for "X vs Y" questions.
Inputs: column (required), values (required).
dataset_provenanceWhere this data comes from, and how to cite itAInspect
The source, the date it was computed, the licence and the citation for the EntitySearch HQ dataset. Read this to attribute a figure correctly.
Inputs: no named parameters.
dataset_rowLook a row up by an exact keyBInspect
The rows of the EntitySearch HQ dataset where a column equals a value exactly (case-insensitive).
Inputs: value (required), column (required).
dataset_searchSearch the datasetBInspect
Rows of the EntitySearch HQ dataset whose cells contain the query (case-insensitive), up to 50.
Inputs: query (required), limit.
dataset_statsSummary statistics for a numeric columnBInspect
count, min, max, mean, median and sum of a numeric column of the EntitySearch HQ dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).
Inputs: column (required).
dataset_topRank rows by a numeric columnCInspect
The highest (or lowest) rows of the EntitySearch HQ dataset by a numeric column: "which is the most/least X".
Inputs: column (required), limit, ascending.
enquiry_describeWhat you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)AInspect
Read first. States plainly what submit_enquiry does on EntitySearch HQ: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
Inputs: no named parameters.
enquiry_fieldsThe questions the enquiry asksAInspect
Every field of the EntitySearch HQ enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
Inputs: no named parameters.
submit_enquirySubmit an ENQUIRY to human providers (two steps; not a purchase)AInspect
Submits an enquiry to EntitySearch HQ: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "By submitting you agree EntitySearch HQ emails you the answer to your lookup question and shares nothing else with anyone."
Inputs: answers (required), consent (required), confirmation.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
HostingByStack: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
Rechner HQ: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
FindAgency HQ: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
FlightDelayHQ: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
Related MCP Servers
- AlicenseBqualityBmaintenanceOne MCP server for web search, page extraction, and cited research.147 npm1MIT
- AlicenseBqualityDmaintenanceMCP server for searching research grants across NSF (US), ERC (EU), and KRF/NRF (Korea) via a unified interface. NIH excluded—covered by existing connectors.312 npmMIT
- AlicenseAqualityBmaintenanceMCP server providing access to U.S. government primary-source records, fact-checks, news search, and trackers, with cross-referenced entity data and source links.444 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server for maintaining specific Wikidata items (person, company, publications) with read tools and a two-step write workflow that enforces sourced, human-approved batch edits.-
Glama MCP Gateway
Add one secure layer between your agents and this server.