TweetFeed for AI Agents
Connect Claude Desktop, ChatGPT, Cursor, Zed or any MCP client to the IOC feed (free, no auth)
Agents
MCP, Agent Skills and API discovery (free, no auth)
Fastest path: paste this line to your agent and it configures itself.
All three: free, no authentication, no rate limit for normal use, same IOC data.
Connect
MCP server
Remote Model Context Protocol server over HTTP JSON-RPC 2.0 (protocolVersion 2025-11-25).
Works with Claude Desktop, Claude Code, ChatGPT, Cursor, Zed and any SDK-based MCP client.
{
"mcpServers": {
"tweetfeed": {
"url": "https://mcp.tweetfeed.live/"
}
}
}
ChatGPT (connectors and deep research)
- In ChatGPT, go to Settings, Connectors, Create (or add a custom connector from Deep research).
- Paste
https://mcp.tweetfeed.live/. No authentication needed. - Ask a question. Every result carries a tweetfeed.live URL, so answers cite the feed.
The server exposes the search and fetch tools ChatGPT requires, alongside the typed tools below.
claude mcp add --transport http tweetfeed https://mcp.tweetfeed.live/Available tools
| Tool | Purpose |
|---|---|
query_iocs |
IOC rows for today, week or month; filter by user, tag, type (url, domain, ip, sha256, md5). |
check_url |
Is a URL or substring in the past 30 days? Case-insensitive match on type=url IOCs. |
check_ip |
Is an IPv4 or IPv6 address listed? 365 days plus archive, else 30-day substring match on type=ip. |
check_hash |
Is a file hash listed? 365 days plus archive, else 30 days. MD5 (32 hex) or SHA-256 (64 hex) auto-detected, hex only. |
list_recent_iocs |
IOCs added since a YYYY-MM-DD date, newest first. Optional type, tag; 30-day window. |
get_tag_info |
One tag: counts for today, week, month, year from counts.json, plus recent IOCs. |
get_trending |
Top tags and IOC-type split for today, week, month or year, from counts.json. |
enrich_ioc |
Use when the type is unknown: auto-detects it, then 365 days plus archive, else a 30-day substring scan. |
get_campaigns |
Last-30-day campaigns (AI-clustered), 2 sample IOCs each. Optional brand, min_confidence (low/medium/high), limit (1-50, default 10). |
get_campaign_iocs |
Header and rows of one campaign. Required campaign_id; optional type, limit (1-500, default 100). API docs. |
get_trends |
31-day volume by type, moving tags week over week, abused TLDs, new-vs-recurring ratio. |
search |
ChatGPT connector: one query (IOC, tag, campaign id, text) returns ioc:/tag:/campaign: ids with URLs, as structuredContent. |
fetch |
ChatGPT connector: full document for one search id. Returns {id, title, text, url, metadata}. |
get_feed_status |
Pipeline freshness (stale, age_seconds) and X-source coverage. No parameters. Check it when a lookup is empty. |
The tools above stay the filtered, size-bounded path. The server also exposes:
- MCP resources:
tweetfeed://status,tweetfeed://iocs/{time}/{type},tweetfeed://campaigns/{id}and more. - Read them with
resources/read: raw JSON of the matching document. - Three prompts (
triage_ioc,daily_brief,campaign_summary): slash commands in Claude Desktop and Claude Code that chain the tools.
curl -sX POST https://mcp.tweetfeed.live/ \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
Source: github.com/0xDanielLopez/tweetfeed-mcp · Server card: /.well-known/mcp/server-card.json
Agent Skills
For agents that consume Agent Skills Discovery (RFC v0.2.0) instructions instead of MCP tools. Each skill is a markdown file describing how to call the feed.
| Skill | Purpose |
|---|---|
tweetfeed-iocs |
Query the IOC feed with route pattern, filter taxonomy, common queries and gotchas. Drop-in for any Claude Code / Copilot-compatible harness. |
tweetfeed-ioc-lookup |
Exact-match lookup for one specific IOC over the full 365-day window plus the pre-365-day archive: first/last seen, reporters, optional AI context. |
tweetfeed-blocklists |
Ready-made plain-text blocklists (domains, hosts, AdGuard, IPs, RPZ, dnsmasq, URLs) for direct import into firewalls and DNS resolvers. |
tweetfeed-trends |
Community IOC trend analytics: daily volume, top-moving tags, abused TLDs, novelty ratio. |
tweetfeed-campaigns |
AI-clustered campaign groupings of the last 30 days, grouped by shared infrastructure or tag. |
Discovery index: /.well-known/agent-skills/index.json (includes sha256 content digest for integrity).
REST API
No MCP or skills harness? Call the public REST API directly: no key, no auth, CORS-enabled, JSON responses.
GET https://api.tweetfeed.live/v1/{time}/{filter1}/{filter2}
The API page is the reference: every parameter, the 10,000-row result cap and its truncation headers, conditional requests, and the campaigns, counts, trends and IOC-lookup endpoints.
Bulk data and discovery
For platforms that ingest files on a schedule instead of calling a tool per question.
Bulk data formats
Static bundles for SIEM/Threat Intelligence platforms and incremental sync. All regenerated every 15 minutes from the same pipeline that feeds the API and MCP server.
| Endpoint | Purpose |
|---|---|
/stix/manifest.json |
STIX 2.1 indicator bundles for the today/week/month windows. Details on Feeds. |
/taxii2/ |
TAXII 2.1 server over the same STIX data, for OpenCTI, ThreatQ and other TIPs. Details on the API page. |
/v1/since/<ISO8601> |
IOCs added after a timestamp, for incremental sync. Details on the API page. |
/rss/tag/<slug>.xml |
One RSS feed per active tag, to follow a single threat type. Details on Feeds. |
Discovery endpoints
Crawlers and agents can discover every integration from a single
HEAD https://tweetfeed.live/: the Link header carries
rel="api-catalog", rel="agent-skills", rel="mcp-server",
rel="service-doc" and rel="service-desc" (RFC 8288).
| Path | Format | Spec |
|---|---|---|
| /.well-known/api-catalog | application/linkset+json |
RFC 9727 |
| /.well-known/agent-skills/index.json | application/json |
Agent Skills Discovery RFC v0.2.0 |
| /.well-known/mcp/server-card.json | application/json |
MCP SEP-1649 draft |
robots.txt · Content-Signal |
text/plain |
contentsignals.org |
License
IOC data (feed rows, API responses, MCP tool outputs) is freely available; see the Terms of Service for license. No attribution required, no warranty. Source code for the MCP server: tweetfeed-mcp (MIT).
Frequently asked questions
Do I need an API key or an account?
No. The MCP server, the Agent Skills and the REST API are all open: no key, no sign-up, and no rate limit for normal use. The IOC data is CC0.
MCP server, Agent Skills or REST API - which one?
If your client speaks Model Context Protocol (Claude Desktop, Claude Code, ChatGPT, Cursor, Zed), use the MCP server: the agent gets 14 tools and chooses between them itself. If it consumes Agent Skills instructions instead, point it at the skills manifest. If it is a script, or an n8n, Make or Zapier workflow, call the REST API. All three read the same rows.
Which clients work with the MCP server?
Any client that speaks JSON-RPC 2.0 over HTTP at protocolVersion 2025-11-25. It is tested with Claude Desktop, Claude Code, Cursor and Zed, and implements the ChatGPT connector interface (search / fetch). Nothing gets installed: the server is remote, so a URL in the client config is all it takes.
How fresh is the data an agent sees?
The pipeline rebuilds every 15 minutes, and the MCP server, the REST API and the bulk files all read that same output. An agent asking twice in the same quarter of an hour gets the same answer.
Can I redistribute what the agent pulls?
The IOC data is free to reuse; the Terms of Service carries the license. No attribution required, no warranty. The MCP server source is MIT.