COROS
REMOTE · MCPUS.COROS.COM · 3 COMPONENTS
Access COROS activity, training and health data, and manage training plans and workouts.
Available components
Last scanned (16 hours ago)
Scores higher than 14% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (4)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Oct 26 31
First indexed and scored.
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://mcpus.coros.com/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.coros.com | CN=GlobalSign GCC R46 DV TLS CA 2025,O=GlobalSign nv-sa,C=BE | 15 Sept 2026 | 2 Apr 2027 | RSA 2048 | SHA256-RSA | 248cca605f36da7eebe6f518 |
| SANs: *.coros.com, coros.com | ||||||
| CN=GlobalSign GCC R46 DV TLS CA 2025,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root R46,O=GlobalSign nv-sa,C=BE | 17 Sept 2025 | 23 Jun 2029 | RSA 2048 | SHA256-RSA | 8443588121db5ab28499ffae80670ba4 |
| CN=GlobalSign Root R46,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign,OU=GlobalSign Root CA - R3,O=GlobalSign | 20 Nov 2019 | 18 Mar 2029 | RSA 4096 | SHA384-RSA | 75a8bad878f8af305f72dd1c1140df3a |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcpus.coros.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| coros.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcpus.coros.com/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://mcpus.coros.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| www-authenticate | Bearer resource_metadata="https://mcpus.coros.com/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://mcpus.coros.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcpus.coros.com/mcp |
| Authorisation server | https://mcpus.coros.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcpus.coros.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcpus.coros.com/mcp | Inconclusive | 401 |
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 →
No tool schema has been captured from this endpoint yet.
How do I install the COROS MCP server?
COROS is a hosted endpoint at https://mcpus.coros.com/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 · mcpus.coros.com
claude mcp add --transport http coroslab-coros-mcp 'https://mcpus.coros.com/mcp'
What is the COROS MCP server?
COROS is an MCP server listed in the public MCP registry as io.github.coroslab/coros-mcp. Access COROS activity, training and health data, and manage training plans and workouts. This page covers its hosted endpoint (https://mcpus.coros.com/mcp).
Is the COROS MCP server safe to use?
COROS scores 31 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.
Does the COROS MCP server require authentication?
Yes. COROS asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the COROS MCP server still maintained?
COROS 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.
What did VerifyMCP test on the COROS MCP server?
VerifyMCP ran 4 checks on COROS, covering TLS certificate, Authorization, HSTS header and DNSSEC. 7 items could not be completed, a gap on our side rather than a finding about COROS: HTTPS, Transport, Schema quality, Stability and 3 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.