Update README.md
Browse files
README.md
CHANGED
|
@@ -19,30 +19,37 @@ size_categories:
|
|
| 19 |
|
| 20 |
# MCP Clients Dataset
|
| 21 |
|
| 22 |
-
This data contains
|
|
|
|
|
|
|
| 23 |
|
| 24 |
## Dataset Contents
|
| 25 |
|
| 26 |
-
The dataset contains
|
|
|
|
|
|
|
|
|
|
|
|
|
| 27 |
|
| 28 |
### Raw Split (`raw`)
|
| 29 |
- **name**: MCP client name (e.g., "Cursor", "Anthropic/ClaudeAI", "chat-ui-mcp")
|
| 30 |
- **version**: Client version
|
| 31 |
- **capabilities**: Client capabilities (JSON string)
|
| 32 |
-
- **last_seen**: Most recent timestamp when this client was seen
|
| 33 |
|
| 34 |
### Deduplicated Split (`deduplicated`)
|
| 35 |
- **name**: MCP client name (normalized, mcp-remote suffix stripped)
|
| 36 |
- **versions**: All versions seen for this client (comma-separated)
|
| 37 |
- **capabilities**: Client capabilities (JSON string)
|
| 38 |
-
- **last_seen**: Most recent timestamp when this client was seen
|
| 39 |
|
| 40 |
## Notes about the Data
|
| 41 |
|
| 42 |
-
- Some Clients only send capabilities that have been configured (for example, `fast-agent` only sends the `roots` capability if
|
| 43 |
- There are a number of capabilities out of specification that are helpful to track (e.g. MCP-UI, Skybridge, Apps SDK). We encourage the use of `experimental` to advertise these capabilities for tracking.
|
| 44 |
-
- The data is extracted from the `evalstate/hf-mcp-logs` dataset, filtering for `initialize` method calls and tracking the most recent `last_seen` timestamp for each unique client configuration.
|
| 45 |
- The `deduplicated` split groups clients by (name, capabilities), concatenating all versions together.
|
|
|
|
|
|
|
| 46 |
|
| 47 |
## Usage
|
| 48 |
|
|
|
|
| 19 |
|
| 20 |
# MCP Clients Dataset
|
| 21 |
|
| 22 |
+
This data contains MCP Client identity and capability information logged by the MCP Server at `huggingface.co/mcp`.
|
| 23 |
+
|
| 24 |
+
The data is updated daily (~4AM UTC).
|
| 25 |
|
| 26 |
## Dataset Contents
|
| 27 |
|
| 28 |
+
The dataset contains two configurations, `raw` and `deduplicated`.
|
| 29 |
+
|
| 30 |
+
Raw contains distinct (name,version,capabilities) and a timestamp of the latest that distinct configuration was seen.
|
| 31 |
+
|
| 32 |
+
Deduplicated removes `mcp-remote` suffixes, and concatenates the version numbers to contain distinct (name,capabilities) and a timestamp. Note that further post-processing may be added to handle specific clients such as `postman`.
|
| 33 |
|
| 34 |
### Raw Split (`raw`)
|
| 35 |
- **name**: MCP client name (e.g., "Cursor", "Anthropic/ClaudeAI", "chat-ui-mcp")
|
| 36 |
- **version**: Client version
|
| 37 |
- **capabilities**: Client capabilities (JSON string)
|
| 38 |
+
- **last_seen**: Most recent timestamp when this distinct client configuration was seen
|
| 39 |
|
| 40 |
### Deduplicated Split (`deduplicated`)
|
| 41 |
- **name**: MCP client name (normalized, mcp-remote suffix stripped)
|
| 42 |
- **versions**: All versions seen for this client (comma-separated)
|
| 43 |
- **capabilities**: Client capabilities (JSON string)
|
| 44 |
+
- **last_seen**: Most recent timestamp when this distinct client configuration was seen
|
| 45 |
|
| 46 |
## Notes about the Data
|
| 47 |
|
| 48 |
+
- Some Clients only send capabilities that have been configured (for example, `fast-agent` only sends the `roots` capability if roots are configured)
|
| 49 |
- There are a number of capabilities out of specification that are helpful to track (e.g. MCP-UI, Skybridge, Apps SDK). We encourage the use of `experimental` to advertise these capabilities for tracking.
|
|
|
|
| 50 |
- The `deduplicated` split groups clients by (name, capabilities), concatenating all versions together.
|
| 51 |
+
- The Protocol Version not currently captured - future datasets may include this
|
| 52 |
+
|
| 53 |
|
| 54 |
## Usage
|
| 55 |
|