Skip to main content
Glama

Server Details

MCP server counts from the official registry, new servers per day, and MCP/A2A spec changes. As is.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 8 tools

Disambiguation4/5

The tools mostly target distinct analytical questions: time series, threshold counts, totals, breakdowns, freshness, provenance, and spec changes. However, ecosystem_overview vs registry_totals overlap on total server counts, and data_freshness vs snapshot_info both concern snapshot metadata, though descriptions clarify the intended use.

Naming Consistency5/5

All tool names use consistent snake_case with descriptive noun phrases, and the optional 'since' suffix is applied uniformly to time-threshold tools. The convention is predictable throughout the set.

Tool Count5/5

Eight tools is well-scoped for a focused analytics server, with each tool covering a distinct slice of the MCP ecosystem data. There is no excessive surface area or thin coverage.

Completeness4/5

The surface covers totals, breakdowns, daily growth, threshold counts, freshness, provenance, and spec changes, which is strong for the stated purpose. Minor gaps exist, such as no time-series breakdown by namespace or transport, but agents can work around these using existing tools.

Available Tools

8 tools
daily_new_countsA
Read-onlyIdempotent
Inspect

Returns a ready-to-chart series of new MCP servers per UTC day for the last N days (1 to 365). The last day can be partial, see snapshot_at. Example output: {"days":3,"series":[{"date":"2026-10-30","new_servers":551}]}. Optional argument: days, default 30. With no arguments you get 30 days. Good for 'Show daily new MCP servers over the last two weeks'.

Inputs: days.

data_freshnessA
Read-onlyIdempotent
Inspect

Returns how old these numbers are: the snapshot date, its age in days today (UTC), whether it is older than 7 days, the newest server first publish date and the newest spec change date in the data, and how the data is refreshed. Example output: {"snapshot_date":"2026-10-31","snapshot_age_days":0,"is_stale":false}. No arguments. Good for 'How fresh is this data?'.

Inputs: no named parameters.

ecosystem_overviewA
Read-onlyIdempotent
Inspect

Returns the total number of servers in the Official MCP Registry, new servers in the last 7 and 30 days, the 3 latest MCP and A2A spec changes with source links, and the snapshot date. Example output: {"total_servers":53618,"new_servers_last_7_days":{"count":4044},"snapshot_date":"2026-10-31"}. No arguments. Good for 'How big is the MCP ecosystem and what changed lately?'.

Inputs: no named parameters.

namespace_typesA
Read-onlyIdempotent
Inspect

Returns who publishes MCP servers and how: the split between code host namespaces (io.github, io.gitlab, io.bitbucket) and publishers' own domains, by servers and by distinct namespaces. Example output: {"servers_by_namespace_type":{"io.github":31407,"own-domain":22209}}. No arguments. Good for 'What share of MCP servers use their own domain?'.

Inputs: no named parameters.

new_servers_count_sinceA
Read-onlyIdempotent
Inspect

Returns how many MCP servers were first published on or after a date, split by namespace type. Example output: {"since":"2026-10-01","count":16045}. Optional argument: date as YYYY-MM-DD, for example "2026-10-01". With no arguments it counts the last 30 days up to the snapshot date. Good for 'How many new MCP servers since October?'.

Inputs: date.

registry_totalsA
Read-onlyIdempotent
Inspect

Returns how many MCP servers the Official MCP Registry lists, split by status (active, deprecated), remote transport (streamable-http, sse) and package type (npm, pypi, ...). Example output: {"unique_servers":53618,"by_status":{"active":52778,"deprecated":840}}. No arguments. Good for 'How many MCP servers are there, and how many run remotely?'.

Inputs: no named parameters.

snapshot_infoA
Read-onlyIdempotent
Inspect

Returns the snapshot date and source behind the other tools, and which fields are kept or dropped. Example output: {"snapshot_at":"2026-10-31T00:00:00Z","source":"Official MCP Registry"}. No arguments. Good for 'Which day do these numbers describe and where do they come from?'.

Inputs: no named parameters.

spec_changes_sinceA
Read-onlyIdempotent
Inspect

Returns what changed in the MCP and A2A specifications since a date, each as a short summary in our own words with a link to the release notes. A short curated list, not a full changelog. Example output: {"since":"2026-01-01","count":4,"changes":[{"spec":"MCP specification","tag":"2026-07-28"}]}. Optional argument: date as YYYY-MM-DD, for example "2026-01-01". With no arguments it starts on 1 January of the snapshot year. Good for 'What changed in the MCP spec this year?'.

Inputs: date.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Answers count questions about the MCP server ecosystem, including totals, growth over time, namespace types, daily new servers, data freshness, and recent MCP/A2A spec changes, using a dated snapshot of the Official MCP Registry.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      ead-only MCP server over ProtocolProbe's public API: dated public-record facts about servers in the official MCP registry (record checks, servers by topic, registry size and daily changes). Needs no key and calls no other server's tools.
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for academic research with shared token bucket governance, evidence-based read depth, and archival inscription. Uses multiple sources with failover to avoid rate limits.
      6
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources