API.SH MCP Server

by api Your server? Claim it

answering

API.SH is answering right now. Last checked 8 min ago.

Live JSON from 84 sites: Google, Amazon, TikTok, Instagram, LinkedIn, Maps, Reddit and more

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

85 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check API.SH every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add apish --transport http https://mcp.api.sh/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.api.sh/mcp

~/.codex/config.toml

[mcp_servers.apish]
url = "https://mcp.api.sh/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "apish": {
      "url": "https://mcp.api.sh/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "apish": {
      "type": "http",
      "url": "https://mcp.api.sh/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.api.sh/mcp	streamable-http	sign-in	116 ms	8 min ago

Alternatives to API.SH

same job, measured the same way

Trends API

by trendsapi

Trend data from Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and more as JSON

6 tools answering

Scraping Daddy

by scrapingdaddy

Structured public data from YouTube, TikTok, Instagram, Reddit, X, Facebook, Google Maps and more.

16 tools answering

Trends MCP

by trendsmcp

Trend data from Google Trends, YouTube, TikTok, Reddit, Amazon, Wikipedia, npm, Steam and more

6 tools answering

Blend MCP

by blend-ai

Manage Google, Meta, TikTok, Microsoft, Pinterest, Amazon, LinkedIn & Reddit ads from your AI

answering

APICK Web

by apick

Domain/IP, web capture, Google search/maps, YouTube, Instagram, TikTok, X and Amazon data jobs

38 tools answering

Synter Ads

by jshorwitz

Manage ad campaigns across Google, Meta, LinkedIn, Reddit, TikTok, and more via AI.

235 tools answering

WhatsTrending: Trending Topics Today

by whatstrending

What's trending today: trending topics on Google, TikTok, YouTube, Reddit, X, Amazon and more

answering

Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads

by adkit

PPC advertising on Google Ads, Meta Ads (Facebook Ads), TikTok Ads, LinkedIn Ads, Reddit Ads & more.

answering

API.SH — questions

Answers built from our own checks of this server.

Why is there no tool list for API.SH?

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 API.SH 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 85 ms. The bar chart above shows every period we have measured.

How do I connect API.SH?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to API.SH?

No API key is involved. API.SH answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is API.SH?

It answers our handshake in 85 ms on average, which is faster than 95% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.