WhenIsBins

Last 30 days

Uptime

100%

Response time

146 ms typical, 155 ms slowest 5%

Last check

4 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "whenisbins": {
      "type": "http",
      "url": "https://whenisbins.com/mcp"
    }
  }
}

4 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. collections[].containers lists each distinct container group once: options are alternatives separated by 'or', each with a condition when the council sta

• 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. collections[].containers lists each distinct container group once: options are a

Security scan

• Unusually long description in tool:get_collections
  get_collections Step 2. Looks up collection dates for the one property the user …

Recent checks