Is com.qualisend/email-verification up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | Qualisend 1.0.0 |
| Answered in | 266 ms |
| Endpoint checked | https://app.qualisend.com/api/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Could not tell (fetch failed: 801ED4ED01000000:error:0A00010B:SSL routines:tls_validate_record_header:wrong version number:../deps/open…)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Could not tell (not asked: https://app.qualisend.com did not answer the agent-card request).https://app.qualisend.com/api/mcp/server-card |
| MCP server card (SEP-1649 location) | Could not tell (not asked: https://app.qualisend.com did not answer the agent-card request)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (not asked: https://app.qualisend.com did not answer the agent-card request)./.well-known/http-message-signatures-directory |
Read at https://app.qualisend.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 12 tools: analyze_email_header, check_blacklist, check_disposable, check_domain, check_typo, generate_dns_record, get_credit_balance, get_verification, lookup_smtp_code, verify_email, verify_emails, verify_list.
Its tools changed between 2026-09 and 2026-10:
check_blacklist: description changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.qualisend/email-verification |
|---|---|
| Endpoint | https://app.qualisend.com/api/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt