Quick follow-up to our `list_members` testing. We went quite a bit deeper after the latest fix and found two separate things. 𝟭) 𝗧𝗵𝗲 𝗰𝘂𝗿𝗿𝗲𝗻𝘁 𝗺𝗲𝗺𝗯𝗲𝗿-𝗹𝗶𝘀𝘁 𝗳𝗶𝘅 𝘀𝘁𝗶𝗹𝗹 𝗶𝘀𝗻'𝘁 𝗿𝗲𝗹𝗶𝗮𝗯𝗹𝗲 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 - Hosted Catknows still gets a 403 on Skoolers, where I'm only a regular member. - On another regular-member community, pagination starts repeating page 1 after member 30. So a request for 65 can appear successful while actually returning duplicated members. - At the same time, Skool's own authenticated browser requests repeatedly return 200 with `t=active`, including sorting, filtering and page 2. So `t=active` itself doesn't appear to be the universal trigger; the difference looks more request/context-specific. 𝟮) 𝗦𝗸𝗼𝗼𝗹'𝘀 𝗠𝗲𝗺𝗯𝗲𝗿𝘀 𝘀𝗲𝗮𝗿𝗰𝗵 𝗲𝘅𝗽𝗼𝘀𝗲𝘀 𝗮 𝗹𝗼𝘁 𝗺𝗼𝗿𝗲 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹𝗶𝘁𝘆 𝘁𝗵𝗮𝗻 𝗖𝗮𝘁𝗸𝗻𝗼𝘄𝘀 𝗰𝘂𝗿𝗿𝗲𝗻𝘁𝗹𝘆 𝗱𝗼𝗲𝘀 We mapped and verified the actual `members.json` parameters for: - lifecycle: active / cancelling / churned / banned - sorting: newest / last active / most points - status: admins / online - billing: free trials / monthly / annual / 1-time / free - tiers: Standard / Premium / VIP - course access, including multiple courses - mixed filters - page-number pagination We also verified that the Boolean behaviour differs by filter family: for example, tiers behave as OR, while multiple course IDs and separate status/billing flags behave as AND. The attached PDF contains the full reproduction, verified query grammar, pagination safeguards, suggested MCP schema, and acceptance tests so the implementation can be worked from directly. 🐾