Horizon MCP
Related Servers
Alternatives to Horizon MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that fetches web pages and extracts clean, AI-usable context from them, enabling tools for link discovery, content search, and integrated fetch-and-search operations.58 npm1MIT
- AlicenseAqualityBmaintenanceMCP server for RSS aggregation and LLM summarization, allowing users to fetch latest articles, search archives, and generate topic-specific digests via natural language.7MIT
- AlicenseAqualityAmaintenanceA content exploration MCP server that helps LLMs surface high-signal, unsummarized web content through clean APIs and Markdown conversion, with intelligent frontmatter steering and citation tracking.134MIT
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server providing four tools for URL summarization, content repurposing, news digests, and competitor analysis, with cost telemetry and dual transport support.MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.5213 npm15MIT
- FlicenseAqualityBmaintenanceAn MCP server for aggregating multi-domain intelligence feeds, performing 80:20 crossover analysis, and publishing structured insights to multiple channels.5-
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose with no ambiguity. Tools like hz_fetch_items, hz_score_items, hz_filter_items, hz_enrich_items, and hz_generate_summary represent sequential stages in a content processing pipeline, while others handle metadata, metrics, configuration, and pipeline execution, all with non-overlapping functions.
All tool names follow a consistent hz_verb_noun pattern with snake_case throughout. The naming is predictable and readable, making it easy to understand each tool's function at a glance, such as hz_list_runs, hz_get_metrics, and hz_run_pipeline.
With 12 tools, the count is well-scoped for a content processing pipeline server. Each tool earns its place by covering distinct aspects like pipeline stages, metadata access, metrics, configuration validation, and full pipeline execution, without being excessive or insufficient.
The tool set provides complete coverage for the content processing domain. It includes all pipeline stages (fetch, score, filter, enrich, summarize), metadata and summary retrieval, run listing, metrics monitoring, configuration validation, and a full pipeline execution tool, leaving no obvious gaps for agent workflows.