Archived listing / no verified MCP endpoint/Finance

Market Triggers listing

No MCP endpoint is published. This listing is retained for reference.

Market Triggers is a planned market-event feed for AI agents. It watches up to 25 US tickers for 8-K filings, opening gaps, day moves, volume spikes and earnings-date changes, and says it will deliver events over MCP, webhooks or Discord. The service is waitlisted and early-stage, and the provider does not publish an MCP endpoint or an authentication method yet. The planned MCP tools are subscribe, list_events and ack.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.Official docs
No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Traders and small funds that already run an agent or bot and want market events pushed to it, once the waitlist opens.

  • Join the waitlist for an event feed covering up to 25 tickers.
  • Review the provider's public sample log of gaps, day moves, volume spikes and 8-K filings.
  • Plan a webhook or MCP delivery path around subscribe, list_events and ack.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Market Triggers documentationhttps://ab-market-triggers.agentbets.workers.dev/