mcp-ml-tools
Related Servers
Alternatives to mcp-ml-tools
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables developers to explain error messages, validate and format JSON, generate regex patterns from descriptions, and summarize text via an LLM, all through MCP-connected clients.-
- AlicenseAqualityDmaintenanceEnables AI clients to use developer utilities like JSON formatting, JWT decoding, UUID generation, and more via MCP.1288 npm2MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to score retrieval quality with recall, precision, nDCG, hit rate and MRR, compare 2-3 configurations with seeded paired-bootstrap confidence intervals, audit agent tool calls against expected traces, and detect prompt regressions against golden sets. It also generates Markdown, JSON or JUnit reports with pass/fail gates, all deterministically and offline without paid API keys.647 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to access model registry, prediction logging, drift detection, bias/fairness auditing, compliance and governance queries, explanation generation, LLM/RAG monitoring, content safety, alert management, multi-agent workflow tracking, and performance metrics through 197 tools across 18 domains. Supports stdio and hosted Streamable HTTP transports, plus MCP Apps interactive audit cards.35 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM evaluation and observability by uploading documents, building test sets, running RAG pipelines, and automatically scoring answers for groundedness, hallucination risk, retrieval quality, latency, and cost, with tools exposed to MCP-compatible clients.1MIT
- AlicenseNot gradedqualityBmaintenanceExposes MCP tools to list and inspect the 48 harm-ladder tasks, deterministically score a submitted decision trace, run a full evaluation against a mock or real model provider, and retrieve data provenance. This lets developers measure a model's pushback and refusal calibration as plan harm rises, directly from any MCP client.29 npmMIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct operation: token counting/costing, BM25 retrieval, paired evaluation statistics, JSON Schema validation, and prompt-injection scanning. There is no meaningful overlap in input type or output, so an agent can select the right tool unambiguously from the name alone.
All names use snake_case, which is consistent, but the grammatical pattern varies: 'tokenize' is a bare verb while the others are noun_verb or noun_noun_verb compounds ('bm25_search', 'json_schema_validate'). This is a minor deviation that stays readable and predictable.
Five tools is a compact, well-scoped set with no padding or redundant entries. For a broad 'ml-tools' label it is slightly thin, but each tool clearly earns its place as a distinct utility.
The surface covers a coherent slice of LLM-app utilities (tokenize, retrieve, evaluate, validate, screen), and each tool is self-contained. However, obvious gaps remain for an ML toolkit: no embedding/vector retrieval (BM25 only), no model invocation, and no general metrics beyond paired comparison.