Link to community directories in the README

[rickcys]

Hi. The README currently points to the official MCP Registry for browsing servers. I run DReview (https://dreview.co), a free community directory (install configs per-client, categorized, no login required to browse) would a maintainer be open to a short "community directories" mention alongside the registry link? No worries if that's out of scope for this repo. I just wanted to ask directly rather than open an unsolicited PR.

[Ecocitizenz]

I'd support community-directory visibility, with one boundary made explicit:

discovery is not authority.

Community directories can add substantial value through categorisation, install configuration, comparison, search and ecosystem visibility. But a directory entry should not automatically be interpreted by clients or relying parties as proof that the listed endpoint, operator, version or current state remains authoritative.

As the ecosystem grows, I think the clean separation is:

1. Directory → "this MCP exists / can be discovered"
2. Registry/package metadata → "this artefact was published"
3. Runtime observation → "something responded here at time T"
4. Resolver/evidence layer → "this operator currently stands behind this identity/state/evidence"

That separation lets directories become richer without forcing them to become certification or trust authorities.

It is also the reason we're building ECZ-ID as a resolver-first identity and evidence layer rather than another MCP directory. The layers should compose.

— Adam Al-Zayed
Founder | EcoCitizenz Ltd
ECZ-ID — MCP & Agent Trust
https://mcp.ecocitizenz.com/
Resolver: https://resolver.ecocitizenz.org/passport/ECZ-GB-RBS1NW