Skip to main content
Glama
resuly

io.github.resuly/daleads-mcp

by resuly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.resuly/daleads-mcp

No user-submitted related servers found.

    Related Servers

    • Realty In Au MCP Server

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      Enables access to Australian real estate data through the Realty In Au API, supporting property listings, agent/agency information, property details, school lookups, and property search with various filters.
      13
      MIT

    • RoyceCo Victorian Property

      JDuRieu26
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables live access to free, open Victorian government spatial data for property due diligence, covering site screening, planning controls, parcels, contamination, heritage, and flood checks without API keys.
      -

    • mcp-datagov-au

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and retrieving Australian open government data from data.gov.au via CKAN API, including datasets, organizations, groups, tags, and resources.
      8 npm
      MIT

    • mcp-arcgis-asheville

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying City of Asheville open geospatial data (parcels, zoning, etc.) through ArcGIS Feature Services. Supports searching datasets, querying layers with SQL-like filters, and retrieving layer schemas.
      8 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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes. search_das and nearby_das both find DAs but by different criteria (filters vs. location), and property_intelligence is broader than nearby_das. The sample tools are clearly demos. Minor potential confusion between search_das and nearby_das when both are applicable, but descriptions mitigate.

    Naming Consistency2/5

    Naming is mixed: verb_noun (search_das, get_da, list_categories, list_councils, get_stats), descriptive (nearby_das, sql_query), and a property_* prefix group (property_intelligence, property_sample, property_flood_sample, property_sandbox_addresses). No consistent verb or noun pattern across the entire tool set.

    Tool Count5/5

    11 tools is well-scoped for a DA lookup and property intelligence server. Each tool contributes a distinct capability: search, get, nearby, metadata, stats, SQL access, and property intelligence samples. No redundant or excessive tools.

    Completeness5/5

    The tool surface covers the domain comprehensively: searching with many filters, retrieving full details, geospatial search, metadata lists, statistics, and raw query capability. Property intelligence adds a complementary feature set. No obvious gaps such as missing update/create, which are irrelevant for a read-only public data API.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources