Skip to main content
Glama
bridge-applications

Pebbler MCP

Official
by bridge-applications
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Pebbler MCP

No user-submitted related servers found.

    Related Servers

    • Datapoint MCP

      impel-intelligence
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to recruit real humans for evaluation tasks like surveys, A/B tests, and ratings on text, images, audio, and video, returning aggregated results directly into the conversation.
      13
      7
      MIT

    • GetABrain🧠 | Live Human-in

      Guitarmaniac24
      A
      license
      A
      quality
      D
      maintenance
      Real human judgment as agent tools -- an AI agent can ask a question and get back a structured, schema-validated JSON answer from a real quality-scored human. 16 response types (yes/no, ratings, rankings, A/B tests, sentiment, image/video/audio review, voice/video/photo capture). Fully programmatic signup with a $5 free trial credit, no card required.
      7
      62 npm
      MIT

    • qloo-mcp

      NoBanks
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to resolve and search taste entities and tags, get recommendations, demographics, and taste analysis, and run an audience-finding agent that turns a creative work description into audience affinities, local places, and a ready-to-use pitch.
      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.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct lifecycle step: catalog discovery, study creation, quote refresh, local recovery, purchase, status polling, and results retrieval. Descriptions explicitly differentiate overlapping terms like quote vs. create and status vs. results.

    Naming Consistency5/5

    All tool names follow a predictable snake_case verb_noun pattern (get_catalog, create_study, list_local_studies, purchase_study, etc.). The convention is consistent and readable throughout.

    Tool Count5/5

    Seven tools appropriately cover the full workflow from format discovery through purchase, status tracking, and results retrieval, plus local recovery. No tool feels redundant or missing for the core scope.

    Completeness4/5

    The toolset covers the full study lifecycle: discovery, creation, quoting, purchase, status polling, results, and local recovery. Minor gaps exist for cancellation/refund or explicit study metadata retrieval, though immutability and the payment model may make these out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources