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

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

0 this week 83 Trust /100

Last scanned (13 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1578 tokens (~225/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
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 21 Nov 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=YE1,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA384 5a80ba758a0a4cfa17256a383f61366eeef
SANs: datascoop.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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. DS published 38690 8 Verified
datascoop.io. No DS 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 · 7 exposed · ~1,017 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 ~66

How to get full access: the current plan of this connection, row caps, prices (free preview, one-off export, Pro annual pass), 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 ~184

Free area totals and breakdowns for supported datasets, including CQC care-home lists, food hygiene ratings, restaurant inspections, aged care, carriers, building permits and licences. Rating datasets include published rating shares; permits use construction and demolition categories. Other lists show record counts and type breakdowns, with dates where published. Omit area to list the areas available. Read the returned field names and coverage before comparing areas; 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. cqc, fsa, fhis-scotland, au-aged-care, us-motor-carriers, us-food-inspections, us-building-permits, us-business-licenses or us-liquor-licenses

No output schema declared.

No examples provided.

get_dataset_intelligence ~152

For England CQC care homes, return exact selection totals, registered providers, recorded beds, missing-value coverage and up to 25 provider summaries. Provider IDs describe registered operators, not ultimate owners. A pending response requires retrying after the supplied delay. Uses the same strict filters as query_dataset; careHome defaults to true.

NameTypeReqDescription
datasetstringyes–
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 unless their schema sets caseSensiti…

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 ~313

Return matching public records, their total count and the attribution to cite. Fields marked personal in our schema are excluded; published business names, addresses or phone numbers may still identify sole traders. Without a Pro key each call returns at most 25 rows; when more match, truncated=true and next_step explains how to buy a full CSV or use Pro. Pro calls return up to 1,000 rows, with offset for retrieving the rest. 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 unless their schema sets caseSensiti…
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 when paging through results; the per-request plan cap still applies
strict_filtersboolean–Reject unknown or invalid nonempty filters instead of ignoring them. Recommended when exact scope matters. Empty values are omitted; true-only boolean filters cannot select false. Default false prese…

No output schema declared.

No examples provided.

search_datasets ~110

Find candidate DataScoop datasets from keywords or a short task description, such as "Find care homes in Surrey" or "restaurant inspections Chicago". Candidates describe declared coverage, not verified matches for the requested location. Call get_dataset_schema, then query_dataset with explicit filters; example filters are illustrative and are not inferred from the request.

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.

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'
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 83 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 7 tools: get_dataset_intelligence, list_datasets, search_datasets, get_dataset_schema, query_dataset, and 2 more. Their descriptions and schemas cost roughly 1,017 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 21 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 DataScoop public data MCP server?

VerifyMCP ran 13 checks on DataScoop public data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.