# Pouch.me (remote · agents.pouch.me)

Custom printed pouches, plus labels, tissue, tape and boxes (Pouch.me): specs and quote requests.

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

## Components

- remote · `agents.pouch.me`: 63/100 (this document), [markdown](https://verifymcp.io/servers/me-pouch-agents/agents.md), [page](https://verifymcp.io/servers/me-pouch-agents/agents)

## Channel facts

- Endpoint: `https://agents.pouch.me/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## 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**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 972 tokens (~138/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 9 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Pouch.me MCP server?

Pouch.me is a hosted endpoint at https://agents.pouch.me/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 me-pouch-agents 'https://agents.pouch.me/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "me-pouch-agents": {
      "url": "https://agents.pouch.me/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-pouch-agents": {
      "type": "http",
      "url": "https://agents.pouch.me/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.me-pouch-agents]
url = "https://agents.pouch.me/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-pouch-agents": {
      "type": "remote",
      "url": "https://agents.pouch.me/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-pouch-agents --url 'https://agents.pouch.me/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-pouch-agents:
    url: "https://agents.pouch.me/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "me-pouch-agents": {
      "Transport": "http",
      "Url": "https://agents.pouch.me/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-pouch-agents -t streamable-http -u 'https://agents.pouch.me/mcp'
```

### Other

```json
{
  "mcpServers": {
    "me-pouch-agents": {
      "type": "http",
      "url": "https://agents.pouch.me/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-03 (score 63, +1)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 63%
- [functional] Schema quality: fair → good
- [functional] New tool “recommend_bag_size”

### 2026-11-02 (score 62, −3)

- [security regression] Stability: 0.17 → fail
- [security regression] Tool “inkable_options” was removed
- [security regression] Tool “inkable_price” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: fail → pass
- [functional] Schema quality: good → fair
- [functional] Server version: 1.0.1 → 1.0.2

### 2026-11-01 (score 65, +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-30 (score 64, +1)

- [functional improvement] Schema quality: 134 → 113
- [functional] New tool “bag_recommendation_questions”
- [functional] New tool “recommend_bag_type”

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

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

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

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 62)

First indexed and scored.

## MCP tools (7)

### `list_bag_formats` (~30 tokens)

List bag formats

Pouch.me: the bag formats we quote, with each format's minimum order quantity per design.

### `get_bag_format` (~39 tokens)

Get one bag format

Pouch.me: details for one format id from list_bag_formats (options, materials, minimum).

Input parameters:

- `format_id` (string, required)

### `how_we_work` (~44 tokens)

How Pouch.me works

Pouch.me: what's free (design, prepress, standard US shipping), the quote -> proof -> payment steps, options, materials and what we need from the customer.

### `bag_recommendation_questions` (~28 tokens)

Bag recommendation questions

Pouch.me: the questions (and allowed answers) for recommend_bag_type.

### `recommend_bag_type` (~71 tokens)

Recommend a bag type

Pouch.me: a rule-based starting suggestion for bag format and material. It doesn't size the bag or check fit; our team confirms format, size and material on the written quote. Pass answers as {question_id: choice_id} from bag_recommendation_questions.

Input parameters:

- `answers` (object, required)

### `recommend_bag_size` (~297 tokens)

Recommend a bag size

Pouch.me: a starting bag size from the same sizing tool as pouch.me/bag-sizing and our quote form's "Size it for me". Give the product, how much goes in each bag (weight, volume or count) and the bag type (e.g. from recommend_bag_type); for solid pieces add the size of one piece. Returns the recommended outside size in inches and mm, how well it fits, and the sizing tool's own explanation. Our team confirms the final size on the written quote. To put the size on a quote request, pass sizing_reference to submit_quote_request.

Input parameters:

- `bag_size`: A bag size the customer already has in mind, with units, if any. The sizing tool checks it.
- `fill_amount` (string, required): How much goes in each bag: weight, volume or count, e.g. '12 oz', '250 g', '24 cookies'. Ask the customer; don't guess.
- `format` (string): Bag type, e.g. from recommend_bag_type. not_sure lets the sizing tool pick. Roll stock isn't sized.
- `piece_size`: For solid pieces (cookies, bars, jerky): the size of one piece with units, e.g. '4 x 4 x 1 in'.
- `product` (string, required): What goes in the bag, e.g. 'whole bean coffee'. Ask the customer; don't guess.

### `submit_quote_request` (~106 tokens)

Submit a quote request

Pouch.me: send a quote request to our team for your user. We email your user a confirmation link first; the request reaches our team only after they confirm it themselves (don't click it for them). Our team reviews it; if it's something we can make, we reply by email with a written quote or a question about the spec. No reply time is given. Requires customer_consent=true. Returns a reference number. Does not create an order.

Input parameters:

- `request` (required)

## Diagnostics

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

## Score history

- 2026-11-05: 63
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 62
- 2026-11-01: 65
- 2026-10-31: 64
- 2026-10-30: 64
- 2026-10-29: 63
- 2026-10-28: 62
- 2026-10-27: 62

## Common questions

### What is the Pouch.me MCP server?

Pouch.me is an MCP server listed in the public MCP registry as me.pouch/agents. Custom printed pouches, plus labels, tissue, tape and boxes (Pouch.me): specs and quote requests. This page covers its hosted endpoint (https://agents.pouch.me/mcp).

### Is the Pouch.me MCP server safe to use?

Pouch.me scores 63 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 Pouch.me MCP server expose?

Pouch.me exposes 7 tools: list_bag_formats, get_bag_format, how_we_work, bag_recommendation_questions, recommend_bag_type, and 2 more. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

### Does the Pouch.me MCP server require authentication?

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

### Is the Pouch.me MCP server still maintained?

Pouch.me 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.

### What did VerifyMCP test on the Pouch.me MCP server?

VerifyMCP ran 12 checks on Pouch.me, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Pouch.me: HTTPS. 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://agents.pouch.me/mcp
- Website: https://agents.pouch.me/
- Changelog RSS feed: https://verifymcp.io/servers/me-pouch-agents/agents.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-pouch-agents/agents/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/me-pouch-agents/agents.json
- HTML version of this page: https://verifymcp.io/servers/me-pouch-agents/agents