IntelMCP Get started

Changelog

What changed, and when

Changes you can notice as a user, newest first. Fixes that change nothing visible are left out.

    • One alert per event. Reposts and copies of the same event within 72 hours are grouped into an incident, and matches are marked new, update or repeat. An update is a later post that adds something: an identifying indicator or a country new to the event, a step up in exploitation (proof of concept, then exploited), a reply in the same channel, a channel posting it a second time, or a match for another of your rules. Exploitation terms are recognised in English, Russian, Ukrainian, Arabic, Persian and Hebrew.
    • Webhooks skip repeats, carry Standard Webhooks signatures beside X-TI-Signature, and say what matched, when it was posted and how an update joined its incident. Failed sends are retried for about an hour; a destination that keeps failing is paused. Only public HTTPS targets are accepted. See webhooks.
    • A shorter setup. Set up monitoring asks two questions, tests draft rules against recent history with their expected alerts per day, and creates everything with one approval, including matches from the last 7 days.
    • Four guides. The connector menu lists Set up monitoring, Investigate, Dashboard and Triage matches, and the Claude Code plugin has all four as commands: /intelmcp:setup, /intelmcp:triage, /intelmcp:dashboard and /intelmcp:investigate.
    • Setup checks the volume: drafts that would bring more alerts than you can review are narrowed first, the newest matches are shown after saving, and running it again tunes what you have.
    • Matching: Arabic and Hebrew word rules match spelling variants and attached prefixes (=word leaves out the article); domain rules cover subdomains and email addresses at the domain; countries are recognised from flag emojis and country-code domains.
    • Channel requests say when a channel is already collected, and then no request is filed.
    • Matches show who else reported it: how many other posts carried the same event, and from which channels.
    • Forward tracing now finds the earliest post with the same wording, not only the chain of forwards.
    • Search: quoted phrases and -word hold in the default search mode too.
    • Rules created with history count those matches in their hit counts.
    • When a request asks for more results or a longer window than the plan allows, IntelMCP says what it used instead.
    • Subscriptions through Polar. If you sign in without a subscription, IntelMCP replies with a checkout link; if a subscription ended, the message says what happens to its data.
    • IntelMCP opens as a hosted MCP server at mcp.intelmcp.io: search and monitor public Telegram channels from Claude.
    • Sign in with Google or a one-time code sent to your email.
    • The setup interview and the dashboard as prompts, and a Claude Code plugin with /intelmcp:setup and /intelmcp:dashboard.
    • New rules can check recent history when they are created.
    • Only public chats are collected; messages deleted at the source are removed.
    • Account data is kept for 90 days after a subscription ends, then deleted; backups are encrypted.
    • This website, with the privacy policy, terms and refund policy.
    • Collection begins. The searchable history starts here.