Skip to content

Dataset licence facts MCP server

uk.datalicense/dataset-licencedatalicense.ukstreamable-httpv1.0.1Scanned

Licence facts for Hugging Face datasets: declared licence, files, sources, conflicts.

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Dataset licence facts MCP server can do

The Dataset licence facts MCP server is published by datalicense.uk, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (dataset_licence).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • dataset_licenceRetrieve licence facts for one Hugging Face dataset: declared licence, where it was declared, recorded source datasets, detected licence files and a signal.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "retrieve" and "file": it reads files.
    Description, as the server wrote it
    Retrieve licence facts for one Hugging Face dataset: declared licence, where it was declared, recorded source datasets, detected licence files and a signal. Each licence value comes with an evidence URL linking to the Hub file, API record, file list or Hub page that was checked, with a commit-specific link where available. For datasets in the daily build, facts come from the build by default. Other public datasets are checked live on the Hugging Face Hub. Signal values: permissive = permissive or share-alike licence reported; restrictive = use restrictions reported; conflict = possible licence conflict; unclear = insufficient or unrecognised licence information. These signals do not establish permission to use a dataset. Licence facts reported by the dataset and its declared sources. Not legal advice, and not a grant of permission to use the dataset.
  • find_datasetsSearch the 5,000 most downloaded Hugging Face datasets in the daily build, returning matches in descending order of download count.No findings

    Why it is in this group

    • The name "find_datasets" says "find": a word for reading.
    Description, as the server wrote it
    Search the 5,000 most downloaded Hugging Face datasets in the daily build, returning matches in descending order of download count. Optionally filter by signal, task tag and declared licence ID; all supplied filters must match. Returns up to 50 results; licence_evidence links to the Hub file, API record or file list checked for a declared licence. Signal values: permissive = permissive or share-alike licence reported; restrictive = use restrictions reported; conflict = possible licence conflict; unclear = insufficient or unrecognised licence information. These signals do not establish permission to use a dataset. Licence facts reported by the dataset and its declared sources. Not legal advice, and not a grant of permission to use the dataset.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 14, 2026, 12:22 UTC, unchanged since Oct 30, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http dataset-licence https://mcp.datalicense.uk/mcp
claude mcp add --transport http dataset-licence https://mcp.datalicense.uk/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dataset-licence__dataset_licence",
      "mcp__dataset-licence__find_datasets"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dataset-licence. Review it before you use it.

Capability tags behind 1 rule
  • mcp__dataset-licence__dataset_licence private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/uk.datalicense/dataset-licence/verify?hash=0298f38c70c87517ee47b3c143345c181a182fcbfe2f1c2ce6131146d60cbc1b" | jq -e '.changed == false'

Pinned hash 0298f38c70c8, from Nov 10, 2026, 20:20 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/uk.datalicense/dataset-licence/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for uk.datalicense/dataset-licence
[![Anlyon Radar](https://radar.anlyon.com/badge/uk.datalicense/dataset-licence.svg)](https://radar.anlyon.com/servers/uk.datalicense/dataset-licence)

Source: MCP Registry. Synced Nov 10, 2026, 20:20 UTC.

Dataset licence facts MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Dataset licence facts MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Dataset licence facts MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Dataset licence facts MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Dataset licence facts MCP server have?

2 tools: 2 read. dataset_licence and find_datasets.

Does the Dataset licence facts MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Dataset licence facts MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Dataset licence facts MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.