Skip to content
Bot2Bot Labs logo

Bot2Bot Labs MCP server

Which MCP servers are Bot2Bot Labs's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Bot2Bot Labs

Whose server it is
  • Registry namecom.bot2botlabs/deadline-deskverified in the MCP registry

The registry name sits under bot2botlabs.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools2
  • Server calls itselfdeadline-desk
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 191 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 2 of 2 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer149 ms
  • Space in an agent's context≈ 352 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 2

What an agent can do with it

  • not sure · compare AI-built clone costs against the subscription each replaces
  • not sure · check run cost of an AI-built app against hosting list prices
  • not sure · order a dated, measured receipt for an AI-built app

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-29
  • lookup_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…

  • get_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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http bot2botlabs https://deadline.bot2botlabs.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://deadline.bot2botlabs.com/mcp as a custom connector in the settings.

Other servers listed as Bot2Bot Labs's
  • com.bot2botlabs/loop-deskanswers, 3 toolsverified in the MCP registry
  • com.bot2botlabs/warranty-deskanswers, 2 toolsverified in the MCP registry

OpenAPI spec

2 paths, read 2026-10-29. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.