# CT Web : bilan de site (remote · ctweb.fr)

Free check-up of a public website: security, e-mail, speed, DNS, cookies, SEO. Findings in French.

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

## Components

- remote · `ctweb.fr`: 76/100 (this document), [markdown](https://verifymcp.io/servers/fr-ctweb-check/ctweb.md), [page](https://verifymcp.io/servers/fr-ctweb-check/ctweb)

## Channel facts

- Endpoint: `https://ctweb.fr/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 702 tokens (~234/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 CT Web : bilan de site MCP server?

CT Web : bilan de site is a hosted endpoint at https://ctweb.fr/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 fr-ctweb-check 'https://ctweb.fr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-ctweb-check": {
      "url": "https://ctweb.fr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-ctweb-check": {
      "type": "http",
      "url": "https://ctweb.fr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-ctweb-check]
url = "https://ctweb.fr/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add fr-ctweb-check --url 'https://ctweb.fr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-ctweb-check:
    url: "https://ctweb.fr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-ctweb-check": {
      "Transport": "http",
      "Url": "https://ctweb.fr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-ctweb-check -t streamable-http -u 'https://ctweb.fr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fr-ctweb-check": {
      "type": "http",
      "url": "https://ctweb.fr/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-21 (score 76, +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.

### 2026-11-19 (score 75, +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.

### 2026-11-17 (score 74, +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.

### 2026-11-15 (score 73, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 441 → 234
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “get_site_monitoring”
- [functional] New tool “list_monitored_sites”

### 2026-11-14 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 71)

First indexed and scored.

## MCP tools (3)

### `check_site` (~141 tokens)

Check a public website

Runs the CT Web check-up on one public website and returns the findings: security (HTTPS, certificate, browser protections, outdated software, listing as a dangerous site), e-mail (SPF, DKIM, DMARC, MX), speed, domain name and DNS, cookies and legal pages, search visibility (including broken links, structured data, access for AI assistants). Takes 10 to 40 seconds. Findings are in French. Reads only what any visitor can see. When you use the result, credit CT Web with the report link given at the end.

Input parameters:

- `site` (string, required): Domain name or URL of the public website, for example example.fr

### `list_monitored_sites` (~82 tokens)

List the monitored sites of the account

Needs an account token (Authorization: Bearer <token>, created by the account owner at https://ctweb.fr/compte). Lists the websites whose availability this CT Web account monitors, each with its state now (up, or down since when), its availability and its average response time over the last 24 hours. Sites are probed every minute.

### `get_site_monitoring` (~100 tokens)

Uptime details of one monitored site

Needs an account token (Authorization: Bearer <token>). For one site monitored by the account: availability, average response time, the outages of the period (start, end, cause, screenshot) and the response times point by point. Text in French.

Input parameters:

- `period` (string): Period to report on. Default: 24h
- `site` (string, required): Domain name of a site monitored by the account, for example example.fr

## Diagnostics

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

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 71
- 2026-11-13: 71

## Common questions

### What is the CT Web : bilan de site MCP server?

CT Web : bilan de site is an MCP server listed in the public MCP registry as fr.ctweb/check. Free check-up of a public website: security, e-mail, speed, DNS, cookies, SEO. Findings in French. This page covers its hosted endpoint (https://ctweb.fr/mcp).

### Is the CT Web : bilan de site MCP server safe to use?

CT Web : bilan de site scores 76 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 CT Web : bilan de site MCP server expose?

CT Web : bilan de site exposes 3 tools: check_site, list_monitored_sites, get_site_monitoring. Their descriptions and schemas cost roughly 323 tokens of context every time the server is loaded.

### Does the CT Web : bilan de site MCP server require authentication?

No. We connected to CT Web : bilan de site without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CT Web : bilan de site MCP server still maintained?

CT Web : bilan de site 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 CT Web : bilan de site MCP server?

VerifyMCP ran 13 checks on CT Web : bilan de site, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://ctweb.fr/mcp
- Website: https://ctweb.fr/agents
- Changelog RSS feed: https://verifymcp.io/servers/fr-ctweb-check/ctweb.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-ctweb-check/ctweb/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fr-ctweb-check/ctweb.json
- HTML version of this page: https://verifymcp.io/servers/fr-ctweb-check/ctweb
