mcpbeat Sign in

Threads Search API MCP Server

answering

Threads Search API is answering right now. Last checked 4 min ago.

Search public Threads posts by keyword for AI agents: text, author, likes, replies, reposts.

Uptime history 8 days of history · worst day 99%
8 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
332 ms
Response time
average over 24h
API key
Access
streamable-http

Threads Search API missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add threads-search --transport http https://mcp.apify.com/?tools=sauliusautomatesit/threads-search-api
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "threads-search": {
      "url": "https://mcp.apify.com/?tools=sauliusautomatesit/threads-search-api"
    }
  }
}
~/.codex/config.toml
[mcp_servers.threads-search]
url = "https://mcp.apify.com/?tools=sauliusautomatesit/threads-search-api"
.cursor/mcp.json
{
  "mcpServers": {
    "threads-search": {
      "url": "https://mcp.apify.com/?tools=sauliusautomatesit/threads-search-api"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "threads-search": {
      "url": "https://mcp.apify.com/?tools=sauliusautomatesit/threads-search-api"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.apify.com/?tools=sauliusautomatesit/threads-search-api streamable-http needs key 303 ms 4 min ago

Alternatives to Threads Search API

same job, measured the same way
Code Context
by infino-ai

Local code search for AI coding agents: hybrid keyword + semantic + SQL over an index in your repo.

76 installs/wk local only
Miru
by takara

Hybrid semantic and keyword code search for coding agents.

326 installs/wk local only
Agent Ready Report
by agenticplug

Scan any public website and see how ready it is for AI agents and AI search, explained plainly.

2 tools answering
Filesift
by roshunsunder

Local file search for AI agents — semantic + keyword indexing over your codebase.

68 installs/wk local only
Katzilla
by codeislaw101

300+ free public & government data sources behind one API key, for AI agents.

22 installs/wk local only
npubmail
by npubmail

Email inbox for AI agents, owned by a Nostr key. No signup or API key. Receive codes, read, send.

local only
MCP Github
by infoinlet-marketplace

GitHub for AI agents — repos, files, code search, issues, PRs, commits. Read-only default.

29 installs/wk local only
Gitea MCP
by mrfentmen

Gitea.com public API: search repos and users.

78 installs/wk local only

Threads Search API — questions

Answers built from our own checks of this server.

Why is there no tool list for Threads Search API?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Threads Search API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 332 ms. The bar chart above shows every period we have measured.
How do I connect Threads Search API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.
Does Threads Search API need an API key?
Yes. Every time we knock, Threads Search API answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Threads Search API?
It answers our handshake in 332 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.