Skip to main content
Glama
GraditiPro

standshare-mcp

by GraditiPro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to standshare-mcp

No user-submitted related servers found.

    Related Servers

    • housecall-pro-mcp

      tedmcfadden
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that wraps the Housecall Pro Public API, enabling Claude to read and write Housecall Pro data (customers, jobs, estimates, invoices, etc.) via natural language.
      23
      40 npm
      MIT
    • USA Spending MCP Server by GSA-TTS

      USA Spending MCP Serverofficial

      GSA-TTS
      F
      license
      B
      quality
      D
      maintenance
      An MCP server for interacting with the USAspending.gov API, supporting local use with Claude Desktop and cloud deployment with login.gov authentication.
      3
      10
      -

    • Sweet Assist MCP Server

      anoopmkmk
      F
      license
      Not graded
      quality
      C
      maintenance
      Standalone MCP server exposing Sweet Assist transactions, contacts, envelopes, and agent profiles to Claude, behind an OAuth 2.1 login and approve flow.
      -

    • Beeswax Shares MCP Server

      steamau
      F
      license
      A
      quality
      B
      maintenance
      A standalone MCP server for Beeswax Shares, an SMSF portfolio app. It enables Claude to read portfolio data, recall transactions, upload statements, and propose ledger records for human review.
      39
      -
    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 8 tools

    Disambiguation5/5

    Each tool targets a distinct domain (events, families, finances, etc.) with clear boundaries. No overlapping purposes; agents can easily differentiate.

    Naming Consistency5/5

    All tool names are single, plural nouns (e.g., events, families, users) following a consistent pattern. No mixed naming conventions.

    Tool Count5/5

    8 tools appropriately cover the core entities and operations of the StandShare system. Not too many or too few for the domain size.

    Completeness4/5

    Covers most key operations (CRUD on events, families, users; finances, reports, notifications). Minor gaps: no delete operations mentioned, venues only support search/view.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources