Skip to main content
Glama
Sign In
woodydaniel

whodoicallfor-mcp

by woodydaniel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to whodoicallfor-mcp

No user-submitted related servers found.

    Related Servers

    • FixLoop

      nishigandhamali
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes household incident recovery tools over a self-hosted MCP endpoint, letting a voice assistant capture a home problem, diagnose it, draft and hash an approval card, then deliver an approved repair request to a technician either as a simulated record or a real email. Delivery is at-most-once via idempotency keys, with the recipient address bound into the approval hash.
      14 npm
      MIT

    • HomeBrain

      ramkumar122
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that gives an Alexa+ household a durable operational memory for home repairs, warranties, and service cases, enabling multi-turn troubleshooting, provider booking, and reminders.
      Apache 2.0

    • field-agent-mcp

      YihengLi-1
      A
      license
      A
      quality
      D
      maintenance
      MCP server for a production-shaped service-business agent, enabling grounded knowledge search, intake collection, and human escalation with deterministic safety boundaries.
      3
      MIT

    • nyc-property-intel

      ccedacero
      A
      license
      A
      quality
      A
      maintenance
      MCP server for NYC real estate due diligence. Lets Claude query 22+ NYC public-record databases — DOB/HPD/ECB violations, ACRIS deeds, DOF sales, 311 complaints, FDNY incidents, NYPD complaints, marshal evictions, PLUTO, rent stabilization — in plain English.
      18
      7
      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.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct role: routing from a natural language description, retrieving full details for a specific scenario, and listing all available scenarios. There is no functional overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case: route_emergency, get_scenario, list_scenarios. The naming is predictable and intuitive.

    Tool Count5/5

    With only three tools, the server is tightly scoped to the home emergency reference purpose. Each tool earns its place and the count feels neither sparse nor excessive.

    Completeness5/5

    The tool surface covers the full workflow: discover available scenarios (list_scenarios), route from a plain-language emergency (route_emergency), and drill into full details (get_scenario). No obvious gaps for the intended use case.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources