io.github.YS-projectcalc/agent-cold-email
REMOTE · API.COLDRIG.DEV · 2 COMPONENTS
Coldrig — cold-email infra run by your agent: 28 MCP tools, live sending, free sandbox, from $99/mo.
Available components
Last scanned (18 hours ago)
Scores higher than 25% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Oct 26 +1
- Authorization: partial → pass ▲ security
- 15 Oct 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.63 → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 13 Oct 26 0
- New tool “add_leads”, which the server declares destructive security
- New tool “resume”, which the server declares destructive security
- Tool “campaign_results” rewrote its description, which is the text the model reads security
- Tool “inbox” rewrote its description, which is the text the model reads security
- Tool “launch_campaign” rewrote its description, which is the text the model reads security
- Tool “list_campaigns” rewrote its description, which is the text the model reads security
- Tool “list_leads” rewrote its description, which is the text the model reads security
- Tool “metrics” rewrote its description, which is the text the model reads security
- Tool “pause” rewrote its description, which is the text the model reads security
- Tool “pause_all” rewrote its description, which is the text the model reads security
- Tool “thread” rewrote its description, which is the text the model reads security
- Schema quality: 223 → 287 ▼ functional
- Tool coverage: 39% → 44% ▲ functional
- “launch_campaign” added an optional parameter “previewOnly” cosmetic
- “launch_campaign” added an optional parameter “includeAlreadyEmailed” cosmetic
- “launch_campaign” added an optional parameter “repeatOf” cosmetic
- 7 Oct 26 0
- Schema quality: 5912 → 6690 ▼ functional
- 1 Oct 26 0
- Tool “setup_infrastructure” rewrote its description, which is the text the model reads security
- Tool “configure_byo_domain” rewrote its description, which is the text the model reads security
- Tool “contact_operator” rewrote its description, which is the text the model reads security
- Tool “infrastructure_status” rewrote its description, which is the text the model reads security
- Tool “list_messages” rewrote its description, which is the text the model reads security
- Tool “remove_mailboxes” rewrote its description, which is the text the model reads security
- Tool “reply” rewrote its description, which is the text the model reads security
- Schema quality: 296 → 211 ▲ functional
- 30 Sept 26 0
- Tool “setup_infrastructure” rewrote its description, which is the text the model reads security
- Tool “account” rewrote its description, which is the text the model reads security
- 29 Sept 26 0
- Tool “setup_infrastructure” rewrote its description, which is the text the model reads security
- Tool “launch_campaign” rewrote its description, which is the text the model reads security
- Tool “account” rewrote its description, which is the text the model reads security
- Schema quality: 265 → 294 ▼ functional
- “launch_campaign” reworded the description of “sendWindow” cosmetic
- “launch_campaign” reworded the description of “timezone” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.coldrig.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=coldrig.dev | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a1832edf515b745f13873ca1decbf658 |
| SANs: coldrig.dev, api.coldrig.dev, *.api.coldrig.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.coldrig.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| coldrig.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.coldrig.dev/.well-known/oauth-protected-resource/mcp", scope="coldrig"
Bearer resource_metadata="https://api.coldrig.dev/.well-known/oauth-protected-resource/mcp", scope="coldrig" | Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://api.coldrig.dev/.well-known/oauth-protected-resource/mcp", scope="coldrig" |
Protected resource metadata
| Document | https://api.coldrig.dev/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.coldrig.dev/mcp |
| Authorisation server | https://api.coldrig.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.coldrig.dev/mcp | Auth required | 401 | |
| http (plaintext) | http://api.coldrig.dev/mcp | HTTPS enforced | 301 | https://api.coldrig.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account ~243
Account overview: brand, plan, status, vertical ('crowdfunding' or null — set at signup), billingState, activationState, resource counts, usageCents, quota, deliverability (loop state: paused/throttled mailboxes, burning domains, auto-replacements, recentActions[]), and teardown (reclaim summary once canceled, else null). Billing is per-provisioned-mailbox on the live provisioned count: $49 platform + per mailbox, graduated: 1-5 at $10, 6-20 at $8, 21+ at $7; 5-mailbox minimum ($99 at 5); the billed quantity tracks the real provisioned count (deprovision lowers it). activationState is the HONEST send state — trust it over 'sent' counts: 'active' = real sending live; 'pending_provisioning' = paid but infrastructure still being armed, sends shown are sandbox previews that DON'T leave; 'capacity_pending' = provisioning held at a spend limit; 'screening_hold' = account under review; 'sandbox' = demo/free. Use metrics for counts, infrastructure_status for per-mailbox health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ack_message ~124
Acknowledge a message by id (from list_messages or infrastructure_status's messages[]) — sets it read so it stops surfacing as unacked. THIS IS THE ONLY THING THAT SETS readAt: reading or listing messages never marks them, so a message stays unacked until you call this explicitly. Idempotent: acking an already-acked id returns success with no second effect, never an error. 404 if the id doesn't exist for this tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | The message id, from list_messages or infrastructure_status's messages[]. |
No output schema declared.
No examples provided.
activity ~108
Unified activity feed: campaign events (sent/reply/bounce/...) merged with deliverability loop actions (pause/throttle/replace-domain). Cursor-paginated → { items[], nextCursor }; each item { id, kind:'event'|'deliverability', label, ts, target, detail }. Filters: kind, limit (default 50, max 200). Use inbox for replies only.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| kind | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
add_leads ~878
Add contacts to a running campaign. Inputs: campaignId, leads[] (same shape as launch_campaign: email, optional firstName, company, vars), listSource (REQUIRED on a crowdfunding account). Only an active or paused campaign of this account (404 if unknown; 400 if past its end date). Each new contact starts at step 1 on the campaign's own schedule, under every launch rule: a {{firstName}} or {{key}} the sequence uses must have a value on every new contact, or the call is refused (400) and nothing is added. Skipped and counted, never an error: an address already in this campaign (unchanged), an address on your suppression list (stored as suppressed, never emailed), an address repeated in the request. Adding never resumes a paused campaign; repeating the call adds nothing; a campaign holds at most 5000 contacts. A trial account can launch up to 5 test campaigns in any 24 hours, each holding up to 100 contacts, which is enough for a small test. Both are limits of the trial, not of Coldrig: going live removes them. Nothing in a campaign launched on the trial is ever really sent: when the account goes live, the emails it still has waiting are canceled and it cannot be resumed or added to, so launch a new campaign to send real email. People who already got this email are skipped: a contact is left out, never stored or emailed, when another campaign of this account has sent them, or still has waiting for them, an email with the same subject and body as this campaign's first email, as written before {{tokens}} are filled in (spacing differences do not count). A trial's test email counts only while the account is still on the trial, and the built-in demo campaign never counts. alreadyEmailed in the answer is how many were skipped (anyone also on your suppression list is counted there, not in suppressed): tell the person in plain words, for example "skipped 12 people who already got this email". To include them, send includeAlreadyEmailed: true on the launch itself (previewOnly…
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | The campaign id returned by launch_campaign. |
| includeAlreadyEmailed | boolean | – | Optional. true also stores and emails the contacts who already got this campaign's first email from another campaign of this account; without it they are skipped and counted in alreadyEmailed. |
| leads | array | yes | – |
| listSource | string | – | Where this lead list came from, in a sentence (e.g. "our own past-donor CRM export"). REQUIRED on a crowdfunding account: an add with no source, or "unknown", is refused (400) — cold lists are allowe… |
| repeatOf | string | – | Optional. Send it only to repeat a campaign on purpose: the existingCampaignId that a 409 duplicate_campaign refusal of this add named. Accepted once, and only while it names the most recent campaign… |
No output schema declared.
No examples provided.
campaign_results ~252
Outcome counts for ONE campaign. Input: campaignId (from launch_campaign). Returns { campaignId, sent, reply, bounce, complaint, unsubscribe, failed, soft_bounce, auto_reply } — event counts, bounce = HARD only, soft_bounce separate, opens not tracked; auto_reply = automatic replies such as out-of-office, which are NOT replies (never in reply, replied, replyRate or positiveReplies; they never stop a sequence) — plus unique-contact numbers: contacts (leads in the campaign), contacted (leads sent at least once), replied (leads that replied), replyRate (replied / contacted, 0..1), positiveReplies (replied leads marked interested or meeting_booked via update_lead), and perStep[] of { step, sent, contacted, replied, bounce, unsubscribe } ordered by step (a reply, bounce or unsubscribe counts toward the lead's latest sequence step sent before it). 404 if unknown. To see each contact's own timeline use list_leads with campaign, then thread. Use metrics for account-wide totals, list_campaigns for every campaign at once.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | The campaign id returned by launch_campaign. |
No output schema declared.
No examples provided.
configure_byo_domain ~496
Register or advance a BYO domain/mailbox intake. action = register (needs domain + domainRelationship: fresh_standalone|subdomain_of_primary|is_primary — runs pre-flight scan + abuse gate + reputation ladder, returns starting byoStatus) | poll_dns (needs id — re-checks DNS delegation, advances pending_dns -> active, or -> abandoned after 7 idle days) | acknowledge_consent (needs id + acknowledged:true — required before a primary domain can proceed past pending_consent; documents informed consent, does not remove exposure) | request_managed_mailboxes (needs id + count — platform-provisioned mailboxes on an ALREADY-ACTIVE domain; every response carries a billing projection { provisionedAfter, projectedMonthlyCents, formula }; quoteOnly:true previews without provisioning) | connect_mailbox (needs id + email + transport — declares an EXISTING OAuth/SMTP+IMAP connection, bypassing provisioning; transport is smtp | gmail_api | ms_graph, each with its own credential fields).
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledged | boolean | – | Required (must be true) for acknowledge_consent — SPEC.md §20.4's separate, unbundled risk acknowledgment. |
| action | string | yes | – |
| count | integer | – | Required for request_managed_mailboxes — how many platform-provisioned mailboxes to attach. |
| domain | string | – | Required for register. |
| domainRelationship | string | – | Required for register: fresh_standalone | subdomain_of_primary | is_primary. |
| string | – | Required for connect_mailbox — the existing mailbox address. | |
| id | string | – | Required for poll_dns/acknowledge_consent/request_managed_mailboxes/connect_mailbox — the domainId from register. |
| personaSlug | string | – | Optional for request_managed_mailboxes — defaults to a slug of the domain. |
| quoteOnly | boolean | – | Optional for request_managed_mailboxes — true previews the new mailbox count + projected monthly price WITHOUT provisioning (SPEC §18 quote-before-add). |
| transport | – | – | Required for connect_mailbox — { kind: 'smtp', host, port, secure, user, pass } | { kind: 'gmail_api', clientId, clientSecret, refreshToken } | { kind: 'ms_graph', mode: 'delegated'|'app_only', tenan… |
No output schema declared.
No examples provided.
configure_dashboard ~205
Write a saved dashboard view. action = create (needs name+layout) | update (needs id+rev+layout; optional name renames) | promote (id → default) | delete (id). update is rev-CAS: a stale rev returns { currentRev, currentLayout } to rebase and retry. Optional note. Read the current rev+layout via get_dashboard first.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| id | string | – | Required for update/promote/delete. |
| layout | object | – | Required for create/update. |
| name | string | – | Required for create. Optional for update — pass it to rename the view; omit to leave the name unchanged. |
| note | string | – | Optional human-readable note recorded alongside this edit (edited_by_note). |
| rev | integer | – | Required for update — the rev this edit is based on; stale vs. the view's CURRENT rev returns a structured conflict with currentRev/currentLayout to rebase onto. |
No output schema declared.
No examples provided.
configure_webhook ~272
Manage an outbound webhook subscription. action = create (needs url + eventTypes: reply|bounce|soft_bounce|complaint|unsubscribe; optional secret/active) | update (needs id + one changed field; active:true re-enables an auto-disabled one, active:false pauses; secret rotates) | delete (needs id). create/rotate return the HMAC signing secret ONCE. URLs must be https to a public host (private/metadata IPs rejected). Deliveries are signed X-Coldrig-Signature: sha256=HMAC-SHA256(secret, raw body).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| active | boolean | – | Optional. On update, active:true re-enables an auto-disabled subscription; active:false pauses delivery. |
| eventTypes | array | – | Required for create: which events to push (reply | bounce | soft_bounce | complaint | unsubscribe). |
| id | string | – | Required for update/delete. |
| note | string | – | Ignored placeholder for symmetry; webhooks record no provenance note. |
| secret | string | – | Optional signing secret (>=16 chars). Omit on create to have one generated; pass on update to rotate. |
| url | string | – | Required for create. HTTPS endpoint; private/link-local/metadata IPs are rejected. |
No output schema declared.
No examples provided.
contact_operator ~248
Reach a human operator for anything list_messages/infrastructure_status cannot answer (a stuck vendor issue, a billing question, an account-level ask). Inputs: body (1-2000 chars), urgency (normal|needs_human, default normal). Files a ticket, notifies the operator; returns { ticketId, note, deduplicated }. Works in every account state a token authenticates in (dunning-suspended, canceling, canceled) — admin-terminated is the one exception, rejected at auth. The reply arrives as a message on THIS account (poll list_messages/infrastructure_status — no reply-fetch call). Sending the IDENTICAL body+urgency again within an hour returns the SAME ticketId, no second ticket/alert (`deduplicated: true`). TEXT MATCH, NOT AN INTENT MATCH: a genuinely new message with identical wording collapses the same way, silently — vary the wording (or raise urgency, always a new ticket). `needs_human` bypasses the ~10-min ops-email throttle. Rate-limited to 5/hour/tenant — a 429 names retryAfter (seconds).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| urgency | string | – | – |
No output schema declared.
No examples provided.
get_byo_domains ~157
List your BYO (bring-your-own) domains, or (with id) one domain's full intake detail. No id → [{ domainId, domain, isPrimary, dnsMode, byoStatus, breakerTier, reputationBranch, mailboxCount }]. With id → adds the pre-flight scan result, abuse-gate verdict, and consent-acknowledgment status. byoStatus progresses pending_kyc|pending_consent|pending_dns → active (or rejected/abandoned). Use configure_byo_domain to register a new one or advance it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Omit to list every BYO domain; pass an id for that domain's full intake detail (scan result, abuse verdict, consent status). |
No output schema declared.
No examples provided.
get_dashboard ~99
Read saved dashboard views. No id → list all: [{ id, name, isDefault, rev, editedBy }]. With id → that view's full layout + rev (pass this rev as the CAS base to configure_dashboard update). Views are both agent- and human-editable; write them with configure_dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Omit to list every saved view (summary); pass a view id for its full layout + rev. |
No output schema declared.
No examples provided.
get_webhooks ~109
List your outbound webhook subscriptions, or (with id) one subscription plus its recent delivery + attempt log. No id → [{ id, url, eventTypes, active, status, disabledReason, consecutiveFailures }]. With id → { subscription, recentDeliveries[], recentAttempts[] }. Secrets are never returned on reads — they are shown once at create/rotate.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Omit to list every subscription; pass an id for that subscription plus its recent delivery + attempt log. |
No output schema declared.
No examples provided.
inbox ~160
Unified reply inbox across mailboxes. Cursor-paginated → { threads[], nextCursor }; each row: threadId, campaignName, leadEmail, subject, mailboxEmail, label, lastEventType, markStatus. Filters: mailbox, campaign, label, read, includeNonreply (threads whose last event is a bounce, complaint or automatic reply such as out-of-office; default true), archived (exclude|include|only). Use thread for one thread's history.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | string | – | – |
| campaign | string | – | – |
| cursor | string | – | – |
| includeNonreply | boolean | – | – |
| label | string | – | – |
| limit | integer | – | – |
| mailbox | string | – | – |
| read | boolean | – | – |
No output schema declared.
No examples provided.
infrastructure_status ~252
Warmup + provisioning progress per mailbox. Returns { domains, mailboxes, sendReady, mailboxHealth[], messages[], nextSteps }. New mailboxes ramp-limit server-side: 5 sends/day week 1, 40/day week 4 — dailyCap/sentToday show real capped sending from day 1, never zero. Per-mailbox `sendReady` is a FULLY-RAMPED flag, NOT a send gate — below-ramp mailboxes still send, capped at their own dailyCap; read dailyCap/sentToday for capacity. Top-level `sendReady` is the AND across ALL mailboxes (true once every one is ramped) — for one mailbox's capacity use its own flag. Each mailbox carries delivStatus (healthy/throttled/paused), complaint/bounce/softBounce rates; vendorReputationScore/vendorPlacementRate are VENDOR-REPORTED, null when unmeasured. Vendor-pool warmup is FEED-INVISIBLE by design. `messages[]` previews 5 unacked notices (severities: list_messages); reading never marks read. `nextSteps` names the next action (see setup_infrastructure). Use account/metrics for rollups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
label_thread ~102
Set or clear a triage LABEL on an inbox thread — the same chip the dashboard shows. Inputs: threadId, label (string; pass label:null to clear). Distinct from mark (read/unread/archived state): a label is a free-form category, not a read flag. Filterable via inbox's label param.
| Name | Type | Req | Description |
|---|---|---|---|
| label | – | – | – |
| threadId | string | yes | The thread id, e.g. from inbox() or campaign events. |
No output schema declared.
No examples provided.
launch_campaign ~2,438
Create and activate a campaign on a lead list. You supply name, offer, leads[], sequence[] (per step: subject, body, delayDays — subject is REQUIRED on step 1; a LATER step may omit it to keep step 1's subject line [recommended], which resolves at launch to "Re: " + step 1's subject (unchanged if that already starts with "Re: "), or set one explicitly to change only that step's subject line — every later step is still sent In-Reply-To step 1, though some mail clients display a changed subject as a separate conversation), and optionally timezone, sendWindow, stopOnReply, listSource (one sentence on where the list came from — REQUIRED on a crowdfunding account, where a missing or "unknown" source is refused 400) — the platform does not write copy. Each step's `step` number must be unique within the sequence; a duplicate step number is refused (400) naming it. Subjects and bodies may use {{firstName}} and {{company}} (filled from each lead; firstName and company are both optional) plus your own {{key}} for any key every lead carries in its optional `vars` map (word-keys to one-line strings, e.g. vars:{ icebreaker:"..." }; a key may not be firstName or company). A value is inserted once as plain text. A launch is refused (400), naming the token and how many leads lack it, if a subject or body uses {{firstName}} or a {{key}} that any lead has no non-empty value for — no fallback word is invented; it is also refused if any subject or body uses a {{…}} that is not one word, a single-brace form of a known token such as {firstName} or {company} (a typo for the double-brace form — it would otherwise reach the recipient unsubstituted), or a run of 3 or more consecutive `{` or `}` anywhere (e.g. {{{firstName}}} or a lopsided run like {{{firstName}} — it would otherwise reach the recipient with stray braces attached). The send window is evaluated in `timezone` (IANA, e.g. America/New_York; default UTC) — set it to your recipients' zone. sendWindow is { startHour, endHour, days?…
| Name | Type | Req | Description |
|---|---|---|---|
| endBy | string | – | Optional fixed end date, as an ISO 8601 instant with a zone. From then on nothing more in this campaign sends: every step still waiting is skipped and recorded as a 'failed' event with reason campaig… |
| idempotencyKey | string | – | Optional idempotency key: resend the SAME key when retrying this call so a dropped-response retry is not applied twice (no duplicate campaign/provision/send). |
| includeAlreadyEmailed | boolean | – | Optional. true also stores and emails the contacts who already got this campaign's first email from another campaign of this account; without it they are skipped and counted in alreadyEmailed. |
| leads | array | yes | – |
| listSource | string | – | Where this lead list came from, in a sentence (e.g. "our own past-donor CRM export"). REQUIRED on a crowdfunding account: a launch with no source, or "unknown", is refused (400) — cold lists are allo… |
| name | string | yes | – |
| offer | string | yes | – |
| previewOnly | boolean | – | Optional. true = a dry run: every launch check runs and you get back the rendered subject and body of every step for the first three leads plus the counts a launch would report, and NOTHING is create… |
| repeatOf | string | – | Optional. Send it only to repeat a campaign on purpose: the existingCampaignId that a 409 duplicate_campaign refusal of this launch named. Accepted once, and only while it names the most recent campa… |
| sendWindow | object | – | Integer hours 0-23 (endHour inclusive: the last hour a send may start in) and weekdays, evaluated in `timezone`. Each field you omit (or all of them, by omitting sendWindow) gets the recommended {"st… |
| sequence | array | yes | – |
| stopOnReply | boolean | – | – |
| timezone | string | – | IANA time zone the send window is evaluated in — set it to your recipients' zone. Default UTC. |
No output schema declared.
No examples provided.
list_campaigns ~72
List every campaign at once: [{ campaignId, name, status, counts{sent,reply,bounce,complaint,unsubscribe,failed,soft_bounce,auto_reply} }], newest first — no per-campaign lookup needed. Use campaign_results for one campaign's counts, metrics for account-wide totals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_leads ~189
List/export leads with their contact-level disposition, cursor-paginated. Returns { leads[], nextCursor }; each row: leadId, email, firstName, company, campaignId, campaignName, globalStatus, interestStatus, notes, tags, suppressed, lastEventType, lastEventTs, createdAt, threadId (that lead's conversation: pass it to thread for the lead's timeline; null if nothing was scheduled). Filters: campaign, interestStatus, suppressed, replied. This IS the export surface — paginate to dump the full book of business as JSON (no separate CSV endpoint). Use update_lead to write disposition, suppress_lead to opt an address out.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | – | – |
| cursor | string | – | – |
| interestStatus | string | – | – |
| limit | integer | – | – |
| replied | boolean | – | – |
| suppressed | boolean | – | – |
No output schema declared.
No examples provided.
list_messages ~224
List this tenant's system + operator messages (a retryable setup step, a credential going live, an operator notice), cursor-paginated. Unacked messages sort first (newest within that group), then acked (also newest first). Returns { messages[], nextCursor }; each: id, kind, severity ('info' = resolves on its own | 'action_required' = act and it progresses | 'operator_pending' = platform stopped, only an operator can restart it, retrying the SAME call then works | 'terminal' = platform stopped, only a human can move it, do NOT retry), body, actionHint, source (system|operator), createdAt, readAt. `readAt` is set ONLY by ack_message — listing never marks messages read, so a null readAt does not mean never seen, only not yet acknowledged. Use ack_message to stop one resurfacing. infrastructure_status inlines the newest 5 unacked messages; this is the full paginated surface.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
mark ~121
Set a thread's READ-STATE for inbox triage. Inputs: threadId, status = 'read' | 'unread' | 'archived' (archived hides it from the default inbox; refetch with inbox archived='include'/'only'). Returns { marked: true }. 404 if unknown. This is the read/archive flag ONLY — use label_thread for a triage label chip, reply to respond.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
| threadId | string | yes | The thread id, e.g. from inbox() or campaign events. |
No output schema declared.
No examples provided.
metrics ~100
Account-wide outcome totals across ALL campaigns: { sent, reply, bounce, complaint, unsubscribe, failed, soft_bounce, auto_reply } — the same event counts as campaign_results but summed tenant-wide (no per-contact fields) (bounce = hard only, opens not tracked; auto_reply = automatic replies such as out-of-office, never counted in reply). Use campaign_results for one campaign, list_campaigns per-campaign, or account for billing/quota.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause ~255
Pause ONE campaign: its status → 'paused' and nothing more in it sends; its remaining steps are HELD, not cancelled (already-sent mail is unaffected) — call resume to continue it. Input: campaignId. Returns { paused: true }. 404 if not found. Add leadEmails to stop ONLY those leads in this campaign instead (e.g. a donor who already gave): their remaining steps are cancelled for good (resume does not bring them back), the campaign keeps running for everyone else, and nobody is suppressed — returns { paused: false }. Matching ignores capitalisation; if any address is not a lead of this campaign, nothing is stopped and the call is refused (404) naming them. Use pause_all to pause every active campaign at once.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | The campaign id returned by launch_campaign. |
| leadEmails | array | – | Optional. Stop ONLY these leads in this campaign (any capitalisation): their remaining steps are cancelled, the campaign keeps running for everyone else, and nobody is added to the suppression list.… |
No output schema declared.
No examples provided.
pause_all ~70
Pause EVERY active campaign for the tenant at once (each active status → 'paused'; nothing more in them sends, and their remaining steps are held). No inputs. Returns { pausedAll: true }. Use pause to pause a single campaign by id, and resume (one call per campaign) to continue one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_campaign ~283
Plan a dated outreach campaign (for example a fundraising drive) and get its price. Read-only: nothing is booked, charged or changed. Inputs: contacts, campaignStart (first campaign day, YYYY-MM-DD, UTC), campaignDays, bookingDate (the day you would book, normally today), and optionally domainsAlreadyHeld (default 0; infrastructure_status shows `domains`) and listIsOwnOptIn (your own opted-in donors; default false). Returns { mailboxes, domainsToBuy, bookBy, advanceStartOn, safeReach, priceCents, warnings[] }. safeReach is how many contacts the warm-up ramp can safely reach if you book on bookingDate; the price is for that many. warnings: over_60_mailboxes (above the 60-address self-serve ceiling), late_booking (safeReach is below contacts), own_list_cheaper_on_esp (an opted-in list may cost less on an email-service provider). A bookingDate after the last campaign day is refused 400. Campaign checkout and booking are not available yet: to book, contact support (contact_operator).
| Name | Type | Req | Description |
|---|---|---|---|
| bookingDate | string | yes | – |
| campaignDays | integer | yes | – |
| campaignStart | string | yes | – |
| contacts | integer | yes | – |
| domainsAlreadyHeld | integer | – | – |
| listIsOwnOptIn | boolean | – | – |
No output schema declared.
No examples provided.
remove_mailboxes ~296
Downgrade: release your N NEWEST live mailboxes, lowering the billed quantity. Inputs: count, acknowledged (must be true — release is immediate but irreversible; no mid-cycle credit, lower price starts next renewal, minimum 5 mailboxes/$99). Returns { releasedCount, failedCount, unreleased, billing, deduplicated }. `count` is RELATIVE (that many MORE, not a fleet target). ALWAYS pass an idempotencyKey: the FIRST call under a key fixes WHICH mailboxes to release; a later call with the SAME key can only finish that set. `releasedCount` can be less than `count` — `failedCount` names how many the vendor refused (still live, billed; `unreleased` lists them). Resend with the same key until `failedCount` is 0. `deduplicated: true` = NO new work — an earlier recorded outcome under that key was replayed. A genuinely NEW downgrade needs a NEW key. 409 = a release already running; re-check infrastructure_status before retrying. To ADD mailboxes use setup_infrastructure or configure_byo_domain.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledged | boolean | yes | – |
| count | integer | yes | – |
| idempotencyKey | string | – | Optional idempotency key: resend the SAME key when retrying this call so a dropped-response retry is not applied twice (no duplicate campaign/provision/send). |
No output schema declared.
No examples provided.
reply ~309
Send a reply on an existing thread, from the mailbox that sent it. Inputs: threadId, body. Returns { messageId, deduplicated }. A reply is real send volume, governed like campaign sends: counts against the mailbox daily cap, and is REFUSED (never silently dropped) when the recipient is suppressed, the mailbox is deliverability-paused, or the cap is used up — a refusal returns { error, code: send_blocked, reason: suppressed|mailbox_paused|daily_cap_reached, retryable }; retryable (cap) clears next daily rollover, non-retryable does not — stop retrying, do not loop replies to manufacture volume. Idempotent: identical retries collapse to one send — pass a stable idempotencyKey (else a body hash is used, matched only 10 minutes) so a dropped-response retry cannot double-send. `deduplicated: true` = NO new email sent; `messageId` is from an earlier matching send. Pass a key, or vary the body, if a repeat must genuinely go out. 404 if no sending mailbox is on record for the thread.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| idempotencyKey | string | – | Optional idempotency key: resend the SAME key when retrying this call so a dropped-response retry is not applied twice (no duplicate campaign/provision/send). |
| threadId | string | yes | The thread id, e.g. from inbox() or campaign events. |
No output schema declared.
No examples provided.
resume ~210
Resume ONE paused campaign: its status → 'active'. Input: campaignId. Returns { resumed: true }. Only a paused campaign of this account can be resumed: 404 if unknown, refused (400) if it is not paused, is past its end date, or is a trial campaign on an account that has gone live. On a paid account, resuming sends nothing by itself: the held steps go out through the normal schedule, inside the send window and the daily caps. A step whose time passed while paused goes out at the next allowed slot, one step at a time per lead: the step after it still waits its own delayDays from when that one actually sent, so a pause never puts two steps in one day. Leads stopped on their own stay stopped: stopped with pause leadEmails, replied, unsubscribed, bounced or suppressed. Steps a campaign lost while it was paused before this tool existed are not restored.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | The campaign id returned by launch_campaign. |
No output schema declared.
No examples provided.
setup_infrastructure ~357
Provision sending infra: buy lookalike domains, create mailboxes, start warmup. Inputs: brand, primaryDomain, domains + inboxesEach (or distribution), persona, physicalAddress, senderIdentity. Billing is per provisioned mailbox; quoteOnly:true previews cost first. `domains`/`inboxesEach` are the infra you want to HAVE, not an amount to add — a repeat call never buys twice; each ordinal 0..domains-1 fills to its own count. Mailbox addresses are DETERMINISTIC from persona+ordinal+slot — keep persona unchanged on a retry. `registerDomains:true` is required consent before any NEW domain purchase; omitting it on a buy call is refused 400 registrar_optin_missing (self-correct by resending true, never an operator escalation) — also needs `registrant`, unless already on file. NO background retry exists: a `provisioning` result (pending|capacity_pending) needs YOU to retry to progress; capacity_pending needs contact_operator instead. Returns { jobId, billing, provisioning?, nextSteps }.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | – |
| distribution | array | – | – |
| domains | integer | yes | – |
| idempotencyKey | string | – | Optional idempotency key: resend the SAME key when retrying this call so a dropped-response retry is not applied twice (no duplicate campaign/provision/send). |
| inboxesEach | integer | – | – |
| persona | string | yes | – |
| physicalAddress | string | yes | – |
| primaryDomain | string | yes | – |
| quoteOnly | boolean | – | – |
| registerDomains | boolean | – | – |
| registrant | object | – | – |
| senderIdentity | string | yes | – |
No output schema declared.
No examples provided.
submit_feedback ~121
Send private feedback to the Coldrig founders about how the product is working for you. Inputs: score (integer 0-10, optional) and/or text (1-2000 chars, optional); at least one is required. It is stored privately and emailed to the founders, never published, and it opens no support ticket and changes nothing on your account (use contact_operator for a problem that needs an answer). Each call is a separate submission. Returns { feedbackId, received }.
| Name | Type | Req | Description |
|---|---|---|---|
| score | integer | – | – |
| text | string | – | – |
No output schema declared.
No examples provided.
suppress_lead ~154
Permanently suppress an email address tenant-wide (every current and future campaign) — the manual/free-text 'stop emailing me' path for opt-outs the strict typed-unsubscribe matcher misses. Inputs: email, reason (fixed 'manual' — the only value this tool honestly claims; bounce/complaint/unsubscribe are recorded automatically elsewhere), note (accepted, not persisted). Cancels every pending send + marks every campaign-lead row 'suppressed'. Last-write-wins: re-suppressing a bounce/complaint/unsubscribe row relabels its reason to 'manual'. There is no un-suppress tool.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| note | string | – | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
thread ~141
Full message history for ONE thread. Input: threadId (from inbox). Returns { threadId, campaignId, leadId, leadEmail, mailboxEmail (null before first send), messages[] }, each message { type (sent/reply/auto_reply/bounce/...; auto_reply = an automatic reply such as out-of-office), step (the sequence step of a sent message, null otherwise), ts, messageId, metadata }, oldest first. 404 if unknown. Use inbox to LIST threads; reply to respond; mark/label_thread to triage.
| Name | Type | Req | Description |
|---|---|---|---|
| threadId | string | yes | The thread id, e.g. from inbox() or campaign events. |
No output schema declared.
No examples provided.
update_lead ~169
Record what you learned about a contact (their reply, your triage) as a durable, contact-level disposition — keyed by email, visible across every campaign that lists them. Inputs: email, interestStatus (none|interested|meeting_booked|not_now|not_interested|bad_fit|out_of_office|wrong_person — a server-enforced enum; 'do not contact' is NOT a member, use suppress_lead instead), notes, tags (free-form). A PARTIAL patch — only the fields you pass are changed; at least one of interestStatus/notes/tags is required. Filterable via list_leads.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| interestStatus | string | – | – |
| notes | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.YS-projectcalc/agent-cold-email MCP server?
io.github.YS-projectcalc/agent-cold-email is a hosted endpoint at https://api.coldrig.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.coldrig.dev
claude mcp add --transport http ys-projectcalc-agent-cold-email 'https://api.coldrig.dev/mcp'
What is the io.github.YS-projectcalc/agent-cold-email MCP server?
io.github.YS-projectcalc/agent-cold-email is an MCP server listed in the public MCP registry as io.github.YS-projectcalc/agent-cold-email. Coldrig, cold-email infra run by your agent: 28 MCP tools, live sending, free sandbox, from $99/mo. This page covers its hosted endpoint (https://api.coldrig.dev/mcp).
Is the io.github.YS-projectcalc/agent-cold-email MCP server safe to use?
io.github.YS-projectcalc/agent-cold-email scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.YS-projectcalc/agent-cold-email MCP server expose?
io.github.YS-projectcalc/agent-cold-email exposes 32 tools: setup_infrastructure, infrastructure_status, launch_campaign, campaign_results, metrics, and 27 more. Their descriptions and schemas cost roughly 9,214 tokens of context every time the server is loaded.
Does the io.github.YS-projectcalc/agent-cold-email MCP server require authentication?
Yes. io.github.YS-projectcalc/agent-cold-email asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.YS-projectcalc/agent-cold-email MCP server still maintained?
io.github.YS-projectcalc/agent-cold-email is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.YS-projectcalc/agent-cold-email MCP server?
VerifyMCP ran 5 checks on io.github.YS-projectcalc/agent-cold-email, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about io.github.YS-projectcalc/agent-cold-email: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.