Skip to main content
Glama
derekslinz

meta-data-mcp

by derekslinz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to meta-data-mcp

No user-submitted related servers found.

    Related Servers

    • Open Emirates Intelligence

      ahmedvnabil
      A
      license
      Not graded
      quality
      B
      maintenance
      A comprehensive MCP server that makes official UAE open data queryable through natural language, offering tools for source discovery, dataset search, spatial joins, and intelligence recipes.
      55 npm
      MIT
    • ReefAPI MCP by reefapi

      ReefAPI MCPofficial

      reefapi
      A
      license
      A
      quality
      C
      maintenance
      One MCP server providing access to 160+ live web data APIs (search, social media, e-commerce, real estate, jobs, travel, news, finance, and more) using dynamic discovery via 4 generic tools to avoid the agent's tool limit.
      5
      3
      MIT

    • Polymath MCP

      Moreti2002
      A
      license
      A
      quality
      B
      maintenance
      Aggregates 17 free, keyless research sources into a single MCP server, enabling unified search for papers, code, models, trends, standards, and electronic components with deduplicated results.
      8
      MIT
    • fd-daas-mcp by FindDataTechnology

      fd-daas-mcpofficial

      FindDataTechnology
      A
      license
      Not graded
      quality
      C
      maintenance
      Consolidated MCP server exposing 161 tools across 9 groups to manage a layered data platform (financial, economic, statistical) backed by a single SQLite file, with data fetching delegated to an upstream semantic fetcher.
      MIT

    • InfiniteMCP

      day50-dev
      F
      license
      Not graded
      quality
      D
      maintenance
      A meta-MCP server that acts as a universal gateway, allowing users to discover and execute tools from thousands of other MCP servers through semantic search. It dynamically loads servers on demand and provides standardized functions for searching, discovering, and running tools across the entire MCP ecosystem.
      6
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool serves a distinct purpose: provider discovery vs activation vs health, plugin drafting vs creation, federated query vs comparison. Even the two federate tools are clearly separated by output (merged series vs coverage matrix). No two tools appear to duplicate each other.

    Naming Consistency4/5

    The vast majority follow the 'opendata_<resource>_<verb>' pattern (e.g., providers_list, plugins_create, health_snapshot). However, three tools deviate with verb-object order (federate_query, federate_compare, explain_choice), which is a minor inconsistency in an otherwise readable and predictable scheme.

    Tool Count5/5

    15 tools is at the upper edge of the ideal range but perfectly appropriate for the server's scope: it manages providers, plugins, health monitoring, federation, and vocabulary. Each tool earns its place with a clear role, and none feel redundant or excessive.

    Completeness4/5

    The core workflows are well covered: discover providers, activate/deactivate, run federated queries, and create new plugins. The only minor gaps are the absence of an explicit update/delete lifecycle for plugins (though plugin creation is the intended path) and no unregister operation for providers beyond deactivation. These do not prevent typical agent workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources