mcpbeat

Instagram data for agents MCP Server

sh.fetcher.instagram/mcp
answering

Instagram data for agents is answering right now. Last checked 10 min ago. It exposes 6 tools.

16 Instagram endpoints. Pay per call in USDC via x402.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
466 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add mcp --transport http https://instagram.fetcher.sh/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://instagram.fetcher.sh/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://instagram.fetcher.sh/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://instagram.fetcher.sh/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://instagram.fetcher.sh/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

balance
check_balance
Free. Show the remaining credit balance for the API key sent in this connection's Authorization header. Call this before a long run of paid requests.
data
fetch_data
Paid. Fetch live data from any Instagram endpoint. Pass the endpoint path plus its parameters (path and query parameters together in `params`). Priced per call in USDC on Base, Polygon, Arbitrum, Monad or Solana: pay with x402, or send an Authorization: Bearer bby_live_... header to spend prepaid credits. Call describe_endpoint first if unsure about parameters.
describe
describe_endpoint
Free. Show the full call signature for one endpoint: required and optional parameters, allowed values, price, and response shape.
endpoints
search_endpoints
Free. Search fetcher.sh's Instagram endpoints by keyword. Returns paths, descriptions and per-call prices. Start here.
instagram
instagram_user_handle
Paid ($0.004). User handle — Instagram. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
topup
topup_credits
Paid (the amount you choose, minimum $1). Buy prepaid credits with x402 so later calls skip the per-call payment round trip. With an Authorization: Bearer bby_live_... header on this connection it recharges that key. Without one, the paying wallet becomes the account and a new API key is minted and returned once — store it as a secret, it cannot be recovered.

Endpoints

URLTransportStateLatencyChecked
https://instagram.fetcher.sh/mcp streamable-http answering 496 ms 10 min ago

Instagram data for agents — questions

Answers built from our own checks of this server.

What can Instagram data for agents do?
It exposes 6 tools, read directly from the server on our last check. Among them: check_balance, describe_endpoint, fetch_data, instagram_user_handle, search_endpoints, topup_credits. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Instagram data for agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 466 ms. The bar chart above shows every period we have measured.
How do I connect Instagram data for agents?
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.
Does Instagram data for agents need an API key?
No. Instagram data for agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Instagram data for agents?
It answers our handshake in 466 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.