Infobroker
Related Servers
Alternatives to Infobroker
- AlicenseNot gradedqualityCmaintenanceZero-auth multi-source research MCP server that enables web search, reading URLs, PDFs, GitHub repos, and querying Hacker News, Stack Overflow, Semantic Scholar, and YouTube transcripts without API keys.79 PyPI11Apache 2.0
- FlicenseAqualityDmaintenanceEnables searching and gathering information from multiple online sources (web, Twitter/X, Telegram, GitHub, Hugging Face, arXiv) through a unified MCP interface.12-
Related Servers
- AlicenseAqualityBmaintenanceEnables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.8MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to perform unified web research through a single MCP server, including search, page fetching, recursive crawling, document parsing, YouTube transcript extraction, and deep multi-query research.3-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform local-first web search, fetch, crawl, extract, cache, research, and autonomous information gathering through MCP, with no API keys or cloud dependencies.1,093 npmAGPL 3.0
- AlicenseNot gradedqualityFmaintenanceMCP server enabling local-first web search, fetch, extract, and caching with citeable excerpts, no API key required. Supports research workflows for agents and apps.42 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform web search, extraction, and research across multiple provider backends with persistent multi-key rotation and auditable routing. Supports MCP, CLI, and Agent Skill entry points.MIT
- AlicenseNot gradedqualityDmaintenanceA provider-neutral Web Search MCP server and CLI that combines live search, scholarly discovery, verified PDF downloads, URL normalization, multi-provider ranking, secure page fetching, caching, and citation-ready research evidence.MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct role, and the descriptions explicitly cross-reference alternatives (e.g. search_web vs fetch_page vs verify_claims vs get_citations). The only potential overlaps — KB search vs web search, provider inspection vs config reload — are sharply bounded by stored-vs-fresh and read-only-vs-mutating semantics.
All tools use the same infobroker_ prefix followed by a consistent snake_case verb_noun pattern: get_citations, fetch_page, inspect_providers, manage_kb, reload_config, search_web, verify_claims. There is no mixing of casing or verb styles.
Seven tools is well within the appropriate range for a research/information-broker server. Each tool earns its place by covering a distinct workflow stage: discovery, retrieval, citation, verification, storage, diagnostics, and configuration.
The surface covers the core research lifecycle: search, page fetch, citation generation, claim verification, knowledge-base storage/recall, provider inspection, and config reload. Minor gaps exist, such as no explicit update/edit action for existing KB entries beyond ingest, but agents can work around this.