Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Wraps

REMOTE · WRAPS.DEV · SCANNED SEP 20

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

Available components

remote · wraps.dev 73
+3 this week 73 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

remote · wraps.dev

# add to Claude Code
claude mcp add --transport http dev-wraps-docs 'https://wraps.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-wraps-docs": {
      "url": "https://wraps.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-wraps-docs": {
      "type": "http",
      "url": "https://wraps.dev/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-wraps-docs --url 'https://wraps.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-wraps-docs:
    url: "https://wraps.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-wraps-docs": {
      "Transport": "http",
      "Url": "https://wraps.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dev-wraps-docs -t streamable-http -u 'https://wraps.dev/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +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.

  • 18 Sept 26 +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.

  • 15 Sept 26 +1
    • Tool “estimate_cost” now declares an output schema ▲ functional
    • Tool “get_doc” now declares an output schema ▲ functional
    • Tool “list_docs” now declares an output schema ▲ functional
    • Tool “search_docs” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
  • 13 Sept 26 +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.

  • 11 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Sept 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://wraps.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wraps.dev CN=YR2,O=Let's Encrypt,C=US 18 Jul 2026 16 Oct 2026 RSA 2048 SHA256-RSA 5b46ea9f84cb82c97c49b69f9663aaa0993
SANs: wraps.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of wraps.dev. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
wraps.dev. present 2371 13 Verified
wraps.dev. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wraps.dev/mcp Verified 200
http (plaintext) http://wraps.dev/mcp HTTPS enforced 308 https://wraps.dev/mcp
MCP tools · 4 exposed · ~473 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
estimate_cost ~289

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.

NameTypeReqDescription
billingstring–Wraps billing interval.
dedicatedIpboolean–Include a dedicated sending IP.
emailsintegeryesEmails sent per month.
eventsinteger–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.
retentionstring–How long email event history is kept.
sesPlanstring–AWS SES pricing plan for that account and Region. New AWS accounts default to 'essentials' ($0.16/1K); 'alacarte' is $0.10/1K.
tierstring–Wraps plan.
NameTypeReqDescription
awsobject–AWS-side cost, itemized.
currencystringyesAlways USD.
inputobject–The estimate inputs, after defaults were applied.
periodstringyesAlways month.
shareUrlstring–Link reproducing this estimate on wraps.dev.
totalnumberyesWraps fee plus the AWS bill.
wrapsobject–Flat Wraps platform fee for the plan. Does not vary with volume.

No examples provided.

get_doc ~58

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

NameTypeReqDescription
pathstringyesSite path such as /docs/quickstart/email, or the full https://wraps.dev/... URL.
NameTypeReqDescription
markdownstringyesFull markdown source.
pathstringyesSite path that was read.
urlstringyesCanonical URL of the page.

No examples provided.

list_docs ~35

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
sourcestringyesURL the index was read from.

No examples provided.

search_docs ~91

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.

NameTypeReqDescription
limitinteger–Maximum sections to return (default 5).
querystringyesWords to search for, e.g. 'verify domain', 'send batch', 'bounce handling'.
NameTypeReqDescription
matchesarrayyesEmpty when nothing matched; that is a result, not an error.
querystringyesThe query as searched.

No examples provided.

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.