No user-submitted related servers found.
Scored across 11 tools
Most tools target clearly distinct signals: pricing, status, drift, jobs, regulations, incidents, and routing. The only mild overlap is get_incident_stats (aggregate counts) vs get_ai_incidents (searchable records), but the descriptions clearly separate counting from searching. get_company_intelligence is a synthesis tool and doesn't collide with the atomic tools.
Ten of eleven tools follow a clean get_* snake_case pattern (get_ai_model_pricing, get_gpu_pricing, get_ai_route, etc.). scan_n8n breaks the get_ prefix convention, but it is an action verb appropriate to a scan operation, so the deviation is minor and readable.
Eleven tools is well-scoped for an AI-ecosystem intelligence server, with each tool covering a distinct signal source (pricing, status, drift, incidents, jobs, regulations, routing, vulnerability scanning). No obvious filler or redundancy.
The surface covers a broad range of intelligence signals plus a cross-signal aggregator (get_company_intelligence) and a routing recommender, giving good lifecycle coverage. Minor gaps exist, such as no historical/trend query for pricing or status, but core workflows are covered.