# The Deploy Log (remote · deployedbyai.com)

AI deployments that shipped and are available now, each sourced to the publisher's own page.

- Trust score: 88/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `deployedbyai.com`: 88/100 (this document), [markdown](https://verifymcp.io/servers/com-deployedbyai-the-deploy-log/log-mcp.md), [page](https://verifymcp.io/servers/com-deployedbyai-the-deploy-log/log-mcp)

## Channel facts

- Endpoint: `https://deployedbyai.com/log/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-06.

- **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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 337 tokens (~112/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the The Deploy Log MCP server?

The Deploy Log is a hosted endpoint at https://deployedbyai.com/log/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-deployedbyai-the-deploy-log 'https://deployedbyai.com/log/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-deployedbyai-the-deploy-log": {
      "url": "https://deployedbyai.com/log/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-deployedbyai-the-deploy-log": {
      "type": "http",
      "url": "https://deployedbyai.com/log/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-deployedbyai-the-deploy-log]
url = "https://deployedbyai.com/log/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-deployedbyai-the-deploy-log --url 'https://deployedbyai.com/log/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-deployedbyai-the-deploy-log:
    url: "https://deployedbyai.com/log/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-deployedbyai-the-deploy-log": {
      "Transport": "http",
      "Url": "https://deployedbyai.com/log/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-deployedbyai-the-deploy-log -t streamable-http -u 'https://deployedbyai.com/log/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-deployedbyai-the-deploy-log": {
      "type": "http",
      "url": "https://deployedbyai.com/log/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-06 (score 88, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-01 (score 88, +1)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 83, +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.

### 2026-10-19 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `recent_deployments` (~140 tokens)

Recent AI deployments

The newest rows to enter The Deploy Log, newest first. Optionally one lane or one company. Each row names what shipped, when, and the publisher's own source URL.

Input parameters:

- `company` (string): A company's name as the record writes it, for example OpenAI or Google
- `lane` (string): One lane: models_apis (Models and APIs), tools_products (Tools and products), robotics_hardware_chips (Robotics, hardware and chips), breakthroughs (Breakthroughs), funding_acquisitions (Funding and…
- `limit` (integer): How many rows, 1 to 25, default 10

### `deployments_in_week` (~58 tokens)

AI deployments in one ISO week

Every row of The Deploy Log that shipped in one ISO week, the same rows as its week page. Each row carries the publisher's own source URL.

Input parameters:

- `week` (string, required): An ISO week, for example 2026-W39

### `search_deployments` (~81 tokens)

Search AI deployments

Rows of The Deploy Log whose company, subject or what shipped contains the words given, newest first. Each row carries the publisher's own source URL.

Input parameters:

- `limit` (integer): How many rows, 1 to 25, default 10
- `query` (string, required): Words to find, for example a model, a product or a company

## Diagnostics

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

## Score history

- 2026-11-06: 88
- 2026-11-05: 88
- 2026-11-04: 88
- 2026-11-03: 88
- 2026-11-02: 88
- 2026-11-01: 88
- 2026-10-31: 87
- 2026-10-30: 87
- 2026-10-29: 86
- 2026-10-28: 86
- 2026-10-27: 85
- 2026-10-26: 85
- 2026-10-25: 85
- 2026-10-24: 84
- 2026-10-23: 84
- 2026-10-22: 83
- 2026-10-21: 83
- 2026-10-20: 82
- 2026-10-19: 82
- 2026-10-18: 81
- 2026-10-17: 81
- 2026-10-16: 78
- 2026-10-15: 77
- 2026-10-14: 77
- 2026-10-13: 77
- 2026-10-12: 76
- 2026-10-10: 75
- 2026-10-09: 75
- 2026-10-04: 72
- 2026-10-03: 72

## Common questions

### What is the The Deploy Log MCP server?

The Deploy Log is an MCP server listed in the public MCP registry as com.deployedbyai/the-deploy-log. AI deployments that shipped and are available now, each sourced to the publisher's own page. This page covers its hosted endpoint (https://deployedbyai.com/log/mcp).

### Is the The Deploy Log MCP server safe to use?

The Deploy Log scores 88 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 The Deploy Log MCP server expose?

The Deploy Log exposes 3 tools: recent_deployments, deployments_in_week, search_deployments. Their descriptions and schemas cost roughly 279 tokens of context every time the server is loaded.

### Does the The Deploy Log MCP server require authentication?

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

### Is the The Deploy Log MCP server still maintained?

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

VerifyMCP ran 13 checks on The Deploy Log, 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://deployedbyai.com/log/mcp
- Website: https://deployedbyai.com/log/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-deployedbyai-the-deploy-log/log-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-deployedbyai-the-deploy-log/log-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-deployedbyai-the-deploy-log/log-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-deployedbyai-the-deploy-log/log-mcp