GovDelivery MCP by usefulapi

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/govdelivery and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 7 Nov 2026. Not supplied by the maker.

• govdelivery_list_topics

  List the topics of the GovDelivery account (their codes and names). Topic codes are needed for subscriptions and bulletins. Read-only. GovDelivery REST: GET /api/account/{account}/topics.

• govdelivery_get_subscriber

  Read one subscriber by email address: their topic subscriptions and record fields, as GovDelivery returns them (XML). Read-only. GovDelivery REST: GET /api/account/{account}/subscribers/{base64 email}

• govdelivery_get_bulletin

  Read one bulletin by id: subject, state (draft or sent), topics and total subscribers, as GovDelivery returns them (XML). Read-only. Bulletin ids come from the bulletin you created or from GovDelivery

• govdelivery_set_subscriber_topics

  WRITE: adds ONE subscriber to topics, or REPLACES that subscriber's topic subscriptions with exactly the codes given (GovDelivery 'replace or create'), so topics not listed may be removed. Use only fo

• govdelivery_create_bulletin_draft

  WRITE: creates a DRAFT bulletin for the given topics. Nothing is sent: the draft waits in GovDelivery until govdelivery_send_bulletin sends it. Subject: plain text, max 400 characters; GovDelivery adv

• govdelivery_send_bulletin

  WRITE: SENDS an existing DRAFT bulletin by email to every subscriber of its topics, now. This cannot be undone. Set confirm_send to true only after the user has approved this exact bulletin in this co