agent-friend
Related Servers
Alternatives to agent-friend
No user-submitted related servers found.
Related Servers
- MIT
- AlicenseAqualityAmaintenance17 decision intelligence algorithms as MCP tools for AI agents. Bandits (UCB1, Thompson), LP/MIP solver (HiGHS), Monte Carlo simulation, Bayesian inference, graph analytics (PageRank, Louvain), genetic algorithms, CMA-ES, anomaly detection, time series forecasting, and more. All under 25ms, deterministic, zero LLM cost.1713MIT
- AlicenseNot gradedqualityCmaintenanceProvides linear programming (LP), mixed-integer programming (MIP), and quadratic programming (QP) optimization capabilities using the HiGHS solver, enabling AI assistants to solve complex optimization problems like production planning, logistics, and portfolio optimization.8 npm18MIT
- AlicenseBqualityAmaintenanceProvides data science, plotting, statistics, system, and web tools via MCP, with interactive CLI clients for OpenAI-compatible and Anthropic providers.261MIT
- AlicenseNot gradedqualityBmaintenanceMachine-readable utilities and datasets for AI agents. MCP + HTTP + x402.MIT
- AlicenseNot gradedqualityBmaintenanceProvides data preparation, anonymization, and processing tools for AI agents, handling big data with Polars and DuckDB.MIT
TDQS
Scored across 314 tools
Domain prefixes keep tools within each category distinct, but cross-category overlaps exist: fetch_fetch, http_http_request, browser_browse, and retry_retry_http all retrieve URLs, while timer_timer_stop and metrics_metric_timer_stop are easy to confuse. The sheer number of tools also increases the chance an agent picks a related but wrong tool, though descriptions usually clarify.
Almost all tools follow a predictable snake_case category_prefix + verb_noun pattern, such as queue_queue_create, cache_cache_get, and lock_lock_release. Minor deviations like process_run, search_search, and browser_browse break the strict double-prefix style but are still readable and predictable.
314 tools is an extreme tool count, far beyond what an agent can reasonably scan or evaluate. Even though this is a general-purpose utility server, the surface is effectively a kitchen sink rather than a coherent, scoped toolset.
Most domains have strong lifecycle coverage: cache, locks, state machines, rate limiters, validators, and vector stores are essentially complete. Notable gaps exist in file operations (no delete/move) and git (no checkout/push/pull/merge), but these are workable given the enormous breadth elsewhere.