Courier
io.github.trycourier/courier
Send notifications, manage templates, and configure integrations with Courier.
— the operator's own registry description reported
Publisher io.github.trycourier · first seen
2026-08-12 · endpoint https://mcp.courier.com
Dependency rating derived
allow — rich-solo — safe to depend on
Cluster rich-solo · distinctiveness 0.478 (moderate). 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
latency85 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools144
vs populationhigh
capabilities1
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary
🔏 Signed receipt rr_df53dd7aaff65a2296f44ed3 · 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_bulk_users add_subscribers_to_list add_user_to_tenant archive_journey archive_journey_template archive_notification archive_preference_section archive_preference_topic archive_request archive_routing_strategy bulk_add_user_tenants bulk_add_user_tokens bulk_replace_user_preferences bulk_subscribe_to_list bulk_update_user_preferences cancel_automation cancel_journey cancel_message cancel_notification_submission courier_installation_guide create_brand create_bulk_job create_journey create_journey_template create_list create_notification create_or_merge_user create_or_replace_user_push_token create_or_update_tenant create_preference_section create_preference_topic create_provider create_routing_strategy delete_audience delete_brand delete_list delete_profile delete_provider delete_tenant delete_tenant_preference delete_tenant_template delete_user_list_subscriptions delete_user_preference_topic delete_user_token generate_jwt_for_user get_audience get_audit_event get_brand get_bulk_job get_journey get_journey_template get_journey_template_content get_list get_list_subscribers get_message get_message_content get_message_history get_notification get_notification_content get_notification_draft_content get_preference_section get_preference_topic get_provider get_routing_strategy get_tenant get_tenant_template get_tenant_template_version get_translation get_user_list_subscriptions get_user_preference_topic get_user_preferences get_user_profile_by_id get_user_push_token invoke_ad_hoc_automation invoke_automation_template invoke_journey list_audience_members list_audiences list_audit_events list_automations list_brands list_bulk_users list_digest_instances list_journey_template_versions list_journey_templates list_journey_versions list_journeys list_lists list_messages list_notification_checks list_notification_versions list_notifications list_preference_sections list_preference_topics list_provider_catalog list_providers list_routing_strategies list_routing_strategy_notifications list_tenant_templates list_tenant_users list_tenants list_user_push_tokens list_user_tenants patch_profile patch_user_token publish_journey publish_journey_template publish_notification publish_preferences publish_tenant_template put_journey_template_content put_journey_template_locale put_notification_content put_notification_element put_notification_locale release_digest remove_all_user_tenants remove_user_from_tenant replace_journey replace_journey_template replace_notification replace_preference_section replace_preference_topic replace_profile replace_routing_strategy replace_tenant_template resend_message restore_list run_bulk_job send_message send_message_template send_message_to_list send_message_to_list_template subscribe_user_to_list subscribe_user_to_lists track_inbound_event unsubscribe_user_from_list update_audience update_brand update_notification_checks update_provider update_tenant_preference update_translation update_user_preference_topic
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 A — an agent can pick and call these reliably.
144 of 144 tools graded · 144 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
2025-06-18
protocol version
1.3.7
server version @trycourier/courier-mcp
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)
raw probe
records
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:
[](https://robinsaige.com/s/io.github.trycourier/courier)
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