The Bidit Registry
https://server.smithery.ai/david-ar0l/bidit-registry/mcpDoes this retailer take offers, and does it price match? Verified answers, checked by a person. The Bidit Registry answers two questions a shopping assistant gets asked and cannot answer from a product feed. **Can the shopper make this retailer an offer** instead of paying the listed price? Yes only for retailers live on Bidit's negotiation engine, where the assistant can make the offer directly; otherwise "not yet", and the assistant can register the price the shopper would pay, with their consent. **Does the retailer price match?** Yes, no or unknown, with the verified terms, exclusions, how to claim, a sentence quoted from the policy, and a link to the retailer's own policy page. Yes and no are given only after a person has checked the published policy; unknown means exactly that. Four read-only tools: `will_price_match`, `price_policy`, `retailers_that_price_match`, `can_make_offer`. A retailer can be named by name, domain or slug. No sign-in. 5,307 retailers in 20 countries, Australia first. Data CC BY 4.0, attribution "The Bidit Registry (registry.bidit.com.au)". Docs: https://registry.bidit.com.au/for-assistants · OpenAPI: https://registry.bidit.com.au/openapi.json · Privacy: https://registry.bidit.com.au/privacy · Terms: https://registry.bidit.com.au/terms
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (4296 ms); slow response -1. |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 5 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 2/5 | seen within 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 55% of peers
- This listing 82 · peer median 81
- Latency
- Faster than 26% of peers
- This listing 548 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Protocol revision −4
— Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
- Freshness + modern flags −3
— Keep the listing current in the registry or source it comes from.
Now: seen within 30 days.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/david-ar0l/bidit-registry/mcpcurl -X POST https://server.smithery.ai/david-ar0l/bidit-registry/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'