MyClawn Desktop
REMOTE · WWW.MYCLAWN.COM · SCANNED SEP 20
Hand jobs to an always-on cloud desktop with a real browser, saved logins and its own email.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 & 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.
How do I install the MyClawn Desktop MCP server?
MyClawn Desktop is a hosted endpoint at https://www.myclawn.com/mcp/desktop, 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 · www.myclawn.com
claude mcp add --transport http com-myclawn-desktop 'https://www.myclawn.com/mcp/desktop'
{
"mcpServers": {
"com-myclawn-desktop": {
"url": "https://www.myclawn.com/mcp/desktop"
}
}
} {
"servers": {
"com-myclawn-desktop": {
"type": "http",
"url": "https://www.myclawn.com/mcp/desktop"
}
}
} [mcp_servers.com-myclawn-desktop] url = "https://www.myclawn.com/mcp/desktop"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-myclawn-desktop": {
"type": "remote",
"url": "https://www.myclawn.com/mcp/desktop",
"enabled": true
}
}
} openclaw mcp add com-myclawn-desktop --url 'https://www.myclawn.com/mcp/desktop' --transport streamable-http
mcp_servers:
com-myclawn-desktop:
url: "https://www.myclawn.com/mcp/desktop" {
"McpServers": {
"com-myclawn-desktop": {
"Transport": "http",
"Url": "https://www.myclawn.com/mcp/desktop"
}
}
} assistant mcp add com-myclawn-desktop -t streamable-http -u 'https://www.myclawn.com/mcp/desktop'
{
"mcpServers": {
"com-myclawn-desktop": {
"type": "http",
"url": "https://www.myclawn.com/mcp/desktop"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 36
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 20 Sept 2026 · Probed https://www.myclawn.com/mcp/desktop
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=myclawn.com | CN=YE1,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 53d4cbe0ed6a8fbc68ba6844321b25f3f6c |
| SANs: *.myclawn.com, myclawn.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.myclawn.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| myclawn.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.myclawn.com/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.myclawn.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.myclawn.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://www.myclawn.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.myclawn.com/mcp/desktop | Auth required | 401 | |
| http (plaintext) | http://www.myclawn.com/mcp/desktop | HTTPS enforced | 308 | https://www.myclawn.com/mcp/desktop |
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.
What is the MyClawn Desktop MCP server?
MyClawn Desktop is an MCP server listed in the public MCP registry as com.myclawn/desktop. Hand jobs to an always-on cloud desktop with a real browser, saved logins and its own email. This page covers its hosted endpoint (https://www.myclawn.com/mcp/desktop).
Is the MyClawn Desktop MCP server safe to use?
MyClawn Desktop scores 36 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 MyClawn Desktop MCP server require authentication?
Yes. MyClawn Desktop 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 MyClawn Desktop MCP server still maintained?
MyClawn Desktop is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.