Skip to main content
Glama
Sign In
The Intelligence Radar MCP server

The Intelligence Radar MCP server

Official
by BrightbeamAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to The Intelligence Radar MCP server

No user-submitted related servers found.

    Related Servers

    • awesome-core

      twojlogin
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, filter, and explore a local offline catalog of tools from awesome lists, including finding underrated tools, explaining ranking provenance, listing curator lists, and inspecting catalog facets. All access is read-only over local SQLite with no network calls or API keys.
      43 PyPI
      MIT

    • code-recycle

      Z33MScEssex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants to search locally indexed code and research notes, returning file, line, and source-link references without external accounts or API keys.
      MIT

    • Smart Coding MCP

      daanivanov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search a codebase by meaning using local AI embeddings, finding relevant code even when terminology differs from the query. Also provides package version lookup across 20+ registries, workspace switching, reindexing, cache clearing, and status checks.
      26 npm
      MIT

    • Keepygaga RAG

      TimWongUp
      A
      license
      A
      quality
      C
      maintenance
      Enables local-first hybrid knowledge retrieval from authorized Markdown and plain-text files, combining full-text and vector search with reranking and traceable source references via a single search tool.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource plus action: read-side (search_radar, get_entry, get_dimension, list_dimensions, list_judgements, get_sources, get_sector, check_plan) and contribution-side (prepare/submit/revise/withdraw/my_contributions) are cleanly separated, and prepare vs submit is explicitly spelled out. The main soft spots are search_radar vs show_radar (both can surface a filtered set of entries) and about_radar vs how_to_contribute, which an agent could plausibly mix up on a first call.

    Naming Consistency4/5

    Names are uniformly snake_case and overwhelmingly follow verb_noun (submit_contribution, get_entry, list_dimensions, check_plan, sign_in_with_github). A few break the verb pattern (my_contributions, about_radar, how_to_contribute), but they are readable and internally sensible rather than chaotic.

    Tool Count4/5

    18 tools is on the heavy side, but the server genuinely spans three surfaces: content discovery/reading, plan and radar analysis, and a full contribution lifecycle plus GitHub auth. Nearly every tool earns its place, though the read side (search/get/list/show/dimension/sector/sources) is dense enough that some consolidation could be considered.

    Completeness4/5

    The read surface is thorough (search, entry, dimension, judgements, sources, sector, plan check, interactive view) and the contribution lifecycle covers prepare, submit, revise, withdraw, status, sign-in/out and applying as a contributor. Minor gaps: how_to_contribute references reviewing contributions, yet no reviewer-facing tool exists in the set, and there is no direct 'browse by label' entry point beyond search filters.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources