# WhenIsBins Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## WhenIsBins

Check UK household bin collection dates by postcode and address

- Record: https://musedirectory.ai/connector/whenisbins
- Category: Lifestyle
- Developer: whenisbins.com (https://whenisbins.com/v1/guide)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 194ms, checked 2026-09-28T08:46:03Z
- Endpoint: https://whenisbins.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T21:40:44Z)
- Source: Found in the official MCP Registry (com.whenisbins/bin-collections) https://registry.modelcontextprotocol.io/v0/servers?search=com.whenisbins%2Fbin-collections

Looks up bin collection schedules for UK properties using council data. Finds your address by postcode, then retrieves collection dates and what goes in each container. Free and anonymous.

Example request: "When is my bin collection this week?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use WhenIsBins to help me. It is a free service with an MCP server at https://whenisbins.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- find_addresses: Step 1. Lists the properties the council knows at a UK postcode and names the input get_collections needs (required_input). Show the user the candidates and let them choose, unless what they told you matches exactly one candidate. Rules: never guess or choose a property for the u
- get_collections: Step 2. Looks up collection dates for the one property the user chose. Send the postcode and the field find_addresses named in required_input (normally property_id, from the chosen candidate). Waits up to about 45 seconds. status is done, partial (provisional dates), still_workin
- check_lookup: Reads a lookup that get_collections started, by its lookup_id. Waits up to about 30 seconds. Same statuses as get_collections. What goes in the containers is summarised in collections[].contents when present. If contents is null, say the council has not published contents in the 
- get_schedule: For a repeat check. Reads the stored schedule for a property_id that an earlier done lookup returned. It starts no new lookup; if it reports no_schedule, run find_addresses and get_collections again. What goes in the containers is summarised in collections[].contents when present

Screening checks:
- MCP handshake: pass (Answered in 217ms)
- Domain against threat feeds (Cloudflare security DNS): pass (whenisbins.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (4 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 49 days ago)
- AI review of purpose and tool behavior: pass (No concerns)