deep-agentic-core-mcp
OfficialRelated Servers
Alternatives to deep-agentic-core-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceThis server enables agents to identify users and organizations, inspect versioned datasets and model lineage, start training jobs, run and read evaluations, verify deployments, and execute typed workflows through authenticated MCP endpoints.12Apache 2.0
- -licenseNot gradedqualityDmaintenanceMCP server for interacting with Conductor workflow orchestration, enabling AI agents to create, execute, and analyze workflows.-

AgentMark MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceMCP server for AgentMark. Exposes the full AgentMark API to AI editors: list traces and spans, manage datasets, write scores, run experiments, manage apps, deployments, environments, and annotation queues.352AGPL 3.0- AlicenseAqualityAmaintenanceMCP server that gives agents the same interface as dashAI's GUI: explore datasets, list models, train, track jobs, and read metrics.10MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to access unified development tools including code generation, documentation synchronization, test case rendering, and architecture graph queries through a single MCP server.-
- AlicenseAqualityAmaintenanceMCP server exposing AI agent observability tools: list, inspect, and deterministically replay recorded agent execution traces for debugging failures.1Apache 2.0
TDQS
Scored across 14 tools
Each tool is grouped under a clear domain prefix and has a distinct action, but core.health/core.verify both touch readiness and lens.report_summary/lens.slo_summary/lens.audit_report are all report-like. The descriptions clarify the boundaries well, leaving only minor potential for confusion.
Names consistently use lowercase dotted namespaces with snake_case and mostly follow a verb_noun pattern (analyze_workflow, compare_runs, run_experiment). A few noun-only names (core.health, core.version, sidecar.status) break the verb-first pattern, but the convention is still predictable.
Fourteen tools is well within the ideal range and each tool serves a distinct purpose across five focused domains. No tool feels redundant or gratuitous for a server covering core diagnostics, lens analysis, chaos, sidecar, and spec validation.
The tool set covers the advertised surface well: health/readiness, workflow analysis, run comparison, SLO evaluation, audit, chaos experiments, sidecar inspection, and artifact validation. Minor gaps exist around creating/modifying/storing artifacts, but they may be outside the server's intended scope and do not create obvious dead ends.