Skip to main content
Glama
neuralverge

NeuralVerge MCP Server

Official
by neuralverge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to NeuralVerge MCP Server

No user-submitted related servers found.

    Related Servers

    • Relay

      adarshp14
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      MIT
    • Mixpeek MCP Server by mixpeek

      Mixpeek MCP Serverofficial

      mixpeek
      A
      license
      Not graded
      quality
      D
      maintenance
      Automatically loads Mixpeek's OpenAPI spec and exposes its endpoints as MCP tools, enabling natural language interaction with Mixpeek's API via standard MCP clients.
      24 npm
      1
      MIT

    • AXE Fleet MCP Server

      memjar
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Exposes over 19,000 Apify Actors as MCP tools for web scraping, data extraction, and OSINT automation. It enables AI agents to dynamically discover and execute scrapers to collect structured data and crawl web content.
      MIT

    • rest2mcp

      gonzalo123
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes any REST API as MCP tools, enabling AI agents to discover and call existing HTTP endpoints without modifying the original API.
      -
    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 16 tools

    Disambiguation3/5

    Multiple tools target similar actions (email finder vs LinkedIn email, people vs company employee search, phone vs US phone enrichment), and async workflows (research vs agent) are easy to confuse. Descriptions help clarify, but boundaries between tools are not always sharp.

    Naming Consistency3/5

    Strong run_ prefix creates a consistent feel, but suffixes mix verb-style (search, extract) and noun-style (email_finder, phone_enrichment_us) naming. The outlier get_session_status breaks the run_ pattern, and run_linkedin_domain is misleading (it does not search by domain).

    Tool Count4/5

    With 16 tools, this is slightly above the typical 3-15 range, but the server covers distinct domains (research, search, LinkedIn, email, phone, Crunchbase), so each tool earns a place. The count feels justified for a comprehensive enrichment platform, though it borders on heavy.

    Completeness4/5

    Core data retrieval surfaces are well covered: research workflow, search, extraction, LinkedIn, email, phone, and company data. Notable gaps include no agent management (list/create agents) and no session control (cancel/pause), but most practical workflows are supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources