# Deadline Desk (remote · deadline.bot2botlabs.com)

US retail return/warranty/cancel policy lookup with cited text and TRACE receipts.

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

## Components

- remote · `deadline.bot2botlabs.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-bot2botlabs-deadline-desk/deadline.md), [page](https://verifymcp.io/servers/com-bot2botlabs-deadline-desk/deadline)

## Channel facts

- Endpoint: `https://deadline.bot2botlabs.com/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-05.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 52/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 370 tokens (~185/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% 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 Deadline Desk MCP server?

Deadline Desk is a hosted endpoint at https://deadline.bot2botlabs.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-bot2botlabs-deadline-desk 'https://deadline.bot2botlabs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-bot2botlabs-deadline-desk": {
      "url": "https://deadline.bot2botlabs.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-bot2botlabs-deadline-desk]
url = "https://deadline.bot2botlabs.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-bot2botlabs-deadline-desk:
    url: "https://deadline.bot2botlabs.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-bot2botlabs-deadline-desk": {
      "type": "http",
      "url": "https://deadline.bot2botlabs.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-04 (score 74, +1)

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

### 2026-11-02 (score 73, +1)

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

### 2026-10-31 (score 72, +1)

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

### 2026-10-29 (score 71, +1)

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

### 2026-10-28 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 155 → 185

### 2026-10-27 (score 70, +5)

- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional] Schema quality: good → fair
- [cosmetic] Tool “get_receipt” changed its title: Fetch lookup receipt
- [cosmetic] Tool “lookup_policy” changed its title: Look up retail policy

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

- [security] Tool “get_receipt” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 92 → 106
- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 64)

First indexed and scored.

## MCP tools (2)

### `lookup_policy` (~155 tokens)

Look up retail policy

Look up a US retailer's published return, price adjustment, warranty, or cancellation policy with quoted source text and a TRACE receipt. Call before Black Friday / Cyber Week purchase decisions (holiday_extended_return.policy_year overlays, price_adjustment_detail honesty). Call Dec 26–Jan 31 for return-by urgency — responses surface exceptions before headline January dates and honest live|curated|archive source badges.

Input parameters:

- `anchor_date` (string): Delivery or purchase date (ISO) when computing last eligible day
- `as_of` (string): ISO date (YYYY-MM-DD) for deadline math
- `kind` (string, required)
- `store` (string, required): Store slug or domain, e.g. "target" or "target.com"

### `get_receipt` (~58 tokens)

Fetch lookup receipt

Fetch a public receipt from a prior Deadline Desk policy lookup. ddr_ IDs return a format v1 receipt (signed, software-only TRACE record); older dd- IDs return the v0 log entry.

Input parameters:

- `receipt_id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 65
- 2026-10-25: 65
- 2026-10-24: 64

## Common questions

### What is the Deadline Desk MCP server?

Deadline Desk is an MCP server listed in the public MCP registry as com.bot2botlabs/deadline-desk. US retail return/warranty/cancel policy lookup with cited text and TRACE receipts. This page covers its hosted endpoint (https://deadline.bot2botlabs.com/mcp).

### Is the Deadline Desk MCP server safe to use?

Deadline Desk scores 74 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 Deadline Desk MCP server expose?

Deadline Desk exposes 2 tools: lookup_policy, get_receipt. Their descriptions and schemas cost roughly 213 tokens of context every time the server is loaded.

### Does the Deadline Desk MCP server require authentication?

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

### Is the Deadline Desk MCP server still maintained?

Deadline Desk 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.

## Links

- Remote endpoint: https://deadline.bot2botlabs.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-bot2botlabs-deadline-desk/deadline.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-bot2botlabs-deadline-desk/deadline.json
- HTML version of this page: https://verifymcp.io/servers/com-bot2botlabs-deadline-desk/deadline