MCP server counts from the official registry, new servers per day, and MCP/A2A spec changes. As is.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
New MCP servers per UTC day for the last N days (1 to 365, default 30), ready to chart. Call it to show or describe the trend, for example 'daily new MCP servers over the last two weeks' -> days=14.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
New MCP servers per UTC day for the last N days (1 to 365, default 30), ready to chart. Call it to show or describe the trend, for example 'daily new MCP servers over the last two weeks' -> days=14.
| Argument | Type | Description |
|---|---|---|
| days | integer |
{
"type": "object",
"title": "daily_new_countsArguments",
"properties": {
"days": {
"type": "integer",
"title": "Days",
"default": 30
}
}
}How MCP servers are published: under a code host namespace (io.github, io.gitlab, io.bitbucket) or under the publisher's own domain. Call it for questions like 'What share of MCP servers use their own domain?'. No arguments.
No arguments.
{
"type": "object",
"title": "namespace_typesArguments",
"properties": {}
}How many MCP servers were first published on or after a date, with a split by namespace type. Call it for growth questions like 'How many new MCP servers since October?'. Example: date="2026-10-01" (YYYY-MM-DD).
| Argument | Type | Description |
|---|---|---|
| date* | string |
{
"type": "object",
"title": "new_servers_count_sinceArguments",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"title": "Date"
}
}
}How many MCP servers the Official MCP Registry lists, split by status (active, deprecated), remote transport (streamable-http, sse) and package type (npm, pypi, ...). Call it for questions like 'How many MCP servers are there?' or when you need a headline number for a post, slide or dashboard. No arguments.
No arguments.
{
"type": "object",
"title": "registry_totalsArguments",
"properties": {}
}Date and source of the data behind the other tools, and which fields are kept. Call it when you want to cite the data or tell the user which day the numbers describe. No arguments.
No arguments.
{
"type": "object",
"title": "snapshot_infoArguments",
"properties": {}
}Notable changes to the MCP and A2A specifications on or after a date, each as a one-line summary with a link to the source. A short curated list, not a full changelog. Call it for questions like 'What changed in the MCP spec this year?'. Example: date="2026-01-01" (YYYY-MM-DD).
| Argument | Type | Description |
|---|---|---|
| date* | string |
{
"type": "object",
"title": "spec_changes_sinceArguments",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"title": "Date"
}
}
}