# Wraps (remote · wraps.dev)

Search the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication.

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

## Components

- remote · `wraps.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-wraps-docs/wraps.md), [page](https://verifymcp.io/servers/dev-wraps-docs/wraps)

## Channel facts

- Endpoint: `https://wraps.dev/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-09-20.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 583 tokens (~145/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Wraps MCP server?

Wraps is a hosted endpoint at https://wraps.dev/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 dev-wraps-docs 'https://wraps.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-wraps-docs": {
      "url": "https://wraps.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-wraps-docs": {
      "type": "http",
      "url": "https://wraps.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-wraps-docs]
url = "https://wraps.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-wraps-docs": {
      "type": "remote",
      "url": "https://wraps.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-wraps-docs --url 'https://wraps.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-wraps-docs:
    url: "https://wraps.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-wraps-docs": {
      "Transport": "http",
      "Url": "https://wraps.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-wraps-docs -t streamable-http -u 'https://wraps.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-wraps-docs": {
      "type": "http",
      "url": "https://wraps.dev/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-09-20 (score 73, +1)

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

### 2026-09-18 (score 72, +1)

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

### 2026-09-15 (score 71, +1)

- [functional improvement] Tool “estimate_cost” now declares an output schema
- [functional improvement] Tool “get_doc” now declares an output schema
- [functional improvement] Tool “list_docs” now declares an output schema
- [functional improvement] Tool “search_docs” now declares an output schema
- [functional] First check of Tool coverage: 100

### 2026-09-13 (score 70, +1)

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

### 2026-09-11 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-10 (score 68)

First indexed and scored.

## MCP tools (4)

### `search_docs` (~91 tokens)

Search Wraps docs

Search the full Wraps documentation (CLI, TypeScript SDKs, infrastructure, guides) and return the matching sections as markdown. Use this first for any 'how do I ... with Wraps' question.

Input parameters:

- `limit` (integer): Maximum sections to return (default 5).
- `query` (string, required): Words to search for, e.g. 'verify domain', 'send batch', 'bounce handling'.

Output parameters:

- `matches` (array): Empty when nothing matched; that is a result, not an error.
- `query` (string): The query as searched.

### `get_doc` (~58 tokens)

Read a Wraps doc page

Return the full markdown source of one Wraps page. Call list_docs first to see which paths have markdown.

Input parameters:

- `path` (string, required): Site path such as /docs/quickstart/email, or the full https://wraps.dev/... URL.

Output parameters:

- `markdown` (string): Full markdown source.
- `path` (string): Site path that was read.
- `url` (string): Canonical URL of the page.

### `list_docs` (~35 tokens)

List Wraps documentation

Return the Wraps llms.txt index: every documentation page, product page, guide, and SDK reference with a one-line description.

Output parameters:

- `source` (string): URL the index was read from.

### `estimate_cost` (~289 tokens)

Estimate Wraps + AWS cost

Estimate the real monthly cost of running email on Wraps + AWS: the flat Wraps platform fee for the plan, and the itemized AWS bill (SES, EventBridge, SQS, Lambda, DynamoDB, dedicated IP, WAF). The Wraps fee never varies with volume; the AWS-side event-pipeline line items (EventBridge, SQS, Lambda, DynamoDB) are derived from emails sent and event types per email. The events parameter is accepted for backward compatibility and does not currently affect the estimate. Use this instead of doing the arithmetic — six variables interact, including which SES pricing plan the AWS account is on.

Input parameters:

- `billing` (string): Wraps billing interval.
- `dedicatedIp` (boolean): Include a dedicated sending IP.
- `emails` (integer, required): Emails sent per month.
- `events` (integer): Custom events you emit via POST /v1/events per month. Emails sent and SES delivery events (deliveries, opens, clicks, bounces) are not counted and do not affect price.
- `retention` (string): How long email event history is kept.
- `sesPlan` (string): AWS SES pricing plan for that account and Region. New AWS accounts default to 'essentials' ($0.16/1K); 'alacarte' is $0.10/1K.
- `tier` (string): Wraps plan.

Output parameters:

- `aws` (object): AWS-side cost, itemized.
- `currency` (string): Always USD.
- `input` (object): The estimate inputs, after defaults were applied.
- `period` (string): Always month.
- `shareUrl` (string): Link reproducing this estimate on wraps.dev.
- `total` (number): Wraps fee plus the AWS bill.
- `wraps` (object): Flat Wraps platform fee for the plan. Does not vary with volume.

## Diagnostics

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

## Score history

- 2026-09-20: 73
- 2026-09-19: 72
- 2026-09-18: 72
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68

## Common questions

### What is the Wraps MCP server?

Wraps is an MCP server listed in the public MCP registry as dev.wraps/docs. Search the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication. This page covers its hosted endpoint (https://wraps.dev/mcp).

### Is the Wraps MCP server safe to use?

Wraps scores 73 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 Wraps MCP server expose?

Wraps exposes 4 tools: search_docs, get_doc, list_docs, estimate_cost. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.

### Does the Wraps MCP server require authentication?

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

### Is the Wraps MCP server still maintained?

Wraps is still listed as active in the MCP registry. We last reached this channel on 20 September 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://wraps.dev/mcp
- Repository: https://github.com/wraps-team/wraps
- Website: https://wraps.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-wraps-docs/wraps.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-wraps-docs/wraps.json
- HTML version of this page: https://verifymcp.io/servers/dev-wraps-docs/wraps