# SafeToClone (remote · safetoclone.com)

Safety grade (A to F) for any public GitHub repo, in plain English, before you install it.

- Trust score: 60/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `safetoclone.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/com-safetoclone-safetoclone/safetoclone.md), [page](https://verifymcp.io/servers/com-safetoclone-safetoclone/safetoclone)

## Channel facts

- Endpoint: `https://safetoclone.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 288 tokens (~144/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 16 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SafeToClone MCP server?

SafeToClone is a hosted endpoint at https://safetoclone.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.

### Claude

```bash
claude mcp add --transport http com-safetoclone-safetoclone 'https://safetoclone.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-safetoclone-safetoclone": {
      "url": "https://safetoclone.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-safetoclone-safetoclone": {
      "type": "http",
      "url": "https://safetoclone.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-safetoclone-safetoclone]
url = "https://safetoclone.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-safetoclone-safetoclone": {
      "type": "remote",
      "url": "https://safetoclone.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-safetoclone-safetoclone --url 'https://safetoclone.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-safetoclone-safetoclone:
    url: "https://safetoclone.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-safetoclone-safetoclone": {
      "Transport": "http",
      "Url": "https://safetoclone.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-safetoclone-safetoclone -t streamable-http -u 'https://safetoclone.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-safetoclone-safetoclone": {
      "type": "http",
      "url": "https://safetoclone.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-15 (score 60, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-07 (score 60, −1)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 1.1.0
- [security regression] Tool “get_next_post” was removed
- [security regression] Tool “list_upcoming_posts” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 111 → 139

### 2026-11-06 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-05 (score 60)

First indexed and scored.

## MCP tools (2)

### `get_safety_scores` (~42 tokens)

Get the latest SafeToClone safety grades (A to F) for popular AI tools on GitHub. Use it to answer questions in comments or DMs.

### `check_repo` (~135 tokens)

Check whether a GitHub repo is safe before installing, cloning or running it. Call it whenever the user shares a GitHub link, or asks to install a tool, app, MCP server, Claude skill or plugin from GitHub. Works for any public repo. Returns an A to F grade, a one-sentence summary to tell the user, a recommendation (install, install_with_care, ask_first, only_if_trusted, do_not_install), the warning signs and a link to the full report.

Input parameters:

- `repo` (string, required): A GitHub link like https://github.com/owner/name, or just owner/name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-safetoclone-safetoclone/safetoclone#diagnostics

## Score history

- 2026-11-21: 60
- 2026-11-20: 60
- 2026-11-19: 60
- 2026-11-18: 60
- 2026-11-17: 60
- 2026-11-16: 60
- 2026-11-15: 60
- 2026-11-14: 60
- 2026-11-13: 60
- 2026-11-12: 60
- 2026-11-11: 60
- 2026-11-10: 60
- 2026-11-09: 60
- 2026-11-08: 60
- 2026-11-07: 60
- 2026-11-06: 61
- 2026-11-05: 60

## Common questions

### What is the SafeToClone MCP server?

SafeToClone is an MCP server listed in the public MCP registry as com.safetoclone/safetoclone. Safety grade (A to F) for any public GitHub repo, in plain English, before you install it. This page covers its hosted endpoint (https://safetoclone.com/mcp).

### Is the SafeToClone MCP server safe to use?

SafeToClone scores 60 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 SafeToClone MCP server expose?

SafeToClone exposes 2 tools: get_safety_scores, check_repo. Their descriptions and schemas cost roughly 177 tokens of context every time the server is loaded.

### Does the SafeToClone MCP server require authentication?

No. We connected to SafeToClone without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SafeToClone MCP server still maintained?

SafeToClone is still listed as active in the MCP registry. We last reached this channel on 21 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 SafeToClone MCP server?

VerifyMCP ran 11 checks on SafeToClone, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about SafeToClone: Authorization and HTTPS. 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.

## Links

- Remote endpoint: https://safetoclone.com/mcp
- Website: https://safetoclone.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-safetoclone-safetoclone/safetoclone.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-safetoclone-safetoclone/safetoclone/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-safetoclone-safetoclone/safetoclone.json
- HTML version of this page: https://verifymcp.io/servers/com-safetoclone-safetoclone/safetoclone
