Skip to main content
Glama
hey-research-lab

HEY Research MCP Server

by hey-research-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to HEY Research MCP Server

No user-submitted related servers found.

    Related Servers

    • Neural Search Engine MCP

      stand-out-of-my-sun
      A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with 12 real-time tools for search synthesis, grounded research dossiers, claim verification, citation generation, sentiment analysis, expert ranking, timeline creation, and competitive landscape mapping over Streamable HTTP or stdio.
      1
      12
      MIT

    • Enlace

      Caelos-Palacio
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes four stdio tools that let an agent research an application's documented interface, produce a validated single-use plan, and execute read-only operations against public HTTP JSON APIs, static HTML/JSON/text sources, and host-configured CLIs. Runs in-process with no listening port, accounts, or model dependency, returning bounded results while keeping inputs and outputs inside a host-enforced research-plan-execute lifecycle.
      MIT

    • ControlsGuard MCP Server

      SidJanawade
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes policy, control, risk and system lookup tools plus an agent-as-a-tool query endpoint over stdio or streamable HTTP, so clients can run hybrid and graph retrieval, traverse knowledge-graph neighbors, and assess control-coverage gaps. Answers come back cited and guardrailed, and it runs fully offline without API keys.
      MIT
    • @shieldlabs-ai/mcp by ShieldLabs-ai

      @shieldlabs-ai/mcpofficial

      ShieldLabs-ai
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read identification verdicts, search history, summarize entities, explain risk scores, and verify webhook signatures through read-only tools over stdio or streamable HTTP.
      6
      216 npm
      MIT

    • ThinkingModels MCP

      Klesenchang
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes five read-only tools that let clients query a public knowledge base of cognitive models — browsing taxonomy and categories, searching models, retrieving a model's details, exploring its lineage and relationships, and inspecting cited sources with verification status. It runs as a standalone Node.js service over local stdio or self-hosted Streamable HTTP, so assistants can ground answers in real, cited model data.
      1
      Creative Commons Zero v1.0 Universal

    • flowscan-mcp

      joshavenue
      A
      license
      A
      quality
      B
      maintenance
      Exposes real-time Hyperliquid explorer and analytics data from flowscan.xyz as 44 read-only tools, letting AI agents answer questions about protocol revenue, perp market positioning, individual open positions, wallet activity, and staking without an API key. It runs over stdio against Hyperliquid mainnet only, using the same API routes the Flowscan frontend calls.
      44
      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.5/5.0

    Scored across 13 tools

    Disambiguation3/5

    Most tools target distinct resources or views, but ask_hey, research_answer, find_projects, and get_project_snapshot overlap in answering project questions. get_changes, get_project_timeline, and project_diff also have related temporal-change boundaries that require careful reading to separate.

    Naming Consistency3/5

    Many tools follow snake_case verb_noun conventions (find_projects, get_contract, explain_fact), but ask_hey, chain_overview, and research_answer are noun-phrase or conversational rather than action-oriented. The mix is readable but not predictable enough for a 4.

    Tool Count5/5

    Thirteen tools is well within the appropriate range for a research server covering projects, chain activity, evidence, markets, and contracts. Each tool appears to earn its place without excessive surface area.

    Completeness5/5

    The set covers discovery, project snapshots, timelines, changes, diffs, explanations, evidence lookup, token markets, contracts, v4 hooks, and chain-level overviews. This is a comprehensive research lifecycle with few obvious dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources