Skip to main content
Glama
clevertechca

CleverTech MCP Server

Official
by clevertechca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to CleverTech MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-canada

      ReyemTech
      A
      license
      A
      quality
      B
      maintenance
      MCP server giving AI agents structured access to Canadian federal, provincial, and municipal government data.
      5
      60
      MIT

    • local-dfw-mcp

      LizzleChen
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to answer DFW civic and property questions using official data sources without API keys.
      9
      106 npm
      2
      Apache 2.0

    • mcp-statscan

      pipeworx-io
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides access to Statistics Canada official statistics without authentication, enabling AI agents to query Canadian economic and demographic data.
      5 npm
      MIT

    • DataEdmonton MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query Edmonton's open data portal via the Socrata SODA API. Part of the Pipeworx MCP gateway.
      147 npm
      MIT

    • DataToronto MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query City of Toronto open data through the CKAN API, providing access to 893+ live data sources via Pipeworx.
      145 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.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action: property search, roll lookup, permits, zoning, and DLS conversion each have distinct purposes. The only mild overlap is between property_report and the individual permit/zoning lookups, and between reverse_geocode and dls_convert, but the descriptions clarify scope well enough to avoid real confusion.

    Naming Consistency4/5

    Tool names mostly follow a clear [domain]_[action] snake_case pattern like property_search, building_permit_search, and zoning_lookup. A few names like property_by_roll, property_top, and building_permit_recent deviate from the verb-oriented pattern, but the overall convention remains predictable and readable.

    Tool Count5/5

    Twelve tools is well-scoped for a real-estate and land-data server: property data, permits, zoning, DLS conversion, geocoding, and business registry search are each represented without redundant tools. Each tool serves a distinct workflow, and the count feels proportional to the domain.

    Completeness5/5

    The tool surface covers the advertised domain thoroughly: property discovery, detailed reports, roll-based lookup, top listings, DLS conversion in single and batch modes, permit search and recent activity, zoning lookup, reverse geocoding, and city discovery. No obvious dead ends or missing core operations are apparent for a read-only data API.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources