# 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.

- Trust score: 75/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `registry.bidit.com.au`: 75/100 (this document), [markdown](https://verifymcp.io/servers/au-com-bidit-registry/api-mcp.md), [page](https://verifymcp.io/servers/au-com-bidit-registry/api-mcp)

## Channel facts

- Endpoint: `https://registry.bidit.com.au/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http au-com-bidit-registry 'https://registry.bidit.com.au/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "au-com-bidit-registry": {
      "url": "https://registry.bidit.com.au/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "au-com-bidit-registry": {
      "type": "http",
      "url": "https://registry.bidit.com.au/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.au-com-bidit-registry]
url = "https://registry.bidit.com.au/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "au-com-bidit-registry": {
      "type": "remote",
      "url": "https://registry.bidit.com.au/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add au-com-bidit-registry --url 'https://registry.bidit.com.au/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  au-com-bidit-registry:
    url: "https://registry.bidit.com.au/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "au-com-bidit-registry": {
      "Transport": "http",
      "Url": "https://registry.bidit.com.au/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add au-com-bidit-registry -t streamable-http -u 'https://registry.bidit.com.au/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "au-com-bidit-registry": {
      "type": "http",
      "url": "https://registry.bidit.com.au/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 138 → 180
- [functional] New tool “find_products”

### 2026-10-20 (score 75, +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.

### 2026-10-18 (score 74, +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.

### 2026-10-16 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 72)

First indexed and scored.

## MCP tools (5)

### `will_price_match` (~165 tokens)

Will this retailer price match?

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.

Input parameters:

- `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, required): Retailer name, domain or Registry slug, e.g. 'JB Hi-Fi', 'jbhifi.com.au' or 'jbhifi'

### `price_policy` (~72 tokens)

A retailer's verified price policy

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.

Input parameters:

- `retailer` (string, required): Retailer name, domain or Registry slug

### `retailers_that_price_match` (~101 tokens)

Retailers with a verified price-match policy

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.

Input parameters:

- `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.

### `can_make_offer` (~93 tokens)

Can a shopper make this retailer an offer?

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.

Input parameters:

- `retailer` (string, required): Retailer name, domain or Registry slug

### `find_products` (~305 tokens)

Find products at retailers that take offers or price match

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.

Input parameters:

- `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, required): What the shopper wants, in a few words, e.g. 'linen shirt', 'Dyson V15', 'gold hoop earrings'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/au-com-bidit-registry/api-mcp#diagnostics

## Score history

- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://registry.bidit.com.au/api/mcp
- Repository: https://github.com/Bidit-AU/bidit-registry
- Website: https://registry.bidit.com.au/for-assistants
- Changelog RSS feed: https://verifymcp.io/servers/au-com-bidit-registry/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/au-com-bidit-registry/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/au-com-bidit-registry/api-mcp