Search the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication.
Wraps is a remote MCP server published at wraps.dev. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 530 ms, a delay an agent will notice. It offers a narrow, focused set of 4 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
list_docs — Description does not explain when or why to use this tool.estimate_cost — Parameters like 'tier' and 'billing' have unclear definitions and constraints.| Run |
|---|
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
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.
querystringrequiredlimitintegerget_docReturn the full markdown source of one Wraps page. Call list_docs first to see which paths have markdown.
pathstringrequiredlist_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 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.
emailsintegerrequiredeventsintegertierstringbillingstringsesPlanstringdedicatedIpbooleanretentionstringDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/dev-wraps-docs)<a href="https://mcpmetrics.io/servers/dev-wraps-docs"><img src="https://mcpmetrics.io/badge/dev.wraps/docs/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
Read-only MCP for Rialto quotes and swap preflight on Robinhood Chain. No signing or broadcast.
Search Vascue's public healthcare-ops, insurance-claims and booking docs. Public content only.
Public record of one read only walk over the official MCP registry: who answered, tools, who pays.
Read-only OpenHeritage search for genealogy and cultural heritage records.
Public fellowship and grant search with sourced details and live filter vocabularies.
| Era |
|---|
| Modern |
|---|
| ms |
|---|
| Legacy |
|---|
| ms |
|---|
| Versions |
|---|
| 2026-09-13 01:33:33 | Dual-era | 200 | 768 | 200 | 737 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 |
| 2026-09-12 23:31:36 | Dual-era | 200 | 530 | 200 | 536 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 |
| 2026-09-12 21:29:15 | Dual-era | 200 | 842 | 200 | 860 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 |
| 2026-09-12 19:27:29 | Dual-era | 200 | 400 | 200 | 384 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 |
| 2026-09-12 17:24:09 | Dual-era | 200 | 259 | 200 | 242 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 |
| 2026-09-12 15:21:42 | Dual-era | 200 | 366 | 200 | 353 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.