Skip to main content
Glama

Estatesales Net

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

EstateSales.NET MCP — upcoming estate sales, by ZIP

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.2% over 25 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-estatesales-net
GitHub Stars
1
Server Listing
estatesales-net

TDQS

A4/5.0

Scored across 39 tools

Disambiguation3/5

Several tools overlap heavily in purpose: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, entity_profile, company_facts, compare_entities, and recent_changes all answer research-style questions, while polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, and bet_research form a dense cluster of betting/market tools. Descriptions do attempt to guide selection and disambiguate, but the sheer number of near-neighbours means an agent can easily misselect.

Naming Consistency4/5

Almost all tool names use snake_case with clear prefixes for groups (ask_pipeworx*, polymarket_*, estatesales_*, resolution_*, pipeworx_*), which is easy to read. However, verb styles are mixed: some are verb-led (ask_pipeworx, compare_entities, validate_claim, resolve_entity, scan_dependency) while others are noun-phrase (company_facts, entity_profile, resolution_audit, recent_alerts), a minor inconsistency.

Tool Count2/5

39 tools is well above the 25+ threshold that typically indicates an overloaded surface, and the set spans many unrelated domains (estate sales, AI visibility, npm dependency scanning, prediction-market arbitrage, SEC financials, weather). Despite the broad Pipeworx gateway scope, this many tools is heavy for an agent to navigate and is mismatched with the narrow-sounding server name 'Estatesales Net'.

Completeness4/5

The surface covers a wide range of domains: estate-sale search/detail/companies, company financials and profiles, prediction-market analysis, memory, subscriptions, alerts, feedback, and AI-visibility checks. Gaps are minor (e.g., estate sales are read-only with no create/update, and some meta-tools lack write operations), but agents can work around them using the existing tools.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 39 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedestatesales_companies
    • First observedestatesales_sale
    • First observedestatesales_search
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • Zillapi - Zillow Property Data

    ZeroPointRepo
    A
    license
    Not graded
    quality
    B
    maintenance
    REST API and MCP server for Zillow property data: Zestimates, rent estimates, tax records, listing search, price history, photos, and 300+ fields. 4 tools with OAuth 2.1 + PKCE. Free tier: 100 credits.
    7
    MIT No Attribution

  • Correios: CEP

    mcp-dir
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for querying Brazilian postal codes (CEP) from the official Correios source, supporting read-only lookups via natural language in any MCP-compatible client.
    MIT

  • Redfin MCP Server

    HasData
    A
    license
    A
    quality
    A
    maintenance
    Search Redfin for-sale, for-rent, and sold listings with Redfin's full visitor filter set, and retrieve complete property pages as structured JSON, through any MCP client and without an MLS license.
    2
    2
    69 npm
    48 PyPI
    11
    MIT
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources