Should my agent depend on the MCP server io.github.AinaLuc/mailcannon?

Verdict: allow — stale-rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Mailcannon

io.github.AinaLuc/mailcannon

AI-powered email outreach platform — send campaigns with deliverability tracking.

— the operator's own registry description reported

Publisher io.github.AinaLuc · first seen 2026-08-12 · endpoint https://www.thinkandautomate.dev/api/mcp

allow

verdict

stale-rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — stale-rich-solo — safe to depend on

Cluster stale-rich-solo · distinctiveness 0.302 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency236 ms

vs populationtypical

protocolstale

authopen

Use — can it use it?

tools34

vs populationhigh

capabilities1

harnessB

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_589d7c5627696353f16c40e7 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

add_campaign_step add_contact add_contacts add_provider check_domain_deliverability check_email_spam_score check_step_spam_score create_campaign create_task delete_campaign delete_campaign_step delete_task get_deliverability get_setting list_campaigns list_contacts list_providers list_schedules list_settings list_tags list_tasks pause_campaign process_campaigns remove_contact remove_provider resume_campaign retry_failed schedule_campaign send_test_email set_setting update_campaign update_campaign_step update_contact_tags update_task

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	34/34	✓
has a description	34/34	✓
description is substantive	16/34	16/34
parameters are typed	34/34	✓
parameters are described	11/34	11/34

34 of 34 tools graded · 34 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2024-11-05

protocol version

—

session model

0.1.0

server version mailcannon

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:54Z	ok_tools	200	236	2024-11-05
2026-08-12T05:34:08Z	ok_tools	200	158	2024-11-05

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.AinaLuc/mailcannon.svg)](https://robinsaige.com/s/io.github.AinaLuc/mailcannon)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview