Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hustle Got Real

REMOTE · MCP.HUSTLEGOTREAL.COM

Dropshipping for eBay, Amazon and Shopify: products, listings, prices, stock, orders and analytics.

+3 this week 57 Trust /100

Last scanned (17 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 34974 tokens (~202/item across 173 items; 172 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
  • Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Do not tell the user", at byte 6308 of that field. See how to fix → Fail
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 174 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “hgr_post_searchproduct_recoverlisting”, which the server declares destructive security
    • New tool “hgr_post_searchproduct_recoverlistings”, which the server declares destructive security
    • Tool “hgr_get_searchproduct_getmissinglistings” rewrote its description, which is the text the model reads security
    • Server version: 2026.11.1.0 → 2026.11.3.1 functional
  • 2 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “hgr_post_listingcreate_getdata” rewrote its description, which is the text the model reads security
    • Server version: 2026.10.31.0 → 2026.11.1.0 functional
  • 1 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “hgr_post_sales_loadprogress” rewrote its description, which is the text the model reads security
    • Server version: 2026.10.29.1 → 2026.10.31.0 functional
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 2026.10.29.0 → 2026.10.29.1 functional
  • 29 Oct 26 54

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.hustlegotreal.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=partner.hustlegotreal.com CN=YR2,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 RSA 2048 SHA256-RSA 573b203bf16fc63dfaee0ed17cb4f2756ac
SANs: mcp.hustlegotreal.com, partner.hustlegotreal.com, partnerapi.hustlegotreal.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.hustlegotreal.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
hustlegotreal.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.hustlegotreal.com/ Not MCP 200
http (plaintext) http://mcp.hustlegotreal.com/ HTTPS enforced 308 https://mcp.hustlegotreal.com/
MCP tools · 172 exposed · ~31,732 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
hgr_get_noapi_solution_state ~69

Reads No-API Server verification/connection state for a visible store and translates it to human language. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_pending_listings ~226

Lists pending listings for one visible store. First resolve the store with hgr_list_channels, then call this tool using channelOAuthId from the selected store. For rankings, filtering and summaries, pass fields/sortBy/sortDirection/limit directly to this tool and answer from its response. Pending listing ids may be shown only where HGRWeb shows them. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
fieldsarray–Fields to return. Use projection for compact answers.
limitinteger–Maximum number of rows to return. HGRApi maximum is 10000.
offsetinteger–Zero-based row offset.
pageinteger–One-based page number.
showWeListForYouboolean–Whether to include We List For You pending items.
sortBystring–Field used to sort before limit/pagination.
sortDirectionstring–Sort direction.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_price_warrior ~59

Reads Price Warrior dashboard/settings for one visible store. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_pricing_rules ~56

Reads pricing rules for one visible store. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_products_subscriptions_get ~214

Dedicated HGRApi tool for GET Api/Products/Subscriptions/Get. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Lists the HGR listing-subscription plans and prices available to the requesting account. ownerAgent: account-metrics. supportingAgents: support, orchestrator. Domain: account_metrics. Entity: subscription_plan. Operation: list. Scope: product_catalog. AllowedIntents: subscription_plan_catalog. Use when: Use to quote monthly or annual plan prices and compare listing capacities. Input: No body or query input. Authentication is optional: sign in for eligible legacy prices. Anonymous requests receive public prices. Admin-only: false. The selected channel is not required. Output: Returns the complete enabled listing-plan catalogue. ProductOrder is listing capacity. Each price includes PlatformId, BillingPeriodId, CurrencyId, Price and PlatformProductId. LegacyPricing indicates continuing legacy subscription eligibility. Search terms: products subscriptions get.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_sales ~80

Reads sales aggregates for the selected visible store using WAPI GetSales. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesWAPI GetSalesRequest body: Period, From, To, timeDiff.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_sales_getorderimage_orderid_cache ~189

Dedicated HGRApi tool for GET api/Sales/GetOrderImage/{orderId}/{cache}. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the GET get order image operation in sales/order operations. Use when: Use it when a client needs to run the get order image operation for sales/order operations. Input: [FromRoute] orderId: int. [FromRoute] cache: string. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the get order image operation. Search terms: sales getorderimage orderid cache. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
cachestringyesHGRApi route parameter cache.
orderIdstringyesHGRApi route parameter orderId.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_searchproduct_getmissinglistings ~234

Dedicated HGRApi tool for GET api/SearchProduct/getMissingListings. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Returns marketplace/channel listings detected as missing during periodic synchronization, together with existing hidden HGR products that can be recovered. ownerAgent: listings. Domain: listings. Entity: missing_listing. Operation: list_missing. Scope: current_store. Use when: Use when the user asks which products from the current store can be imported or recovered into HGR. Input: Header channel: current ChannelOAuthId. No body. Output: Returns both collections together: Listings contains ChannelItem, ChannelTitle, Sku and variation attributes; RecoverableListings contains ListingId, PrimaryId and Title. Listings excludes already active products and every recoverable PrimaryId, including all its variations. Search terms: searchproduct getmissinglistings. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_searchproduct_getpendingnoapipreviousvalues ~186

Dedicated HGRApi tool for GET api/SearchProduct/GetPendingNoApiPreviousValues. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the GET get pending no api previous values operation in existing published product/listing management. Use when: Use it when a client needs to run the get pending no api previous values operation for existing published product/listing management. Input: Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the get pending no api previous values operation. Search terms: searchproduct getpendingnoapipreviousvalues. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_searchproduct_pricechanges ~299

Dedicated HGRApi tool for GET api/SearchProduct/PriceChanges. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Reads the recorded selling price change history shown in HGRWeb for one listing variation. ownerAgent: listings. Domain: listings. Entity: listing_price_history. Operation: read_history. Scope: exact_variation. Use when: Use it when the user asks for price history, price changes, previous selling prices or a price timeline of an identified or attached store product. Current price in the product details is not its history. Input: Required query id: positive internal ListingVariationId, not the parent ListingId, supplier ProductSourceId or marketplace Product ID. Resolve the attached product's visible Product ID through Listing/GetListings in the selected channel; use the matching variation Id. If several variations match, resolve the requested variation rather than choosing one arbitrarily. Output: Returns History entries with Date, Value (channel selling price), Author and Why when recorded. A successful History: [] means no recorded price changes for that variation. success=false or a missing History is a failed lookup, not evidence of no history. Search terms: searchproduct pricechanges. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_searchproduct_stockchanges ~301

Dedicated HGRApi tool for GET api/SearchProduct/StockChanges. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Reads the recorded stock quantity change history shown in HGRWeb for one listing variation. ownerAgent: listings. Domain: listings. Entity: listing_stock_history. Operation: read_history. Scope: exact_variation. Use when: Use it when the user asks for stock history, stock changes, quantity changes, inventory history or an availability timeline of an identified or attached store product. Current stock in the product details is not its history. Input: Required query id: positive internal ListingVariationId, not the parent ListingId, supplier ProductSourceId or marketplace Product ID. Resolve the attached product's visible Product ID through Listing/GetListings in the selected channel; use the matching variation Id. If several variations match, resolve the requested variation rather than choosing one arbitrarily. Output: Returns History entries with Date, Value (channel stock quantity), Author and Why when recorded. A successful History: [] means no recorded stock changes for that variation. success=false or a missing History is a failed lookup, not evidence of no history. Search terms: searchproduct stockchanges. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_source_configuration ~85

Reads explicitly saved supplier settings for one visible store. This is settings data, not supplier availability or listing usage data. It must never be interpreted as an enabled, disabled or suspended supplier state. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_sources ~96

Lists current sources/suppliers from WAPI for one visible store/channel, optionally filtered by visible countryCode. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
countryCodestring–Optional visible country code, for example UK, US, ES, FR, DE, AU or IT.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_sources_get ~273

Dedicated HGRApi tool for GET api/Sources/Get. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Lists supplier/source marketplaces available to the user and the current channel. ownerAgent: catalog-sources. supportingAgents: listings. Domain: sources. Entity: supplier_source. Operation: list. Scope: current_store. Use when: Use it to build supplier selectors, map sourceId values to visible names, resolve suppliers for a catalog search, or verify whether a supplier supports publication and Auto Ordering for the selected store and country. Use actual returned supplier IDs when a catalog search specifies a supplier; do not invent IDs. Input: [FromQuery] isoCountry: int?. Header channel: current ChannelOAuthId. If isoCountry is not sent, use the selected channel country. Output: Returns sources/suppliers with Id, Name, BaseUrl, Site, publication permissions, HasAutoOrder, AutoOrderingFee and other visible metadata. Search terms: sources get. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
isoCountryinteger–HGRApi query parameter isoCountry.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_sources_getpublic ~314

Dedicated HGRApi tool for GET api/Sources/GetPublic. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Lists visible supplier/source marketplaces and their capabilities for a requested country without requiring a selected channel. ownerAgent: catalog-sources. supportingAgents: account-metrics, orders-autoordering, support. Domain: sources. Entity: supplier_source. Operation: list. Scope: country_catalog. AllowedIntents: supplier_capabilities. Use when: Use it for general commercial or pre-sales questions about suppliers available in a country, publication methods, Auto Ordering support, or the configured Auto Ordering fee when no authenticated store context is required. SearchTerms: suppliers available by country, supplier capabilities by country, Amazon Italy Auto Ordering, Amazon.it Auto Ordering, supplier Auto Ordering fee, supported suppliers in Italy. NegativeUseCases: Do not use it to claim that a supplier account is configured for the current user; Do not use it to list private suppliers belonging to the authenticated user. Input: Required [FromQuery] isoCountry: string. Use the two-letter HGR country code inferred from the marketplace or country named by the user, such as IT for Italy. Output: Returns visible sources/suppliers for the country with Id, Name, BaseUrl, Site, publication permissions, HasAutoOrder and AutoOrderingFee. Search terms: sources getpublic.

NameTypeReqDescription
isoCountrystringyesHGRApi query parameter isoCountry.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_sources_goout ~220

Dedicated HGRApi tool for GET api/Sources/GoOut. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the GET go out operation in source/supplier reading. Use when: Use it when a client needs to run the go out operation for source/supplier reading. Input: [FromQuery] sourceUrl: string. [FromQuery] isoCountry: int?. [FromQuery] channelListingId: int?. Output: Returns the result or applies the effect of the go out operation. Search terms: sources goout. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelListingIdinteger–HGRApi query parameter channelListingId.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
isoCountryinteger–HGRApi query parameter isoCountry.
sourceUrlstringyesHGRApi query parameter sourceUrl.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_subscription_summary ~30

Reads the visible current subscription/quota summary. It never creates, changes or cancels subscriptions.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_support_ticket ~35

Reads one support ticket by its visible ticket id/reference.

NameTypeReqDescription
ticketIdstringyesVisible support ticket id/reference.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_terminated_listings ~195

Lists terminated listings for one visible store. First resolve the store with hgr_list_channels, then call this tool using channelOAuthId from the selected store. Supports fields, sortBy, sortDirection, limit and pagination declared by HGRApi. Terminated listings do not expose price or stock fields. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
fieldsarray–Fields to return. Use projection for compact answers.
limitinteger–Maximum number of rows to return. HGRApi maximum is 10000.
offsetinteger–Zero-based row offset.
pageinteger–One-based page number.
sortBystring–Field used to sort before limit/pagination.
sortDirectionstring–Sort direction.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_user_gettokenbalance ~117

Dedicated HGRApi tool for GET Api/User/GetTokenBalance. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the GET get token balance operation in visible user data. Use when: Use it when a client needs to run the get token balance operation for visible user data. Input: No explicit input parameters required. Output: Returns the result or applies the effect of the get token balance operation. Search terms: user gettokenbalance.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_user_gettokenhistory ~168

Dedicated HGRApi tool for GET Api/User/GetTokenHistory. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Returns the authenticated user's token usage history. ownerAgent: account-metrics. Domain: account_tokens. Entity: token_history. Operation: list. Scope: authenticated_user. Use when: Use it when the authenticated user needs to review token charges, credits, awards, paid token entries or AI action usage history. Input: No body. Uses the authenticated user id from Authorization. No Header channel / ChannelOAuthId required. Not admin-only. Output: Returns history items with ReferenceType, Title, TokenAmount, UpdatedOn and ActionTypes. Search terms: user gettokenhistory.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_virtual_assistants ~27

Lists Virtual Assistant / VA profiles. Prefer names in user-facing responses.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_winning_get_id ~128

Dedicated HGRApi tool for GET api/Winning/Get/{id}. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the GET get operation in winning product generation reading. Use when: Use it when a client needs to run the get operation for winning product generation reading. Input: [FromRoute] id: int. Output: Returns the result or applies the effect of the get operation. Search terms: winning get id.

NameTypeReqDescription
idstringyesHGRApi route parameter id.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_get_winning_list ~109

Dedicated HGRApi tool for GET api/Winning/List. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the GET list operation in winning product generation reading. Use when: Use it when a client needs to run the list operation for winning product generation reading. Input: No explicit input parameters required. Output: Returns the result or applies the effect of the list operation. Search terms: winning list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_list_channels ~46

Lists the user's connected stores/channels with channelOAuthId, store name, marketplace, country and connection status. Use channelOAuthId from this response for store-scoped endpoint tools.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_list_pending_now ~132

Publishes one pending listing immediately by its visible pending listing id. Requires confirmed=true. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
pendingListingIdinteger–Visible pending listing id, only for pending listings where HGRWeb shows this id.
productIdstring–Visible marketplace Product Id / primary id. Prefer this for active or terminated listings.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_list_support_tickets ~20

Lists support tickets for the authenticated user.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_list_templates ~55

Lists listing templates for one visible store/channel. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_load_business_policies ~57

Loads marketplace business policies for one visible store. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_load_order_addresses ~71

Loads available shipping addresses for an order resolved from visible order Reference. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
referencestring–Visible marketplace/order reference.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_load_order_progress ~69

Reads progress for an order resolved from visible order Reference. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
referencestring–Visible marketplace/order reference.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_load_shipping_options ~56

Loads marketplace shipping options for one visible store. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_make_default_template ~127

Marks a listing template as default for one visible store/channel. Requires HGRApi Header channel / ChannelOAuthId resolved internally, confirmed=true and impactConfirmed=true because templates can affect publishing flows.

NameTypeReqDescription
body–yesWAPI MakeDefaultRequest body: templateId.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_manually_dispatch_order_lines ~95

Marks orders resolved from visible order Reference as manually dispatched. Requires confirmed=true. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
referencestring–Visible marketplace/order reference.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_mark_order_lines_as_purchased ~151

Marks exact order lines as purchased in HGR. The MCP resolves current WAPI status and uses FixedOrderLine only for CompletedAutoOrderPending. Requires confirmed=true after showing the full HGRWeb warning. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after showing the full HGRWeb warning: do not use this unless already purchased; it only marks the order as purchased in HGR; Auto-Ordering is required for automatic supplier purchase/sh…
referencestring–Visible marketplace/order reference.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_mark_order_lines_fixed ~95

Marks orders resolved from visible order Reference as fixed/resolved. Requires confirmed=true. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
referencestring–Visible marketplace/order reference.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_pause_pending_to_review ~134

Moves one pending listing to manual review by its visible pending listing id. Requires confirmed=true. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
pendingListingIdinteger–Visible pending listing id, only for pending listings where HGRWeb shows this id.
productIdstring–Visible marketplace Product Id / primary id. Prefer this for active or terminated listings.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_ai_createtask ~237

Dedicated HGRApi tool for POST api/AI/CreateTask. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST create task operation in AI optimization task management. Use when: Use it when a client needs to run the create task operation for AI optimization task management. Input: rq: Data.CreateTaskRequest. Main fields: Action: AIActionType, AutoPublish: bool, Listings: int[], Settings: CreateTaskRequestSetting[]. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the create task operation. Search terms: ai createtask. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/AI/CreateTask request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_ai_getimageinfo ~199

Dedicated HGRApi tool for POST api/AI/GetImageInfo. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST get image info operation in AI optimization task management. Use when: Use it when a client needs to run the get image info operation for AI optimization task management. Input: rq: GetImageInfoRequest. Main fields: Ids: int[]. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the get image info operation. Search terms: ai getimageinfo. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/AI/GetImageInfo request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_ai_gettaskresult ~204

Dedicated HGRApi tool for POST api/AI/GetTaskResult. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST get task result operation in AI optimization task management. Use when: Use it when a client needs to run the get task result operation for AI optimization task management. Input: rq: GetTaskResultRequest. Main fields: TaskId: int, ListingId: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the get task result operation. Search terms: ai gettaskresult. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/AI/GetTaskResult request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_ai_publishnow ~249

Dedicated HGRApi tool for POST api/AI/PublishNow. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST publish now operation in AI optimization task management. Use when: Use it when a client needs to run the publish now operation for AI optimization task management. Input: rq: PublishNowRequest. Main fields: TaskId: int, ListingId: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the publish now operation. Search terms: ai publishnow. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/AI/PublishNow request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_analytics_addwork ~218

Dedicated HGRApi tool for POST api/Analytics/AddWork. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST add work operation in current-channel watcher analytics. Use when: Use it when a client needs to run the add work operation for current-channel watcher analytics. Input: rq: AddWorkRequest. Main fields: Ids: int[]. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the add work operation. Search terms: analytics addwork. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Analytics/AddWork request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_catalog_getproducts ~579

Dedicated HGRApi tool for POST api/Catalog/GetProducts. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides supplier candidates for publication. ownerAgent: catalog-sources. Opening the catalog returns stored recommendations; explicit web, AI chat and MCP searches discover products through a deep internet search that may take several minutes. Use when: Use for catalog/source candidate discovery, not existing store inventory, importing store products, stock checks or ranking active listings. AI chat and MCP may search and apply the documented catalog filters, including themes, seasons and occasions such as Mother's Day gifts. Warn the user in their language before starting that a deep internet search may take several minutes; do not require confirmation for this read-only search. Input: CatalogProductsRequest. Header channel identifies the selected store and country. Search=false or omitted returns all type-0 country recommendations; SessionId preserves random order. For explicit searches from the web, AI chat or MCP set Search=true. Search accepts SourceIds, PriceFrom/PriceTo, ProfitFrom/ProfitTo, Prime options, Criteria as only the human-written free-text product search prompt (not a literal title substring) and optional Tags (selected theme/category integer IDs, using the same IDs as AI Publisher orders). When SourceIds is omitted or empty, searches use up to four distinct eligible supplier domains with the highest priority for the store's country and channel; source ID ascending breaks priority ties. Explicit supplier inclusions or exclusions retain their existing behavior. Theme, category, trending and store exclusion filters remain separate from Criteria. When Criteria is empty, categories and seasonal themes are expanded into related product families before searching; a human-written Criteria skips this expansion. Trending remains a search requirement. Price/profit requirement…

NameTypeReqDescription
body–yesHGRApi POST /api/Catalog/GetProducts request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_catalog_submitcatalog ~362

Dedicated HGRApi tool for POST api/Catalog/SubmitCatalog. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Queues selected catalog candidates for publication or review. ownerAgent: publication. Use when: Use after selecting real candidates from Catalog/GetProducts. Not for discovering products, importing existing store inventory, or publishing ad-hoc URLs; use Listing/SaveBulkPublish for general URL publication. Input: CatalogSubmitRequest. Header channel is required. Each ProductsToList item contains the exact Url, Title, SubOrigin (CatalogSelection=1 or CatalogSearch=2) and optional PublishOn for individual scheduling. Optimization/review options and Origin remain supported. Legacy Id and DelaysMap remain accepted for existing first-steps clients. UserDevice is optional web telemetry; AI chat and MCP omit it. Output: Creates URL-based bulk jobs, records SubOrigin while preserving Origin=Catalog, and returns BatchId. Token/quota validation applies. Search terms: catalog submitcatalog. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally. Internal-only request fields are removed automatically before the HGRApi request is sent.

NameTypeReqDescription
body–yesHGRApi POST /api/Catalog/SubmitCatalog request body. Internal-only request fields are removed automatically.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_clearonevariation ~263

Dedicated HGRApi tool for POST api/ChannelListing/ClearOneVariation. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST clear one variation operation in published product creation and optimization. Use when: Use it when a client needs to run the clear one variation operation for published product creation and optimization. Input: rq: ClearVariationsRequest. Main fields: ChannelListingId: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the clear one variation operation. Search terms: channellisting clearonevariation. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/ClearOneVariation request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_clearvariations ~244

Dedicated HGRApi tool for POST api/ChannelListing/ClearVariations. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST clear variations operation in published product creation and optimization. Use when: Use it when a client needs to run the clear variations operation for published product creation and optimization. Input: Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the clear variations operation. Search terms: channellisting clearvariations. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/ClearVariations request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_getcategoriesbytext ~253

Dedicated HGRApi tool for POST api/ChannelListing/getCategoriesByText. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST get categories by text operation in published product creation and optimization. Use when: Use it when a client needs to run the get categories by text operation for published product creation and optimization. Input: [FromBody] rq: GetCategoriesByTextRequest. Main fields: Text: string. Header channel: current ChannelOAuthId. Output: Returns the categories whose name contains the text. When no category name contains it, returns suggested categories for the text: for eBay and TikTok stores the first one is the HGR suggestion for that text, followed by the marketplace suggestions. Search terms: channellisting getcategoriesbytext. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/getCategoriesByText request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_getcategoryspecifics ~281

Dedicated HGRApi tool for POST api/ChannelListing/GetCategorySpecifics. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Returns category field definitions and populated values for manual product preparation. ownerAgent: publication. Use when: Use when the manual product form needs fields for its selected category and supplier product data. Input: GetCategorySpecificsRequest: SourceId, Price, CategoryId, Title, Paragraphs, Features, TableValues. Header channel: current ChannelOAuthId. Admin: false. Output: response_data remains the category field collection. Admin or impersonated sessions additionally receive debug alongside response_data, with actual product inputs and returned definitions, restrictions and values. Missing initial values, internal filling decisions and browser-side changes are explicitly marked as unavailable, never inferred. A failed category-field request includes admin debug with its trace ID in the error response. Search terms: channellisting getcategoryspecifics. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/GetCategorySpecifics request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_getsuggestedcategories ~219

Dedicated HGRApi tool for POST api/ChannelListing/getSuggestedCategories. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST get suggested categories operation in published product creation and optimization. Use when: Use it when a client needs to run the get suggested categories operation for published product creation and optimization. Input: [FromBody] rq: Request.GetSuggestedCategoriesRequest. Main fields: Url: string, Text: string. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the get suggested categories operation. Search terms: channellisting getsuggestedcategories. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/getSuggestedCategories request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_getsuggestedtitles ~210

Dedicated HGRApi tool for POST api/ChannelListing/GetSuggestedTitles. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST get suggested titles operation in published product creation and optimization. Use when: Use it when a client needs to run the get suggested titles operation for published product creation and optimization. Input: [FromBody] request: SuggestedTitles. Main fields: CategoryId: int, Product: SourceProduct. Output: Returns the result or applies the effect of the get suggested titles operation. Search terms: channellisting getsuggestedtitles. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/GetSuggestedTitles request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Hustle Got Real MCP server?

Hustle Got Real is a hosted endpoint at https://mcp.hustlegotreal.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.hustlegotreal.com

# add to Claude Code
claude mcp add --transport http com-hustlegotreal-mcp 'https://mcp.hustlegotreal.com/'
Common questions

What is the Hustle Got Real MCP server?

Hustle Got Real is an MCP server listed in the public MCP registry as com.hustlegotreal/mcp. Dropshipping for eBay, Amazon and Shopify: products, listings, prices, stock, orders and analytics. This page covers its hosted endpoint (https://mcp.hustlegotreal.com/).

Is the Hustle Got Real MCP server safe to use?

Hustle Got Real scores 57 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Hustle Got Real MCP server expose?

Hustle Got Real exposes 172 tools: hgr_get_authenticated_user, hgr_list_channels, hgr_get_subscription_summary, hgr_get_active_listings, hgr_get_pending_listings, and 167 more. Their descriptions and schemas cost roughly 31,732 tokens of context every time the server is loaded.

Does the Hustle Got Real MCP server require authentication?

No. We connected to Hustle Got Real without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Hustle Got Real MCP server still maintained?

Hustle Got Real is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Hustle Got Real MCP server?

VerifyMCP ran 13 checks on Hustle Got Real, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.