mcpbeat Sign in

Wraps MCP Server

not responding

Wraps is listed as active in the registry but did not answer our last check. It exposes 4 tools. Last commit 2 Nov 2026.

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

Uptime history 54 days of history · worst day 3%
54 days agonow
7.7%
Uptime 24h
7 of 91 checks
4
Tools
read from the server
511 ms
Response time
average over 24h
66
Stars
last commit 2 Nov 2026

What the code does

We read the source, 23 h ago · tools taken from the live server · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

                  ~/.aws/credentials
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a database query by concatenation packages/cli/src/commands/email/domains.ts:1574
            `\n${pc.dim(`Distribution ${trackingDistributionId} is disabled; delete it from the CloudFront console once it shows Deployed (10-15 min). Certificate ${domainInfo?.entry?.trackingHttps?.certificateArn} can then be deleted in ACM (us-east-1).`)}`
                  ~/.aws/credentials
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Claims read-only, but the code runs commands infra/api.ts:121
        execSync(`npx @sentry/cli sourcemaps inject ${buildDir}`, {
Runs an external command infra/api.ts:121
        execSync(`npx @sentry/cli sourcemaps inject ${buildDir}`, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Wraps and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add docs --transport http https://wraps.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://wraps.dev/mcp
~/.codex/config.toml
[mcp_servers.docs]
url = "https://wraps.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "docs": {
      "url": "https://wraps.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "docs": {
      "type": "http",
      "url": "https://wraps.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

docs
list_docs
Return the Wraps llms.txt index: every documentation page, product page, guide, and SDK reference with a one-line description.
search_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.
doc
get_doc
Return the full markdown source of one Wraps page. Call list_docs first to see which paths have markdown.
estimate
estimate_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.

Endpoints

URLTransportStateLatencyChecked
https://wraps.dev/mcp streamable-http answering 83 ms 10 min ago

Alternatives to Wraps

same job, measured the same way
Clouddocs
by cloudcorprecords

Search, read, and get recommendations for AWS documentation pages.

local only
Tomorrow Central: Cloud Cost Sentinel
by tomorrowcentral

AWS pricing and cost estimates with no signup, plus read-only idle-resource scans of your account.

38 tools answering
Dockerhub
by pipeworx-io

Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)

429 installs/wk 48 tools answering
Kubernetes Troubleshoot
by nanagyamfiprempeh30

Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes.

local only
ByJG Open Source Docs
by byjg

Search the ByJG open source documentation: PHP, DevOps, Helm, JavaScript and AI projects.

3 tools answering
Karandeepsingh Blog
by karandaid

Search and read Karandeep Singh's DevOps and AWS blog: articles and cheatsheets.

11 tools answering
Specshield MCP Server
by specshield-io

The API-change deploy gate for AI coding agents. Read-only breaking-change detection.

local only
Tilebox
by tilebox

Query geospatial datasets, manage workflow jobs, deploy published releases, and search Tilebox docs.

answering

Wraps — questions

Answers built from our own checks of this server.

What can Wraps do?
It exposes 4 tools, read directly from the server on our last check. Among them: estimate_cost, get_doc, list_docs, search_docs. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Wraps working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 7 of 91 checks got a reply (7.7%), average response time 511 ms. The bar chart above shows every period we have measured.
The registry lists Wraps as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Wraps?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Wraps need an API key?
No. Wraps completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Wraps?
It answers our handshake in 511 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Wraps open source?
We cannot say either way: written in TypeScript and 66 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.