Wraps
REMOTE · WRAPS.DEV · SCANNED OCT 14
Search the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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
claude mcp add --transport http dev-wraps-docs 'https://wraps.dev/mcp'
{
"mcpServers": {
"dev-wraps-docs": {
"url": "https://wraps.dev/mcp"
}
}
} {
"servers": {
"dev-wraps-docs": {
"type": "http",
"url": "https://wraps.dev/mcp"
}
}
} [mcp_servers.dev-wraps-docs] url = "https://wraps.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-wraps-docs": {
"type": "remote",
"url": "https://wraps.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-wraps-docs --url 'https://wraps.dev/mcp' --transport streamable-http
mcp_servers:
dev-wraps-docs:
url: "https://wraps.dev/mcp" {
"McpServers": {
"dev-wraps-docs": {
"Transport": "http",
"Url": "https://wraps.dev/mcp"
}
}
} assistant mcp add dev-wraps-docs -t streamable-http -u 'https://wraps.dev/mcp'
{
"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.
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.
- 10 Oct 26 +3
- Stability: 0.80 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 14 Oct 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=YR1,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | RSA 2048 | SHA256-RSA | 5cda996a47f1a50febe0fa2610ef496af42 |
| SANs: wraps.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 |
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 →
estimate_cost Estimate Wraps + AWS 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.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | – | Wraps billing interval. |
| dedicatedIp | boolean | – | Include a dedicated sending IP. |
| emails | integer | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| aws | object | – | AWS-side cost, itemized. |
| currency | string | yes | Always USD. |
| input | object | – | The estimate inputs, after defaults were applied. |
| period | string | yes | Always month. |
| shareUrl | string | – | Link reproducing this estimate on wraps.dev. |
| total | number | yes | Wraps fee plus the AWS bill. |
| wraps | object | – | Flat Wraps platform fee for the plan. Does not vary with volume. |
No examples provided.
get_doc Read a Wraps doc page ~58
Return the full markdown source of one Wraps page. Call list_docs first to see which paths have markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Site path such as /docs/quickstart/email, or the full https://wraps.dev/... URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | Full markdown source. |
| path | string | yes | Site path that was read. |
| url | string | yes | Canonical URL of the page. |
No examples provided.
list_docs List Wraps documentation ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | URL the index was read from. |
No examples provided.
search_docs Search Wraps 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum sections to return (default 5). |
| query | string | yes | Words to search for, e.g. 'verify domain', 'send batch', 'bounce handling'. |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | Empty when nothing matched; that is a result, not an error. |
| query | string | yes | The query as searched. |
No examples provided.
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 89 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 14 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.