linkup-mcp
Related Servers
Alternatives to linkup-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to perform AI-powered web scraping, extraction, search, crawling, schema generation, and scheduled monitor management through local or hosted integration.-
- AlicenseAqualityBmaintenanceEnables MCP clients to capture webpages as images or PDFs, extract structured content, crawl sites, analyze pages with AI, and retrieve usage and infrastructure statistics.674 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to scrape web pages, extract structured data, search, crawl sites, generate schemas, schedule monitors, and inspect credits/history through hosted or local integrations.-
- AlicenseNot gradedqualityCmaintenanceEnables authenticated, scoped web search and bounded web/PDF fetching for agents and API clients through MCP tools, with configurable engine pools, quotas, and optional REST or browser access.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables users to interact with Interactive Brokers' official Web API through MCP, supporting account management, reporting, and other brokerage operations via the Client Portal Gateway for retail authentication.-
- AlicenseBqualityBmaintenanceEnables MCP clients to run live web searches, fetch and navigate readable web pages, search images, capture PDF screenshots, and retrieve finance, weather, sports, and world-time data through a zero-configuration authenticated backend.1118 npmMIT
TDQS
Scored across 18 tools
Most tools map to a distinct endpoint and resource (search, fetch, research, tasks, extract, rewind, credits), and descriptions explicitly steer between them (e.g. 'for a quick fact use linkup-search'). Residual overlap exists between linkup-search/sourcedAnswer, linkup-responses and linkup-research, and between linkup-research and linkup-tasks-create with a research type, which could still cause misselection.
Names mix verb-first and resource-first ordering inconsistently: linkup-get-research / linkup-list-research / linkup-get-extract sit alongside linkup-tasks-get / linkup-tasks-list, and linkup-credits-balance is noun_noun. All are kebab-case and readable, but the same operation is spelled two different ways across resource families.
18 tools is on the heavy side, but the surface spans several genuinely distinct feature areas (search, fetch, async research, batch tasks, extract, rewind, responses, billing, guide), each needing its own create/read/list or download. A few—linkup-responses, linkup-guide, and the closed-beta rewind pair—are marginal additions rather than core.
The surface covers the main lifecycle well: create/poll/list/wait for research, bulk create/get/list for tasks, extract create/get/list/download, credits, and an offline guide. The notable gap is the absence of cancel/delete operations for research, task, or extract resources, which matters for long-running, billable async work.