MCP's default query parameter hallucination

AI-generated summary

In a support discussion titled “MCP’s default query parameter hallucination,” deviantintegral raises concerns that the MCP (likely a software tool or library) appears to have been developed with heavy AI assistance and may not have undergone sufficient human testing. They point out that the default query parameter order:latest-post seems to be a hallucinated value — not a real or valid parameter — and suggest the README may need updating to clarify this. Falco confirms the issue, noting that while latest-post appears in the documentation, the actual valid parameter in the filter route is latest. sam adds that the hallucinated parameter might be a bug introduced during AI-assisted development and encourages reporting it via a pull request if others encounter similar issues. The thread highlights potential risks of over-reliance on AI-generated code without proper validation, especially in documentation and default configurations.

While the MCP doesn’t have a stable release tagged, I’m suspicious it hasn’t been tested much by humans at all. In going through the default setup, I noticed that it recommends a default query parameter of order:latest-post which looks to be hallucinated. The MCP has clearly been written with significant AI tooling. Perhaps the README needs to be updated to be clear on what has been tested and what is still in progress?

latest-post is a valid parameter in the filter route:

What do you mean?

I think it may be a legit bug in the README… feel free to post a PR if you notice any other inaccuracies, thanks for bringing this up:

https://github.com/discourse/discourse-mcp/pull/18