Skip to main content
Glama
Sign In
AuditSocials Glossary MCP

AuditSocials Glossary MCP

Official
by auditsocials
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AuditSocials Glossary MCP

No user-submitted related servers found.

    Related Servers

    • Google Ads MCP Server

      Johansebastian96
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs and AI agents to query ad account data, inspect resource metadata, and access reporting dimensions, segments, and API discovery/release information.
      3
      Apache 2.0

    • govcon-mcp

      steve-in-tandem
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI clients with deterministic lookup and cross-walk tools for 1,460+ public-sector contracting references, covering FAR/DFARS, SBA set-asides, NAICS/PSC/NIGP codes, procurement portals, glossary terms, and capture playbooks.
      760 npm
      MIT
    • Orphex MCP

      Orphex MCPofficial

      OrphexTech
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query advertising spend, ROAS, campaigns, pacing and anomalies across many ad, analytics and commerce platforms, and to make approval-first changes such as pausing campaigns or adjusting budgets after a preview.
      1
      Apache 2.0

    • Facebook Ads MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to browse and query Facebook Ads data including ad accounts, campaigns, ad sets, and performance insights via natural language.
      184 npm
      MIT
    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.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct and non-overlapping purpose: define a specific term, search by keyword, and list categories. There is no ambiguity about which tool to use for a given task.

    Naming Consistency5/5

    All tools follow the consistent pattern 'glossary_<verb>_<noun>' (glossary_define, glossary_search, glossary_list_categories). The naming is predictable and clearly conveys the action and resource.

    Tool Count4/5

    Three tools is a reasonable number for a focused glossary server. It covers the core operations without being too sparse, though a few more tools (e.g., list all terms) could be added without causing bloat.

    Completeness4/5

    The tool surface covers the essential workflows: discovering terms (search and categories) and retrieving detailed definitions. A minor gap is the lack of a tool to list all terms directly, but the search and category tools adequately enable discovery.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources