Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DataScoop public data

REMOTE · DATASCOOP.IO · 2 COMPONENTS · SCANNED SEP 25

Official UK, US and Australia public datasets as filtered CSV, REST API and MCP for AI agents.

+4 this week 74 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1300 tokens (~216/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the DataScoop public data MCP server?

DataScoop public data is a hosted endpoint at https://datascoop.io/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.

remote · datascoop.io

# add to Claude Code
claude mcp add --transport http io-datascoop-datascoop 'https://datascoop.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-datascoop-datascoop": {
      "url": "https://datascoop.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-datascoop-datascoop": {
      "type": "http",
      "url": "https://datascoop.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-datascoop-datascoop]
url = "https://datascoop.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-datascoop-datascoop": {
      "type": "remote",
      "url": "https://datascoop.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-datascoop-datascoop --url 'https://datascoop.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-datascoop-datascoop:
    url: "https://datascoop.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-datascoop-datascoop": {
      "Transport": "http",
      "Url": "https://datascoop.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-datascoop-datascoop -t streamable-http -u 'https://datascoop.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-datascoop-datascoop": {
      "type": "http",
      "url": "https://datascoop.io/mcp"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 21 Sept 26 +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.

  • 19 Sept 26 +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.

  • 18 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Sept 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Probed https://datascoop.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=datascoop.io CN=YE2,O=Let's Encrypt,C=US 26 Aug 2026 24 Nov 2026 ECDSA 256 ECDSA-SHA384 5315e8f4f8dc3f19020311031b4855448a0
SANs: datascoop.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of datascoop.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
datascoop.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://datascoop.io/mcp Verified 200
http (plaintext) http://datascoop.io/mcp HTTPS enforced 301 https://datascoop.io/mcp
MCP tools · 6 exposed · ~770 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_access_info ~65

How to get full access: the current plan of this connection, row caps, prices (free preview, one-off export, Pro subscription), the signup and pricing URLs, how to pass an API key, and the wording to use when telling a user how to get every row.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_area_statistics ~142

Free aggregate statistics for datasets that have a rating (food hygiene ratings by local authority, Scotland FHIS by council, US restaurant inspections and building permits by city area): totals, share rated well or poorly, rank among areas, breakdown by type, and the most recently rated low performers. Omit area to list the areas available. Cite the page URL returned.

NameTypeReqDescription
areastring–Area name or slug, e.g. "Leeds" or "leeds". Omit to list areas.
datasetstringyesDataset id with statistics, e.g. fsa, fhis-scotland, us-food-inspections, us-building-permits

No output schema declared.

No examples provided.

get_dataset_schema ~85

Get a dataset's columns and the exact filters it accepts (key, type, allowed options, example). Use the filter keys, not column names, when calling query_dataset.

NameTypeReqDescription
datasetstringyesDataset id from list_datasets, e.g. fsa, cqc, charity-commission, us-food-inspections, us-building-permits, fhis-scotland

No output schema declared.

No examples provided.

list_datasets ~107

List every dataset DataScoop carries (official public records: UK food hygiene ratings, Scotland FHIS, CQC care providers, the UK charity register, US restaurant inspections, US building permits, and more as added) with country, coverage, row count, licence, refresh date and the page URLs. Call this or search_datasets first.

NameTypeReqDescription
countrystring–Optional ISO 3166-1 alpha-2 country code to filter by, e.g. GB or US

No output schema declared.

No examples provided.

query_dataset ~278

Return the rows of a dataset that match a set of filters, with the total count and the attribution to cite. Organisational data only (businesses, premises, charities, permits), never personal contact data. Without a Pro key each call returns at most 25 rows and sets truncated=true with the total; the result then includes next_step with the exact links and wording to give the user so they can get every row (one-off spreadsheet export, or a free account upgraded to Pro for unlimited API and MCP rows). Page with offset; ask for format "summary" to get counts only.

NameTypeReqDescription
datasetstringyesDataset id, e.g. fsa
filtersobject–Filter object keyed by the filter keys from get_dataset_schema (not column names), e.g. {"localAuthority":"Leeds","rating":"1"}. Text filters are case-insensitive; "contains" filters match substrings…
formatstring–"rows" (default) returns the rows; "summary" returns only the total and links
limitinteger–Rows to return (default 25, max 1000 per call; free plans are capped at 25)
offsetinteger–Rows to skip, for paging through large results (Pro)

No output schema declared.

No examples provided.

search_datasets ~93

Find which DataScoop dataset answers a need, by keywords such as "care homes Yorkshire", "restaurant inspections Chicago", "charities income", "food hygiene Leeds", "building permits". Returns matching datasets with their filters and an example query.

NameTypeReqDescription
countrystring–Optional ISO country code, e.g. GB or US
querystringyesWhat the user is looking for, in plain words

No output schema declared.

No examples provided.

Common questions

What is the DataScoop public data MCP server?

DataScoop public data is an MCP server listed in the public MCP registry as io.datascoop/datascoop. Official UK, US and Australia public datasets as filtered CSV, REST API and MCP for AI agents. This page covers its hosted endpoint (https://datascoop.io/mcp).

Is the DataScoop public data MCP server safe to use?

DataScoop public data scores 74 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 DataScoop public data MCP server expose?

DataScoop public data exposes 6 tools: list_datasets, search_datasets, get_dataset_schema, query_dataset, get_area_statistics, get_access_info. Their descriptions and schemas cost roughly 770 tokens of context every time the server is loaded.

Does the DataScoop public data MCP server require authentication?

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

Is the DataScoop public data MCP server still maintained?

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