ConnectorReport
REMOTE · CONNECTORREPORT.COM
Hands-on test results for 560+ remote MCP connectors: does it work, how to sign in, what breaks.
Available components
Last scanned (1 hour ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 284 tokens (~56/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +55
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.57 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 28 Oct 26 −52
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://connectorreport.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.connectorreport.com | CN=YR1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 6be224f203d899ea4e0fc3b0ae7e4916b32 |
| SANs: *.connectorreport.com, connectorreport.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of connectorreport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| connectorreport.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://connectorreport.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://connectorreport.com/api/mcp | HTTPS enforced | 308 | https://connectorreport.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_connector_status Check connector status ~57
Current Connector Weather (Clear, Cloudy or Stormy) for a connector by name, plus the last test date. Check this before relying on a connector.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Connector name or slug, for example "Slack" |
No output schema declared.
No examples provided.
compare_connectors Compare connectors ~33
Side-by-side hands-on results for 2 to 10 connector slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | – |
No output schema declared.
No examples provided.
get_connector_report Get a connector report ~68
Full hands-on test report for one connector by slug: status, pass rate, tested date, each task, gotchas, fix recipes and page URL.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Connector slug, for example "notion" or "github". Use list_connectors to find slugs. |
No output schema declared.
No examples provided.
list_connectors List tested connectors ~86
List every MCP connector ConnectorReport has tested hands-on, with status, pass rate and last test date. Optional category: ai-ml, cloud, developer-tools, docs, other, productivity, public-data, search, travel.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | One of: ai-ml, cloud, developer-tools, docs, other, productivity, public-data, search, travel |
No output schema declared.
No examples provided.
search_reports Search reports ~40
Full-text search across tested connectors, task details, run notes and gotchas, for example "OAuth" or "token".
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the ConnectorReport MCP server?
ConnectorReport is a hosted endpoint at https://connectorreport.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · connectorreport.com
claude mcp add --transport http com-connectorreport-connectorreport 'https://connectorreport.com/api/mcp'
What is the ConnectorReport MCP server?
ConnectorReport is an MCP server listed in the public MCP registry as com.connectorreport/connectorreport. Hands-on test results for 560+ remote MCP connectors: does it work, how to sign in, what breaks. This page covers its hosted endpoint (https://connectorreport.com/api/mcp).
Is the ConnectorReport MCP server safe to use?
ConnectorReport scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ConnectorReport MCP server expose?
ConnectorReport exposes 5 tools: list_connectors, get_connector_report, check_connector_status, compare_connectors, search_reports. Their descriptions and schemas cost roughly 284 tokens of context every time the server is loaded.
Does the ConnectorReport MCP server require authentication?
No. We connected to ConnectorReport without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ConnectorReport MCP server still maintained?
ConnectorReport is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.