Skip to main content
Glama
gaofeibilly-maker

oriole

Related Servers

Alternatives to oriole

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes 108+ omega-cli OSINT tools for reconnaissance, web analysis, threat intelligence, and reporting, enabling AI assistants to perform comprehensive open-source intelligence tasks.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      An MCP server for global tech intelligence gathering, offering tools for searching Chinese and English web content, GitHub trending, arXiv papers, HN, Exa, SEC filings, Juejin, Zhihu, Bilibili, and A-share financial reports, all without API keys and with direct China access.
      15
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A custom MCP server with 6 utility tools (file search, file reading, math calculation, JSON formatting, time query, system info) that demonstrates MCP protocol workflow and integrates with LangChain agents.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables job intelligence retrieval and ranking, providing tools to list jobs, fetch details, access corpus statistics, and score candidates against job descriptions using staged retrieval to optimize LLM context usage.
      -

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have distinct purposes, but run_pipeline and run_due both execute workflows and could be confusing. However, descriptions clarify that run_pipeline is a general discovery-probing pipeline, while run_due runs scheduled tasks. Other pairs like discover_sources/probe_source and submit_source/review_source are clearly separated.

    Naming Consistency4/5

    All tools share the 'huangque.' prefix and mostly follow a verb_noun pattern (e.g., list_sources, collect_jobs, get_run). Exceptions like 'status' and 'source_coverage' use nouns, but they are still intuitive and the overall naming is coherent.

    Tool Count4/5

    With 16 tools, the set is slightly above the ideal 3-15 range but still well-scoped for a comprehensive job-source management system. Each tool covers a distinct aspect, and no tool feels redundant.

    Completeness4/5

    The toolset covers the full lifecycle: discovery, submission, probing, review, collection, listing, reporting, and pipeline execution. Minor gaps exist (e.g., no explicit update/delete for sources), but the core workflows are well-supported and agents can work around these limitations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues