A connector is not working?
Compare the public observation with what you see in your assistant and get concrete next checks.
Find what to check →Find the right MCP. Know your next step.
Search by need, check a known server, then configure it in your assistant.
Free search and public checks · No account needed
A name or need opens the catalog. An HTTPS URL starts a check.
What would you like to do?
See all uses →From a need to your assistant
- Find
Choose a use or search by connector name.
- Check
Read the public result: address, MCP protocol and visible tools.
- Configure
Follow the guide for your assistant, then complete sign-in there.
A public check does not test your personal sign-in or execute tools.
Want automatic monitoring?
With Watch, monitor the connectors you select and receive email alerts when a confirmed incident or public change is detected.
Discover Watch →A concrete example
What can an MCP change reveal?
New required parameters, removed models: see observations and useful next checks across 10 connectors.
What does a check report look like?
Or try an example:
Linear
Connection requiredLast checked
View reportA public check verifies only the server's public response and catalog. It does not verify your personal connection or execute private tools.
GitHub
Connection requiredLast checked
View reportLinear
Connection requiredLast checked
View reportExa
Unknown · Transport onlySearch the web from your assistant.
Last checked
View reportFind your connectors again next time
Create a free account
A free account keeps your list and selected assistant. Automatic monitoring is part of Watch.
How a check works
Type a connector name, a capability such as search web, or paste a public HTTPS endpoint. Search or paste a public MCP. See whether it answers, which tools are public, and how to add it to your assistant. Talandor never asks for credentials and never calls tools. Catalog: 30683 public HTTPS endpoints. How it works