Skip to main content
Glama
outis-co

franchisedata-mcp

by outis-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to franchisedata-mcp

No user-submitted related servers found.

    Related Servers

    • RestoSignals

      paperandbeyond23-gif
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents and sales teams to surface US restaurants and bars roughly one to six months before they open, ranked by a readiness score and paired with owner contact details drawn from public liquor-license, permit, and business filings. It also exposes live coverage checks, the raw fused filings behind each venue, and webhook alerts when a new matching venue appears.
      MIT

    • daxoom

      CITROOT
      F
      license
      Not graded
      quality
      D
      maintenance
      The owner-verified local business data + service & menu-price layer for AI agents. Owner-authored business profiles where every response carries provenance — verification level, completeness score, freshness timestamps, and upstream sources. * Search & profiles — find businesses by name, category, city, or geo-radius; full profiles with contacts, hours, media, ratings. * Price layer
      -

    • guerrilla-franchising-mcp

      synyrgx
      A
      license
      A
      quality
      D
      maintenance
      Franchise evaluation tools built from 81+ closed deals. Validate FDD investment ranges, identify red flags, assess readiness, and connect with a free franchise consultant. E-2 visa guide in English and Spanish.
      8
      4 npm
      MIT

    • Restaurant AI MCP Server

      CSOAI-ORG
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides hospitality intelligence tools for restaurant optimization, including menu profitability analysis, food cost calculation, reservation management, review sentiment analysis, and allergen checking.
      0
      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 17 tools

    Disambiguation4/5

    Descriptions include explicit WHEN TO USE / WHEN NOT TO USE / ALTERNATIVES sections, making most boundaries clear (e.g. mcdonalds_locations vs franchise_search_near, search_brands vs semantic_vector_search). Minor overlap remains among the analytics tools (get_weekly_scorecard vs recommend_local_action, and get_local_share_of_choice vs get_menu_pricing both touch delivery pricing), but the cross-references largely resolve it.

    Naming Consistency4/5

    Predominantly snake_case with clear verb_noun structure (search_brands, get_operator_intelligence, detect_tech_stack, track_brand_changes). Deviations are brand-prefixed or noun-only names (mcdonalds_locations, starbucks_store_status, semantic_vector_search) which break the pattern but stay readable and snake_case.

    Tool Count4/5

    17 tools is slightly above the ideal range but each targets a distinct data source or operation, so they mostly earn their place. The generic fetch_franchise_data escape hatch coexists sensibly with the specialized shortcuts.

    Completeness4/5

    Strong coverage of discovery, endpoints, billing, geolocation, operator intelligence, tech stack, brand change tracking, menu pricing, FDD financials, delivery share, and operational scorecards. Read-oriented surface is fairly complete; a dedicated single-brand detail tool and more lifecycle/write operations are minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources