Skip to main content
Glama

Related Servers

Alternatives to Agenda Intelligence MD

  • A
    license
    B
    quality
    C
    maintenance
    MCP server that provides AI assistants access to stock market data including financial statements, stock prices, and market news through a Model Context Protocol interface.
    11
    2,317
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    An MCP implementation that integrates the Brave Search API, providing comprehensive search capabilities including web, local business, image, video, news searches, and AI-powered summarization.
    8
    62,241 npm
    1,561
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Real-time and historical oil, gas, and commodity prices. 40+ energy commodities including Brent Crude, WTI, Natural Gas, LBMA Gold/Silver, EU Carbon, and refined products. Get current prices, compare commodities, view market overviews, and access historical data — all through natural language. Used by energy traders, fintech companies, and researchers worldwide.
    32
    210 npm
    4
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Self-hostable MCP server for WhisperGraph — a graph of 7.39B nodes / 39B edges mapping DNS, BGP, GeoIP, WHOIS, and threat intelligence. Six read-only tools (Cypher query + schema introspection + threat assessment), six resources, eight investigation prompts. stdio and Streamable HTTP transports.
    8
    70 npm
    1
    Apache 2.0
  • A
    license
    A
    quality
    A
    maintenance
    Self-hosted financial data terminal for AI agents. Scrapes and serves SEC filings (full-text search), 13F institutional holdings, insider and congressional trades, FINRA short data, FRED economic indicators, CFTC futures positioning, VIX/put-call ratios, and daily stock prices over MCP.
    65
    240
    AGPL 3.0

Related Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables agents to search and reference trusted, out-of-band ingested source state, run claim-bound document reviews, validate evidence-status proposals against admissibility guards, and build evidence matrices. It keeps proposal, evidence, admissibility, and adjudication separate so agents can propose epistemic statuses without creating the source facts, page locators, provenance, or missingness records that support them.
    5
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables coding agents to turn OpenSpec intents and Git changes into revision-bound proofs by planning, selecting, and running the smallest safe protection set, then verifying composite verdicts and explaining evidence or unresolved states.
    MIT
  • A
    license
    C
    quality
    C
    maintenance
    Enables AI agents to run open-source intelligence workflows such as sanctions screening, prioritized vulnerability briefs, IOC searches, evidence-chain verification, and sun-position chronolocation.
    5
    MIT
  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables autonomous agents to transform raw telemetry, system metrics, and departmental status updates into leadership-ready decision briefs, KPI watchpoint summaries, strategic signal extraction, and actionable mitigation recommendations.
    MIT

TDQS

A3.6/5.0

Scored across 32 tools

Disambiguation3/5

The vertical triage tools (kazakhstan_market_entry_readiness, cis_secondary_sanctions_exposure, gulf_maritime_exposure, middle_corridor_deal_risk, corridor_bankability_screen) are clearly distinct domains, and pre_action_check vs agent_output_verification is well separated. However, the evidence-checking cluster (audit_claims, check_evidence_packet, grounded_check, verify_quotes, verify_claims, verify_claims vs score_output) has overlapping purposes that require careful reading of long descriptions to distinguish, and check_memo_quality vs validate_memo vs agent_output_verification can easily be misselected.

Naming Consistency3/5

There is a mix of verb_noun names (validate_brief, get_signal, append_evidence, generate_repair_prompt) and noun-phrase domain names (agentic_interaction_trust, kazakhstan_market_entry_readiness, corridor_bankability_screen), plus bare verbs (analyze, deep_dive). All snake_case, which helps, but the verb style is inconsistent across the surface.

Tool Count2/5

At 32 tools this exceeds the practical ceiling for reliable tool selection; several vertical triage workers and five-plus evidence-checking tools could plausibly be consolidated or moved behind a dispatcher. Each tool has a defensible purpose, but the volume itself creates selection overhead for the agent.

Completeness4/5

The surface covers the full pipeline: schema discovery (get_schema), assembly (create_brief, append_evidence), validation (validate_brief/evidence/memo), analysis (analyze), evidence review (audit_claims, grounded_check, verify_quotes, verify_claims), repair (generate_repair_prompt), and domain-specific triage. Minor gaps: deep_dive is an explicit non-functional placeholder, and there is no listing/discovery of packaged memos or packaged signals beyond a static index.

Maintenance

ActivityActive
ResponsivenessLimited data