What is the AIsa remote MCP server?
The AIsa remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.aisa.one/mcp, so AI assistants can connect to it without installing or running anything locally.
@AIsa
Basic information
Transport
Streamable HTTP
Authentication
OAuth
Last updated
Category
Data & Analytics
Author
AIsa
Submitted by
jony jiao
AIsa is one key for 950+ data APIs across SEO and AI visibility, finance, social, web search, sales and agent mail — the go-to-market data stack behind prospecting, competitor research and brand monitoring. Five tools rather than hundreds: AIsa's search finds an operation from a plain-language task, get_details gives its contract and price, and use runs it — max_price_usd refuses anything above a cap before any spend. Remote, OAuth, nothing to paste.
https://mcp.aisa.one/mcpclaude mcp add aisa --transport http https://mcp.aisa.one/mcpTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
This server requires authentication. Tool discovery may require signing in or credentials from the provider.
Fetch the live tool list directly from this server's endpoint using the button above.
AIsa is one remote MCP endpoint in front of 950+ data APIs — SEO and AI visibility (DataForSEO, Semrush, Ahrefs), finance (prices, fundamentals, filings, crypto, prediction markets), social (X/Twitter, Instagram, Reddit, Pinterest, YouTube), web search and research (Tavily, Firecrawl, Exa, Perplexity, Oxylabs), sales (Apollo, creator discovery, Similarweb) and agent mail (AgentMail).
One key, one connection, one bill — instead of a developer account, a contract and a rate limit per provider.
Putting 950 operations in tools/list would cost more context than the work. So the endpoint lists five:
| Tool | What it does | Price |
|---|---|---|
search | Find an operation from a plain-language task. Returns operation_id, input_schema, price and match reasons. | Free |
get_details | Full contract for an operation: schemas, availability, price, known pitfalls. | Free |
list_categories | The catalogue at a glance. | Free |
use | Run one operation. | Per call |
batch_use | Run up to 20 concurrently; one failure never cancels the others. | Per call |
search reaches the whole catalogue, so nothing is hidden behind a category. For comparison, Firecrawl's MCP server lists 3 tools and DeepWiki's lists 3 — a short tool list is the norm for servers that route.
{
"mcpServers": {
"aisa": {
"type": "http",
"url": "https://mcp.aisa.one/mcp"
}
}
}
Nothing has to be created first. An unauthenticated request answers 401 naming its protected-resource metadata (RFC 9728), and the authorization server accepts an unregistered client (RFC 7591), so a client registers itself and signs the user in through a browser. An Authorization: Bearer <AIsa API key> header works instead.
Same server, a shorter tools/list. Connect one of these to preload just that category; search still reaches everything from any of them.
| Endpoint | Tools |
|---|---|
https://mcp.aisa.one/seo/mcp | 65 |
https://mcp.aisa.one/finance/mcp | 56 |
https://mcp.aisa.one/social/mcp | 61 |
https://mcp.aisa.one/search/mcp | 32 |
https://mcp.aisa.one/sales/mcp | 84 |
https://mcp.aisa.one/mail/mcp | 54 |
https://mcp.aisa.one/gtm/mcp | 48 |
Any server or module can also be pinned with ?modules=<slug>.
Discovery is free; use and batch_use are billed per call to the key in the Authorization header. Every paid call accepts max_price_usd, which refuses anything above the cap before any spend — so an agent cannot run up a bill by picking an expensive operation. Call use with operation_id: "account" (free) to see the key, balance and usage for today / 7 days / 30 days.
The same metric often exists from more than one provider — domain authority from DataForSEO, Semrush and Ahrefs; backlinks from several indexes. search makes that visible in the candidates, so when a decision depends on the number you can cross-check two providers in one batch_use.
one.aisa/mcp, plus one entry per category endpointThe AIsa remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.aisa.one/mcp, so AI assistants can connect to it without installing or running anything locally.
Add the endpoint https://mcp.aisa.one/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Yes. AIsa uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
AIsa exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
Hosted AdLoop: Google Ads, Reddit Ads, GA4 and Tag Manager in claude.ai, ChatGPT and more, with a preview before every change.
APIR is the evidence record for AI agents
Pay-per-use data and tools for AI agents: crypto token safety and rug checks, web search with cited answers, page-to-Markdown, up-to-date library docs, package safety, company research and UK/EU open data. 160 tools, 20
AOI is a commercial environmental-intelligence gateway that gives AI agents programmatic access to 38 real-world intelligence capabilities — climate risk, satellite monitoring, methane detection, water & soil, vegetation
Ask your assistant what a competitor is advertising and get the ads themselves: text, links, images, videos, platforms and dates from the Meta Ad Library (Facebook and Instagram), Google's Ads Transparency Center and the LinkedIn Ad Library
Comments