AIsa MCP
OfficialRelated Servers
Alternatives to AIsa MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides a single MCP endpoint for 90+ tools across 42 backend servers (search, legal, domain, etc.) with per-call credit billing and a single API key.1MIT

Crawlora MCPofficial
AlicenseCqualityBmaintenanceHosted MCP server for 3926 structured public web-data tools across 488 platform groups, returning clean JSON for search, maps, commerce, social, and finance.14500252 npm1MIT- AlicenseNot gradedqualityDmaintenanceUnified MCP server for managing Meta Ads, LinkedIn Ads, Google Ads, GA4, and Search Console with 89 read/write tools, multi-account support, OAuth setup, and safe dry-run mutations.MIT
- AlicenseCqualityDmaintenanceMCP server for the Meta Marketing API with 118 typed tools across ads, insights, pixels/CAPI, pages, Instagram, WhatsApp, catalogs, audiences, leads, and billing, featuring secure token storage and a confirmation gate on destructive calls.1001MIT

ReefAPI MCPofficial
AlicenseAqualityBmaintenanceOne MCP server providing access to 160+ live web data APIs (search, social media, e-commerce, real estate, jobs, travel, news, finance, and more) using dynamic discovery via 4 generic tools to avoid the agent's tool limit.54MIT- AlicenseNot gradedqualityAmaintenanceConnects AI clients such as Claude Code, Cursor, Codex, ChatGPT, Hermes, and OpenClaw to 2,000+ AI models and data APIs through a local MCP bridge, letting an agent discover, inspect, price, and run tools after a single browser-approved OAuth sign-in. Backed by a read-only catalog, run history, and rollback so calls can be audited and reverted without managing individual API keys.556,724 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: list_categories covers category-level discovery, search finds operations by task, get_details exposes contracts, and use/batch_use execute single or batched operations. There is no meaningful overlap between any pair.
Names are all lowercase imperative commands with underscores, and the pair use/batch_use is logical. The main inconsistency is that search and use are bare verbs while list_categories and get_details include a noun object, but the pattern remains predictable and readable.
Five tools is well-scoped for a gateway server that fronts a huge catalogue: two discovery tools, one detail tool, and two execution tools. Every tool earns its place and the count is appropriate.
The server covers the full lifecycle of working with the AIsa catalogue: browse categories, search operations, inspect contracts, execute one operation, and execute many operations. No obvious dead ends or missing capabilities for the stated purpose.