How musedirectory.ai checks Muse connectors

What gets listed

Any connector that works in Meta Muse: the connectors Meta ships, connectors approved into the Muse directory, and remote MCP servers that Muse can connect to by URL. Local-only servers that need to run on your own machine are out of scope.

How health checks work

Every 15 minutes a scheduled job sends each listed endpoint a real Model Context Protocol initialize request, with no credentials, and records the answer and the time it took.

Live: the endpoint answered with success, or with 401/403 because it requires sign-in (normal for OAuth connectors). Shown as "Live, sign-in" in that case.
Degraded: it answered, but with an error, or took longer than 5 seconds.
Down: no answer within 8 seconds.

Open endpoints are also asked for their tool list, so the tool catalog on each record is what the server actually exposes, refreshed on every check.

Muse status

Built by Meta: shipped as part of Muse.
In Muse directory: reviewed and approved by Meta.
Submitted to Muse: the builder says it is under Meta's review.
Connect by URL: not in the Muse directory; connect it by giving Muse the endpoint.

Muse status is reported by builders and public sources. Health is measured by us. We never let one stand in for the other.

Owner-submitted vs found in the wild

Connectors a builder submitted carry their details as given. Connectors we found in public sources say so, and their builders can claim them to correct the record.

Disclosure

musedirectory.ai is independent and not affiliated with Meta. Some listings are built by the people who run this directory. Those are marked publisher-operated on the list and carry a disclosure on their record, and they are checked by the same job as everything else.

For agents