Hugging Face
REMOTE · HUGGINGFACE.CO · 2 COMPONENTS · SCANNED AUG 3
Connect to Hugging Face Hub and thousands of Gradio AI Applications
Available components
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 →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- 35% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2570 tokens (~85/item across 30 items; 4 tools + 26 resources), lean.Pass
- 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
- Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · huggingface.co
claude mcp add --transport http co-huggingface-hf-mcp-server https://huggingface.co/mcp
[mcp_servers.co-huggingface-hf-mcp-server] url = "https://huggingface.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-huggingface-hf-mcp-server": {
"type": "remote",
"url": "https://huggingface.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-huggingface-hf-mcp-server --url https://huggingface.co/mcp --transport streamable-http
mcp_servers:
co-huggingface-hf-mcp-server:
url: "https://huggingface.co/mcp" {
"mcpServers": {
"co-huggingface-hf-mcp-server": {
"type": "http",
"url": "https://huggingface.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 0
- Server version: 0.4.4 → 0.4.5 functional
- 1 Aug 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.
- 31 Jul 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
- 30 Jul 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
- 28 Jul 26 +1
- Server version: 0.4.1 → 0.4.2 functional
- 27 Jul 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
- 26 Jul 26 60
First indexed and scored.
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 3 Aug 2026 · Probed https://huggingface.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=huggingface.co | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 14 Mar 2026 | 27 Sept 2026 | RSA 2048 | SHA256-RSA | 1e4ab54b9dd552fa54e770d7ae4dcd2 |
| SANs: huggingface.co, *.huggingface.co | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
DNSSEC secure
Validation of huggingface.co. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| huggingface.co. | present | 34884 | 13 | Verified |
| huggingface.co. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://huggingface.co/mcp | Verified | 200 | |
| http (plaintext) | http://huggingface.co/mcp | HTTPS enforced | 301 | https://huggingface.co/mcp |
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.
hf_fs Hugging Face Hub: Find, use and view models, datasets, spaces, buckets, papers, documentation and collections. Get daily papers reports, and browse trending content. ~745
Use to access the Hugging Face Hub. Navigate resources with ls, cat, find, stat, and search over hf:// URIs. Roots: hf://models, hf://datasets, hf://spaces, hf://buckets, hf://collections, hf://papers, hf://docs. For papers, ls hf://papers/ARXIV_ID to discover related resources; cat hf://papers/ARXIV_ID/paper.md or metadata.json. Documentation paths include the current version from each product's llms.txt manifest. Grammar; each token below is one args array element: ls URI [(-R|-r|-lR|-laR|--recursive)] [(-l|-a|-la|-al|--long)] [--glob GLOB] [(-type|--type|--entry-type) TYPE] [--sort SORT] [(-limit|--limit) N] cat URI [RELATIVE_PATH] [(-offset|--offset) N] [(-max-bytes|--max-bytes) N] stat URI [RELATIVE_PATH] find URI [(-R|-r|--recursive)] [(-name|--name|--glob) GLOB] [(-path|--path) GLOB] [(-type|--type|--entry-type) TYPE] [(-limit|--limit) N] search URI [QUERY...] [(-type|--type|--entry-type) TYPE] [--sort SORT] [--tag TAG] [--kind mcp] [(-limit|--limit) N] TYPE = file|dir|repo|bucket|collection|paper|link. Type aliases: f=file, d=dir, l=link, model|dataset|space=repo. SORT = createdAt|downloads|likes|lastModified|likes30d|trendingScore|mainSize|id|trending|upvotes. URI starts with hf://. QUERY and GLOB are each one string token. Search URI: hf://models|datasets|spaces[/OWNER], hf://collections[/OWNER], any hf://docs scope, or exactly hf://papers; not hf://. Repository and collection searches may omit QUERY to browse or filter; documentation and paper searches require it. Search joins multiple positional QUERY tokens with spaces. Cat and stat join one RELATIVE_PATH token to URI. Long-list flags are accepted for compatibility; hf_fs listings are already structured, so they do not alter output. Find is already recursive, so recursive flags are accepted without altering behavior. Space search: hf://spaces uses semantic search; repeat --tag to require tags, or use --kind mcp for --tag mcp-serve…
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Command arguments; each array item is one grammar token. |
| cmd | string | yes | Command to execute. |
| Name | Type | Req | Description |
|---|---|---|---|
| arxiv_url | string | — | — |
| bytes | number | — | — |
| content | string | — | — |
| content_type | string | — | — |
| daily_papers_date | string | — | — |
| daily_papers_uri | string | — | — |
| entries | array | — | — |
| exists | boolean | — | — |
| lfs | boolean | — | — |
| namespace | string | — | — |
| next_offset | number | — | — |
| op | string | yes | — |
| path | string | — | — |
| published_at | string | — | — |
| section | string | — | — |
| size | number | — | — |
| target_uri | string | — | — |
| truncated | boolean | — | — |
| truncation_message | string | — | — |
| truncation_reason | string | — | — |
| type | string | — | — |
| uri | string | yes | — |
| url | string | — | — |
| warnings | array | — | — |
No examples provided.
hf_whoami Hugging Face User Info ~35
Hugging Face tools are being used anonymously and may be rate limited. Call this tool for instructions on joining and authenticating.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hub_repo_details ~279
Get details for one or more Hugging Face repos (model, dataset, or space). Auto-detects type unless specified. For datasets, use operations: overview, dataset_structure, dataset_preview. Use dataset_structure first to discover configs, splits, sizes, and schema. Use dataset_preview only when config and split are known, unless the dataset has a single config/split.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | — | Dataset Viewer config. Required for dataset_preview when the dataset has multiple config/split options. Discover via dataset_structure. |
| limit | integer | — | Row count for dataset_preview. Defaults to 5 and is clamped to 1-100. |
| offset | integer | — | Row offset for dataset_preview. Defaults to 0. |
| operations | array | — | Details to return. Defaults to ["overview"]. For datasets, prefer ["overview", "dataset_structure"] first; then call ["dataset_preview"] with config and split. |
| repo_ids | array | yes | Repo IDs for (models|dataset/space) - usually in author/name format (e.g. openai/gpt-oss-120b) |
| repo_type | string | — | Specify lookup type; otherwise auto-detects |
| split | string | — | Dataset Viewer split. Required for dataset_preview when the dataset has multiple config/split options. Discover via dataset_structure. |
No output schema declared.
No examples provided.
hub_repo_search Repo Search ~208
Search Hugging Face repositories with a shared query interface. You can target models, datasets, spaces, or aggregate across multiple repo types in one call. Include links to repositories in your response.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | — | Organization or user namespace to filter by (e.g. 'google', 'meta-llama', 'huggingface'). |
| filters | array | — | Optional hub filter tags. Applied to each selected repo type (e.g. ["text-generation"], ["language:en"], ["mcp-server"]). |
| limit | number | — | Maximum number of results to return per selected repo type |
| query | string | — | Search term. Leave blank and specify sort + limit to browse trending or recent repositories. |
| repo_types | array | — | Repository types to search. Defaults to ["model", "dataset"]. space uses keyword search via /api/spaces. |
| sort | string | — | Sort order (descending): trendingScore, downloads, likes, createdAt, lastModified |
No output schema declared.
No examples provided.