au.com.bidit/registry
REMOTE · REGISTRY.BIDIT.COM.AU
Does this retailer take offers, and does it price match? Verified answers, checked by a person.
Available components
Last scanned (8 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 24 Oct 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 903 tokens (~180/item across 5 items; 5 tools + 0 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 Management30
- Stability observed for 9 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 23 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 138 → 180 ▼ functional
- New tool “find_products” functional
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 72
First indexed and scored.
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 24 Oct 2026 · Probed https://registry.bidit.com.au/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=registry.bidit.com.au | CN=YR2,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 6d4ffe5a876d4c4ba164e1811d1dca03544 |
| SANs: registry.bidit.com.au | ||||||
| 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 registry.bidit.com.au. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| au. | present | 26642 | 8 | Verified |
| com.au. | present | 14185 | 8 | Verified |
| bidit.com.au. | absent | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://registry.bidit.com.au/api/mcp | Verified | 200 | |
| http (plaintext) | http://registry.bidit.com.au/api/mcp | HTTPS enforced | 308 | https://registry.bidit.com.au/api/mcp |
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 →
can_make_offer Can a shopper make this retailer an offer? ~93
Returns whether a shopper can make this retailer an offer instead of paying the listed price. answer is yes (the retailer accepts offers through Bidit now; offers_url is where) or not_yet (the retailer does not; register_interest_url and consent_text describe how a shopper can register the price they would pay). There is no third state.
| Name | Type | Req | Description |
|---|---|---|---|
| retailer | string | yes | Retailer name, domain or Registry slug |
No output schema declared.
No examples provided.
find_products Find products at retailers that take offers or price match ~305
Searches the products the Registry has pulled from its retailers' own catalogues (Shopify stores, up to 500 products each) and returns each hit with its price, its page at the store, when it was last seen, and the store's verified facts: whether it accepts offers (true only when the store is in the engine's live list) and whether it price matches (yes or no only after a person verified the policy; unknown otherwise). Filter by country, a ceiling on price, only stores that take offers, or only stores with a verified price-match policy. Prices and availability are as of last_seen_at; confirm on the product page before quoting. Not every retailer's products are listed, so an empty result is not a no.
| Name | Type | Req | Description |
|---|---|---|---|
| accepts_offers | boolean | – | true: only stores where a shopper can make an offer. Optional. |
| country | string | – | ISO 3166 two-letter country code, e.g. AU. Optional. |
| limit | integer | – | How many products to return, 1 to 100. Default 20. |
| price_match | boolean | – | true: only stores with a verified price-match policy. Optional. |
| price_max | number | – | Only products whose lowest price is at or under this, in the store's currency. Optional. |
| query | string | yes | What the shopper wants, in a few words, e.g. 'linen shirt', 'Dyson V15', 'gold hoop earrings' |
No output schema declared.
No examples provided.
price_policy A retailer's verified price policy ~72
Returns everything the Registry has verified about how a retailer handles price: whether it takes offers through Bidit, whether it price matches and on what terms, how it runs promotions, and its clearance page. Fields are null where nothing has been verified.
| Name | Type | Req | Description |
|---|---|---|---|
| retailer | string | yes | Retailer name, domain or Registry slug |
No output schema declared.
No examples provided.
retailers_that_price_match Retailers with a verified price-match policy ~101
Returns the retailers whose price-match policy a person has verified, optionally filtered by category and country, each with its terms and policy page. A retailer absent from the list is unverified, not a no.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Registry category, e.g. electronics, furniture, outdoor, hardware, sports, jewellery, beauty. Optional. |
| country | string | – | ISO 3166 two-letter country code, e.g. AU. Optional. |
No output schema declared.
No examples provided.
will_price_match Will this retailer price match? ~165
Returns whether a retailer publishes a policy of matching a competitor's lower price, with the verified terms, exclusions, how to claim, a sentence quoted from the policy and the policy page. answer is yes (a person has verified the published policy), no (a person looked and found none) or unknown (not verified). Whether a particular competitor price qualifies depends on the terms returned.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor_price | number | – | The lower price the shopper has found, in the retailer's currency. Optional; echoed back with the terms. |
| product | string | – | What the shopper wants to buy. Optional. |
| retailer | string | yes | Retailer name, domain or Registry slug, e.g. 'JB Hi-Fi', 'jbhifi.com.au' or 'jbhifi' |
No output schema declared.
No examples provided.
How do I install the au.com.bidit/registry MCP server?
au.com.bidit/registry is a hosted endpoint at https://registry.bidit.com.au/api/mcp, 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 · registry.bidit.com.au
claude mcp add --transport http au-com-bidit-registry 'https://registry.bidit.com.au/api/mcp'
What is the au.com.bidit/registry MCP server?
au.com.bidit/registry is an MCP server listed in the public MCP registry as au.com.bidit/registry. Does this retailer take offers, and does it price match? Verified answers, checked by a person. This page covers its hosted endpoint (https://registry.bidit.com.au/api/mcp).
Is the au.com.bidit/registry MCP server safe to use?
au.com.bidit/registry scores 75 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 au.com.bidit/registry MCP server expose?
au.com.bidit/registry exposes 5 tools: will_price_match, price_policy, retailers_that_price_match, can_make_offer, find_products. Their descriptions and schemas cost roughly 736 tokens of context every time the server is loaded.
Does the au.com.bidit/registry MCP server require authentication?
No. We connected to au.com.bidit/registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the au.com.bidit/registry MCP server still maintained?
au.com.bidit/registry is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.