Skip to main content
Glama

mcp_registry_snapshot

Get a daily summary of the official MCP server registry: total servers, status breakdown, top namespaces, and 1-day deltas (newly added, reactivated, deprecated). Track ecosystem growth and detect deprecated servers in use.

Instructions

Today's summary of the official Model Context Protocol server registry. Returns total servers, by-status breakdown, top namespaces, and 1-day deltas (newly added, reactivated, deprecated). Captured daily at 9:30 AM UTC from registry.modelcontextprotocol.io. Useful when an agent wants to see how the MCP ecosystem is growing or detect freshly-deprecated servers it may be using. Free, no auth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main MCP tool handler for 'mcp_registry_snapshot'. Registered via server.tool(), it calls fetchJSON('/mcp/registry/snapshot') and formats a text response with total servers, status breakdown, top namespaces, and 1-day deltas (newly added, reactivated, deprecated). Free, no auth required.
    server.tool(
      'mcp_registry_snapshot',
      'Today\'s summary of the official Model Context Protocol server registry. Returns total servers, by-status breakdown, top namespaces, and 1-day deltas (newly added, reactivated, deprecated). Captured daily at 9:30 AM UTC from registry.modelcontextprotocol.io. Useful when an agent wants to see how the MCP ecosystem is growing or detect freshly-deprecated servers it may be using. Free, no auth.',
      {},
      async () => {
        const data = (await fetchJSON('/mcp/registry/snapshot')) as {
          summary: {
            date: string;
            capturedAt: string;
            total_servers: number;
            total_versions: number;
            by_status: Record<string, number>;
            top_namespaces: { namespace: string; count: number }[];
            new_today: { count: number; names: string[] };
            reactivated_today: { count: number; names: string[] };
            deprecated_today: { count: number; names: string[] };
            delta_vs_yesterday: { added: number; removed: number; net: number } | null;
          };
        };
        const s = data.summary;
        const statusLine = Object.entries(s.by_status)
          .map(([k, v]) => `${k}: ${v}`)
          .join(', ');
        const topNs = s.top_namespaces.slice(0, 10).map(n => `  ${n.namespace}: ${n.count}`).join('\n');
        const delta = s.delta_vs_yesterday
          ? `Day over day: +${s.delta_vs_yesterday.added} new, -${s.delta_vs_yesterday.removed} removed, net ${s.delta_vs_yesterday.net >= 0 ? '+' : ''}${s.delta_vs_yesterday.net}`
          : 'Day over day: not available (first snapshot)';
        const newToday = s.new_today.count > 0
          ? `\nNewly listed today (${s.new_today.count}):\n` + s.new_today.names.slice(0, 10).map(n => `  ${n}`).join('\n')
          : '';
        const deprecatedToday = s.deprecated_today.count > 0
          ? `\nDeprecated today (${s.deprecated_today.count}):\n` + s.deprecated_today.names.slice(0, 10).map(n => `  ${n}`).join('\n')
          : '';
        return {
          content: [
            {
              type: 'text' as const,
              text:
                `MCP Server Registry — ${s.date}\n` +
                `Total servers: ${s.total_servers} (across ${s.total_versions} versioned entries)\n` +
                `Status: ${statusLine}\n${delta}\n\n` +
                `Top namespaces:\n${topNs}` +
                newToday + deprecatedToday +
                `\n\nSource: registry.modelcontextprotocol.io`,
            },
          ],
        };
      },
    );
  • Tool registration using server.tool('mcp_registry_snapshot', ...) which registers the tool name with the MCP server. Also includes the handler inline (same block).
    server.tool(
      'mcp_registry_snapshot',
      'Today\'s summary of the official Model Context Protocol server registry. Returns total servers, by-status breakdown, top namespaces, and 1-day deltas (newly added, reactivated, deprecated). Captured daily at 9:30 AM UTC from registry.modelcontextprotocol.io. Useful when an agent wants to see how the MCP ecosystem is growing or detect freshly-deprecated servers it may be using. Free, no auth.',
      {},
      async () => {
        const data = (await fetchJSON('/mcp/registry/snapshot')) as {
          summary: {
            date: string;
            capturedAt: string;
            total_servers: number;
            total_versions: number;
            by_status: Record<string, number>;
            top_namespaces: { namespace: string; count: number }[];
            new_today: { count: number; names: string[] };
            reactivated_today: { count: number; names: string[] };
            deprecated_today: { count: number; names: string[] };
            delta_vs_yesterday: { added: number; removed: number; net: number } | null;
          };
        };
        const s = data.summary;
        const statusLine = Object.entries(s.by_status)
          .map(([k, v]) => `${k}: ${v}`)
          .join(', ');
        const topNs = s.top_namespaces.slice(0, 10).map(n => `  ${n.namespace}: ${n.count}`).join('\n');
        const delta = s.delta_vs_yesterday
          ? `Day over day: +${s.delta_vs_yesterday.added} new, -${s.delta_vs_yesterday.removed} removed, net ${s.delta_vs_yesterday.net >= 0 ? '+' : ''}${s.delta_vs_yesterday.net}`
          : 'Day over day: not available (first snapshot)';
        const newToday = s.new_today.count > 0
          ? `\nNewly listed today (${s.new_today.count}):\n` + s.new_today.names.slice(0, 10).map(n => `  ${n}`).join('\n')
          : '';
        const deprecatedToday = s.deprecated_today.count > 0
          ? `\nDeprecated today (${s.deprecated_today.count}):\n` + s.deprecated_today.names.slice(0, 10).map(n => `  ${n}`).join('\n')
          : '';
        return {
          content: [
            {
              type: 'text' as const,
              text:
                `MCP Server Registry — ${s.date}\n` +
                `Total servers: ${s.total_servers} (across ${s.total_versions} versioned entries)\n` +
                `Status: ${statusLine}\n${delta}\n\n` +
                `Top namespaces:\n${topNs}` +
                newToday + deprecatedToday +
                `\n\nSource: registry.modelcontextprotocol.io`,
            },
          ],
        };
      },
    );
  • TypeScript interface MCPRegistrySnapshotResponse defining the shape of the API response, including ok, summary fields (date, capturedAt, total_servers, total_versions, by_status, top_namespaces, new_today, reactivated_today, deprecated_today, delta_vs_yesterday, pages_fetched, fetch_truncated).
    export interface MCPRegistrySnapshotResponse {
      ok: boolean;
      summary: {
        date: string;
        capturedAt: string;
        total_servers: number;
        total_versions: number;
        by_status: Record<string, number>;
        top_namespaces: Array<{ namespace: string; count: number }>;
        new_today: { count: number; names: string[] };
        reactivated_today: { count: number; names: string[] };
        deprecated_today: { count: number; names: string[] };
        delta_vs_yesterday: { added: number; removed: number; net: number } | null;
        pages_fetched: number;
        fetch_truncated: boolean;
      };
    }
  • JavaScript SDK helper method getMCPRegistrySnapshot() that calls this.request('GET', '/mcp/registry/snapshot') as a typed convenience wrapper.
    async getMCPRegistrySnapshot(): Promise<MCPRegistrySnapshotResponse> {
      return this.request<MCPRegistrySnapshotResponse>('GET', '/mcp/registry/snapshot');
    }
  • Python SDK helper method get_mcp_registry_snapshot() that calls self._request('GET', '/mcp/registry/snapshot') returning a dict.
    def get_mcp_registry_snapshot(self) -> dict[str, Any]:
        """Today's summary of the official MCP server registry.
    
        Free, no auth. Returns total servers, by-status breakdown, top
        namespaces, and 1-day deltas (newly added, reactivated, deprecated).
        Captured daily at 9:30 AM UTC from registry.modelcontextprotocol.io.
    
        Returns:
            Dict with ``ok`` and ``summary`` keys. The ``summary`` includes
            ``date``, ``total_servers``, ``by_status``, ``top_namespaces``,
            ``new_today``, and ``delta_vs_yesterday``.
        """
        return self._request("GET", "/mcp/registry/snapshot")
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It clearly states the tool is read-only (summary, no mutation), free, and captured daily at a fixed time. It does not mention idempotency or caching behavior, but the snapshot nature implies it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, dense paragraph covering all key aspects: what it returns, capture time, use cases, and access. It is concise without being verbose, though a bullet list could improve readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (no params, no output schema), the description adequately covers the tool's purpose, output details, and typical use cases. It could be enhanced by mentioning that results remain static until the next daily capture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, making parameter description unnecessary. The description explains the tool's function without needing parameters, meeting the baseline for 0-param tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a daily summary of the MCP registry, specifying exact outputs: total servers, by-status breakdown, top namespaces, and 1-day deltas. It distinguishes itself from the sibling tool mcp_registry_series by emphasizing 'snapshot' and daily capture.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use it: for understanding ecosystem growth or detecting deprecated servers. It adds practical context with 'Free, no auth.' However, it does not explicitly mention alternatives or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RipperMercs/tensorfeed'

If you have feedback or need assistance with the MCP directory API, please join our Discord server