Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

DashaMail

MCP server · mcp.dashamail.ru · found in a public registry · checked since 2026-10-17

Timed out · latest check

As JSON

GET https://mcp.dashamail.ru/

The name is the registry's label, not ours. Not reviewed by a person.

Our checks

An unpaid request daily, from eastern North America

Last 2 checks, oldest to newest; room for 28 more

1 passed, 1 failed, 28 not run.

Passed, 30 daysshort history1 of 2 run
Checks missed0in 30 days
Response, latest—to first headers
Scheduledailyset by usage; rule below
Checked since2026-10-172 days
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hours00——————
7 dayssince 2026-10-1721——————
30 dayssince 2026-10-1721——————

Milliseconds, from eastern North America, timing a passing answer. Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Access

Our latest check
not observed
Stated
not stated
Payment model
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Listing

In the capability tree: Messaging and communication / Email / Newsletters and campaigns (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.

In the index only: does not meet every one of our listing criteria (listing-criteria/4): ✓ says what it does; ✗ its latest check did not pass.

Recent probes

WhenResultTime to headers

cloudflare:MIA
Timed out
no response within 10000 ms
—

cloudflare:EWR
Live, MCP endpoint answered HTTP 405 1563 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
  • Limited evidence: monitored for 2 days (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_4221d7cc943f503a