Skip to content
Find A Co-Packer logo

Find A Co-Packer MCP server

Which MCP servers are Find A Co-Packer'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-26

← Back to Find A Co-Packer

Whose server it is
  • Registry nameuk.co.findacopacker/siteverified in the MCP registry

The registry name sits under findacopacker.co.uk. 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-26
  • Stateanswerschecked 2026-10-26
  • Tools3
  • Server calls itselfFind A Co-Packer (findacopacker.co.uk)
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 683 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 2 of the 7 days it takes to judge reliability.

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: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer899 ms
  • Space in an agent's context≈ 598 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 3 of 3

What an agent can do with it

  • not sure · write a brief a contract packer can price
  • cannot · check minimum order quantity against the first run
  • not sure · compare packer quotes on the same specification

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 offers3 tools · read 2026-10-26
  • enquiry_describe

    Read first. States plainly what submit_enquiry does on Find A Co-Packer: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the…

  • enquiry_fields

    Every field of the Find A Co-Packer enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

  • submit_enquiry

    Submits an enquiry to Find A Co-Packer — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a…

How to connect

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

{
  "mcpServers": {
    "site": {
      "type": "http",
      "url": "https://findacopacker.co.uk/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http findacopacker https://findacopacker.co.uk/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://findacopacker.co.uk/mcp as a custom connector in the settings.

OpenAPI spec

4 paths, read 2026-10-26. 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.