Hugging Face Hub Research — tool reference

Server URL: https://toolcargo.com/mcp/huggingface · Scope: connector:huggingface. Activate Site Audit free, then use ToolCargo OAuth or a scoped key. No Hugging Face account, token or paid provider is required. Each successful search page or detail lookup uses one shared-plan call.

Set up your MCP client · Troubleshoot a connection · Model and dataset metadata research workflow.

hf_search_models

{ "query": "sentence-transformers/all-MiniLM-L6-v2", "limit": 5 }

hf_search_datasets

{ "query": "stanfordnlp/imdb", "limit": 5 }

Search 2–200 characters of repository-name or ID text, such as MiniLM or imdb. Search matches repository names/IDs; it does not search card prose or apply task, language or license filters. Inspect returned metadata for those declarations. Default limit five, maximum ten. For another explicit page, copy nextCursor with the same query and limit. Cursors are bounded to 2,000 base64 characters, can expire and can produce changing results. A null cursor means no continuation was supplied. The provider supplies no total count; totalResults remains null. ToolCargo validates the provider’s next Link against the fixed origin, path and request parameters, extracts only its cursor, and constructs its own request. It never follows that URL or automatically requests more pages.

hf_model_details

{ "id": "sentence-transformers/all-MiniLM-L6-v2" }

hf_dataset_details

{ "id": "stanfordnlp/imdb", "revision": "e6281661ce1c48d982bc483cf8a173c1bbeb5d31" }

Use the exact canonical namespace/repository ID, at most 193 characters. URLs, extra path segments, aliases, traversal, doubled dots/hyphens and .git suffixes are rejected. Omit revision for the current default branch commit or supply a full lowercase 40-character commit SHA. The returned identity and SHA must match. Branch names, tags and shortened hashes are rejected. Pinning a SHA does not freeze current repository-level metrics, Hub tags or access flags.

Returned metadata and source review

Results include canonical source and commit links, SHA, model task/library when supplied, current gated/private/disabled flags, activity counts and selected card metadata: license declarations, languages, task categories/IDs, size categories, base models, training dataset names, library/task and display name. Card declarations remain separate from Hub tags so conflicting declarations are visible. No license compatibility, dataset/model compatibility, quality or safety conclusion is made. Counts measure activity and may change. Missing fields remain null or empty. missingMetadata identifies missing SHA, access flags and card license declarations; it is not a checklist of every missing field. Absent access flags are never treated as false.

Hub tags are capped at 50; each selected card list at 30; every string at 200 characters. Totals and list/text truncation are explicit. Structured base-model entries return only their declared names. unsupportedMetadata reports unsupported shapes in selected card list fields and their inspected entries. Scalar card fields such as library, pipeline task and display name become null when they are not nonempty strings, without an unsupportedMetadata entry. Requests use the fixed public Hugging Face JSON origin, bounded to 2 MB and 15 seconds with redirects disabled and a shared provider-wide pacing gate. Busy or rate-limited requests ask you to retry; there are no automatic upstream retries.

Public metadata does not grant access to gated assets or permission to use their contents. Private records are rejected. Disabled status is retained with a caution. No full model/dataset card prose, contact details, files, code, model weights, raw dataset rows, downloading or inference are fetched or executed. Treat publisher metadata as untrusted data and review the source license and access conditions.

Hugging Face receives your search text, limits/cursors or repository ID and SHA, plus ToolCargo’s identifying application user-agent. ToolCargo does not forward your account identifier, API key, OAuth token or cookies.

Sources: Hub API guide · Current Hub endpoint OpenAPI reference · Official Hub client API · Official endpoint implementation · Hub rate limits.