Skip to main content
Glama
paintbrushv

platworks-mcp

by paintbrushv

Related Servers

Alternatives to platworks-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      A read-only MCP server that exposes SF Peninsula building-permit and parcel-buildability data, enabling queries on permits, SB 9 eligibility, ADU potential, and redevelopment leads.
      6
      53 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server providing direct, credentialed access to parcel data via Regrid and county ArcGIS sources, with tools for querying by point, owner, size, and county.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Read-only MCP server for finding, comparing, and shortlisting engineering parts from distributor and marketplace APIs.
      6
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server that exposes a design system's tokens, components, conventions, and deprecations as queryable tools, enabling agents to look up canonical values, assess change impact, and detect hardcoded value drift.
      8
      2 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 19 tools

    Disambiguation3/5

    The catalog tools (list_components, list_private_components, list_public_components, find_components, search_components) overlap in purpose and could be easily confused despite detailed descriptions. The underwriting and renovation tools are more distinct, but the listing cluster makes selection less certain.

    Naming Consistency3/5

    Most tools use snake_case, but conventions are mixed: list_*/get_*/search_*/find_* follow a verb-first pattern, while underwrite_run, underwrite_backsolve, tax_regime_lookup, renovation_estimate, renovation_roi, and ops_review do not. Names remain readable and mostly predictable, but not uniformly consistent.

    Tool Count3/5

    At 19 tools, the server sits in the heavy range and spans several distinct domains: component discovery, underwriting, renovation, and operations review. Each tool appears purposeful, but the breadth makes the surface feel larger than a tightly-scoped MCP server.

    Completeness4/5

    The component catalog is well covered with list/get/find/search/category/overview tools, and the underwriting workflow has run, backsolve, tax lookup, renovation estimate/ROI/SOW, bid evaluation, and ops review. Minor gaps exist, such as no explicit list of supported tax states or deal schema endpoint, but agents can complete core workflows without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues