Skip to main content
Glama

Shopgoodwill

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

ShopGoodwill auctions — active listings, closed auctions with final sale

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 22 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-shopgoodwill
GitHub Stars
0
Server Listing
ShopGoodwill Auctions

TDQS

A4/5.0

Scored across 39 tools

Disambiguation3/5

The highly detailed descriptions do a lot of work separating the tools, but there are real overlap clusters: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research are four entry points to the same router, and polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread, polymarket_edge_tracker and polymarket_fill_risk all scan or validate prediction-market opportunities. An agent can navigate with the docs, but boundaries like 'edges vs arbitrage' or 'beta vs stable' require careful reading rather than being self-evident. entity_profile / company_facts / compare_entities / recent_changes are better differentiated.

Naming Consistency4/5

Nearly everything is lowercase snake_case with a recognizable verb_noun or domain_noun shape (resolve_entity, validate_claim, search_within, shopgoodwill_search, polymarket_edges). A few entries break the verb-led pattern (entity_profile, company_facts, pipeworx_trending, ask_pipeworx_beta) but stay in the same casing convention, and domain prefixes (polymarket_, shopgoodwill_, ask_pipeworx_) are applied consistently.

Tool Count2/5

39 tools is well past the heavy threshold and the count is driven by a sprawling multi-domain gateway (SEC, FDA, FRED, prediction markets, npm, AI-marketing, memory, subscriptions) rather than the ShopGoodwill auction domain the server is named for. Several families are redundant (three ask_pipeworx variants, five polymarket tools) so the bulk is not fully earned.

Completeness4/5

For the auction domain itself the surface is tight and complete (search, item detail, sold-price comps) and the surrounding gateway covers research, entity resolution, memory, feedback and subscription lifecycle with few dead ends. Minor gaps exist, e.g. no browsing/taxonomy tool for ShopGoodwill categories and memory/subscription depth depends on authentication, but nothing that would block a typical workflow.

Tool Schema Changelog

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

  1. 4 tool updates
    • Changeddeep_research8 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / input
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / prompt
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / q
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / query
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases."
      • addedInput schema / properties / text
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • Changedforget4 fields changed
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key to delete"New value: +"Memory key to delete. Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
    • Changedrecall4 fields changed
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key to retrieve (omit to list all keys)"New value: +"Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
    • Changedremember9 fields changed
      • addedInput schema / properties / content
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / data
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\")"New value: +"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / text
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / v
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • changedInput schema / properties / value / description
        Previous value: -"Value to store (any text — findings, addresses, preferences, notes)"New value: +"Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON."
  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 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 observedshopgoodwill_item
    • First observedshopgoodwill_search
    • First observedshopgoodwill_sold_search
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • mcp-gov-auctions

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides access to government auctions data for physical-asset auctions including surplus, seized, and forfeited items. Designed for AI agents to query and retrieve auction information via natural language.
    386 npm
    1
    MIT

  • GovAuctions MCP server

    benswork-space
    A
    license
    Not graded
    quality
    B
    maintenance
    GovAuctions.app is a free public site for searching government surplus auctions. This MCP server exposes its data: live listings from GSA and other public sellers across the US, UK, CA and AU, sold-price comps from 170,000+ closed auctions, and a 0-100 Flip Score resale signal.
    6 npm
    MIT

  • us-auctions

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables searching live US auction lots and auction events across commercial auction houses and government surplus sources by keyword, state, or proximity to a ZIP, and retrieving sold-price comps and coverage data.
    46 npm
    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