Thanks for looking. Here is what helps and what does not.
Bug reports are genuinely useful, and the more concrete the better: the command you ran, what you expected, what happened instead. If it involves a specific post, account or file, say which.
Feature requests are welcome too, with one caveat worth setting out. The tool list is deliberately small. Every tool is sent to the model on every turn, so each one costs context whether it gets used or not, and a server with four hundred tools is worse than one with forty because the model picks badly from four hundred. Most additions get declined for that reason rather than because the idea is bad.
This is one of a family of servers that are deliberately identical to each other: the same section order, the same safety model, the same shape of tool description, the same voice. A change usually has to land the same way in several of them, so reviewing a patch into that takes longer than writing it.
That is a property of how these are maintained, not a judgement on the patch. If something is broken, an issue gets it fixed faster than a pull request will.
Please do not open a public issue for a vulnerability. Use the private reporting path in SECURITY.md, which also sets out what the server can reach and what it holds.