embodied-mcp
Related Servers
Alternatives to embodied-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to upload tabular datasets and run deterministic Pandas, NumPy, Excel/openpyxl, and automated EDA operations through registered tools.-

flexorch-mcpofficial
AlicenseAqualityBmaintenanceEnables Claude and other MCP-compatible agents to process documents, extract structured data, detect PII, and export LLM-ready datasets through natural language tool calls.821 PyPI1MIT- AlicenseNot gradedqualityDmaintenanceEnables MCP agents to discover, import, query, visualize, select, and cite NEON and local scientific datasets while keeping credentials, private paths, and bulk data out of model context.MIT
- AlicenseAqualityBmaintenanceProvides MCP tools for scanning, redacting, and packaging dataset/model directories for public release, leveraging Presidio for PII detection and generating Hugging Face cards and EU AI Act training-data summaries.3Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables users to ingest documents, run retrieval-augmented queries with dense/sparse search and reranking, and inspect ingestion/query traces and evaluation results through MCP tools.-
- AlicenseAqualityBmaintenanceProvides safe, deterministic inspection, transformation, validation, and diffing of structured data (JSON, CSV, YAML, Parquet) via schema-aware MCP tools.4Apache 2.0
TDQS
Scored across 19 tools
Each tool targets a reasonably distinct action (detect vs. summarize vs. validate vs. quality_report vs. quality_gate), and the descriptions draw the lines clearly (structural validation vs. statistics/anomalies vs. rule evaluation). The main soft overlaps are detect_dataset/summarize_dataset (both surface the format) and the direct-call vs. submit_job paths for validate_dataset/quality_gate, but the background job model is explained well enough to avoid misselection.
Nearly all tools use a consistent snake_case verb_noun pattern (segment_episodes, detect_dataset, validate_dataset, convert_dataset, catalog_search), grouped with readable prefixes like catalog_ and job-related tools. Minor deviations are noun-phrase names such as job_status, quality_report, quality_gate and catalog_stats, which mix styles slightly but remain predictable and readable.
At 19 tools the surface is a bit heavy, but the domain is genuinely broad: inspection, validation, quality analysis, windows/segmentation, conversion, scaffolding, cataloging and job orchestration. Almost every tool maps to a real capability rather than filler, so it lands just over the ideal band without feeling padded.
Coverage is strong end-to-end: discovery, schema summary, structural validation, quality analysis and gating, annotation manifests, conversion, project scaffolding, a searchable catalog with version history, and async job lifecycle (submit/status/cancel/list). Minor gaps remain — no tool to read individual frames/episodes or sample data, and no catalog entry deletion/update beyond upsert by index.