Archived listing / no verified MCP endpoint/Development

ConnectorReport listing

No MCP endpoint is published. This listing is retained for reference.

ConnectorReport was a read-only directory of dated, hands-on test results for remote MCP servers, covering pass rate, sign-in method, gotchas, and fix recipes. Its endpoint returned HTTP 503 with DEPLOYMENT_PAUSED when checked on 2026-11-16, and the provider page would not load, so none of its claims can be re-verified today. The listing is kept for reference only.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.
No MCP endpoint Reviewed 2026-11-16
About

Where it fits

No one right now: the deployment is paused. Check back or use a working test source.

  • Check whether the provider deployment has been restored.
  • Treat the old pass-rate and sign-in claims as unverified.
  • Do not attempt a connection until the service returns.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.