Wraps MCP server
Which servers in the official MCP registry are Wraps's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namedev.wraps/docsverified in the MCP registry
The registry name sits under wraps.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools4
- Server calls itselfwraps
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 123 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 3 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.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- Use29 npm downloads a week64 GitHub stars
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer195 ms
- Space in an agent's context≈ 715 tokensthe definitions of all its tools (4), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
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 (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). 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 →
search_docsSearch 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.
get_docReturn the full markdown source of one Wraps page. Call list_docs first to see which paths have markdown.
list_docsReturn the Wraps llms.txt index: every documentation page, product page, guide, and SDK reference with a one-line description.
estimate_costEstimate 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://wraps.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http wraps https://wraps.dev/mcpclaude.ai, ChatGPT and other clients: add https://wraps.dev/mcp as a custom connector in the settings.
- dev.wraps/emailnot asked yetverified in the MCP registry
OpenAPI spec
57 paths, read 2026-10-19. 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.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.