MCP App Store
by KeenEthics
Ambush icon

Ambush MCP Server for ChatGPT

By Ambush

Overview

Give your agent a live feed of the world. Describe what you care about, like “any news that could impact the price of NVIDIA” or “outages at one of our cloud vendors,” and Ambush watches hundreds of thousands of sources around the clock, only alerting you when something important happens. Ambush routes events in real time to your agent in ultra low latency, triggering Dot to wake up or triggering workflows in ChatGPT Work.

How to connect

  1. ChatGPT: Open the Ambush listing in the ChatGPT app directory and choose Connect. ChatGPT listing Ambush exposes 13 tools here.

Tools

add_email_destination

ChatGPT
Add an email address the user wants alerts at. Ambush emails it a Confirm alerts button and a 6-digit code, both good for 10 minutes. It turns active when the user taps the button, or when you pass the code they read you to verify_email_destination. Tell the user to check their inbox, then check list_channels or this tool's status before saying alerts will arrive there, and send a stream to it with route_feed_channel using emission_channel_id. Adding an address that is already confirmed returns it active. Ask only for the address the user wants; never invent one.

create_feed

ChatGPT
Create a feed from a monitoring prompt. To receive its future emissions in this MCP client, subscribe to feed.emission.created using the returned feed_id and webhook delivery. An explicit name is optional. Every accepted headline is delivered the way the owner's profile asks (by default translated into English and cleaned of emojis, tags and markup); pass headline_output to override that for this feed with language (a BCP 47 tag or 'original') and/or clean (boolean), at least one of them. Include post_processing to transform every future accepted event after that and before delivery.

delete_feed

ChatGPT
Permanently delete an owned feed. This is destructive and should only be called after the user confirms the feed ID.

get_feed

ChatGPT
Get one owned feed, including its current prompt revision, output channels, recent emissions, and usage.

list_channels

ChatGPT
List the authenticated user's preconfigured Slack, webhook, Telegram, iMessage, and mobile push destinations. Use a channel whose install status is connected and destination_status is active with route_feed_channel. Labels mask phone numbers, email addresses, and device names, and webhook endpoint paths and internal metadata are redacted; credentials are managed in Ambush and are never requested through this tool.

list_emissions

ChatGPT
List the complete emission history for one owned feed, newest first. Follow next_cursor to fetch another page.

list_feeds

ChatGPT
List feeds owned by the authenticated user, newest first. Follow next_cursor to fetch another page. The first page also lists "Streams sent to you from the Ambush app": not a news stream, but the channel the user sends you streams through from the Ambush app.

list_hosted_streams

ChatGPT
List the streams Ambush runs once for everyone, such as service status pages and security alerts. Subscribe to one's alerts with its feed_id the same way as an owned feed's; the other tools take only owned feeds.

list_near_misses

ChatGPT
Show recent news considered for a stream you own but not selected as a match, newest first, with up to 30 days of available history. Each item includes prompt_revision_id for the saved prompt used in its review, which may predate stream edits. Pass feed_id and optional limit (up to 50, default 20; larger values are capped). Pass next_cursor as cursor to fetch the next page; null means the end. Scores and explanations are not included.

preview_feed

ChatGPT
Before create_feed, see what a draft prompt would have caught and how many alerts to expect, to tune it with the user. Returns up to 10 of the newest headlines from the lookback (7d unless lookback says 14d, 30d or 60d) that Ambush's relevance filter keeps for the prompt, the way a live stream's would be judged, and alerts_per_day from the last week of news (a guide: a week's alerts move by up to half either way; alerts_at_most means the filter kept none it was shown, so it is an upper bound). When coverage is not supported there are no headlines, because Ambush can't watch for what the prompt asks; tell the user coverage_summary. too_broad means create_feed would refuse the prompt. Nothing is saved.

resend_email_verification

ChatGPT
Send a new confirmation email for an email destination that isn't confirmed yet, at most once a minute. The previous button and code stop working.

route_feed_channel

ChatGPT
Attach a preconfigured delivery channel to an owned feed. Each future accepted event is processed and enqueued to this destination immediately; this does not poll or retroactively deliver earlier emissions. Repeating the same route safely reactivates it.

submit_feedback

ChatGPT
Tell Ambush what is and isn't working, whenever you notice. About a stream's alerts, with its feed_id: irrelevant_alerts (should not have been sent), missed_news (news it should have caught; check list_near_misses first), duplicate_alerts (one story alerted more than once), late_alerts (too late to be useful), alert_formatting (wrong headline, translation, or post-processed output), working_well. About Ambush itself, feed_id optional: missing_source (an outlet Ambush doesn't watch), tool_error (a call failed or behaved unexpectedly), missing_capability (something the user wanted that Ambush can't do), documentation (wrong or unclear docs). Or other. Cite alerts in emission_ids (with feed_id) and news in news_item_ids, up to 50 each, using only IDs Ambush returned. Ambush reads feedback to improve the product; it changes nothing, so suggest update_feed when a prompt itself should change. Never include credentials.

update_feed

ChatGPT
Update an owned feed's prompt, name, status, headline output override, or event-time post-processing. This overwrites the selected settings and changes future monitoring or delivery; existing alerts are not deleted. headline_output replaces this feed's override of the owner's profile: language (a BCP 47 tag or 'original' for the source's language) and/or clean (boolean, strip emojis, tags and markup), at least one of them; fields left out follow the owner, and null removes the override entirely. post_processing runs once whenever a future event is accepted; set it to null to remove it. Set status to paused to pause the feed and active to resume it.

update_feed_channel_route

ChatGPT
Set an existing feed-to-channel route active or inactive for future deliveries. Muting permanently cancels pending deliveries and attempts for this route; unmuting does not restore them. The channel credential and feed are not deleted.

verify_email_destination

ChatGPT
Confirm an email destination with the 6-digit code from its confirmation email, when the user reads it to you instead of tapping the button. Pass the emission_channel_id from add_email_destination. A wrong code counts against five attempts; after that, or after 10 minutes, use resend_email_verification. Never guess a code.

Capabilities

Writes

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/ambush"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/ambush)