seshat-bi
Related Servers
Alternatives to seshat-bi
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that lets clients discover and explore Oracle EPM Planning / NSPB applications, including metadata, substitution variables, targeted data slices, existing-job inspection, and sanitized connection status, while job and business-rule execution stay disabled.GPL 3.0
- AlicenseAqualityAmaintenanceRead-only MCP server that exposes the agentic-os governance, SDLC, and Quality Engineering methodology to any MCP host. It never writes to your repository and never executes code — it serves the methodology, plans an install, and verifies it, handing any commands back to the host to run.7Apache 2.0
- AlicenseCqualityDmaintenanceA read-only MCP server that enables users to query Databricks SQL, browse metadata, and monitor Delta Lake tables. It also supports tracking Databricks Jobs, DLT Pipelines, and cluster metrics through natural language interfaces.254MIT
- AlicenseNot gradedqualityAmaintenanceThis read-only MCP server lets AI assistants inspect Apache NiFi, ClickHouse, and Kafka across multiple environments through natural language. It provides health checks, flow and message searches, querying and metadata tools while enforcing OIDC or proxy authentication, per-user auditing, secret masking, and two-lock read-only safeguards.Apache 2.0
- AlicenseBqualityCmaintenanceA read-only MCP server for Microsoft Intune and Entra ID that enables list, get, search, and reporting operations for tenant visibility, audits, troubleshooting, and health reporting without write actions. It includes authentication helpers, report exports, and metadata discovery tools.361MIT
- AlicenseBqualityAmaintenanceRead-only MCP server that exposes governed operational records with provenance and validity windows so clients can check which evidence is still current before answering. It lets agents reconcile freshness, schedule state, and evidence specificity to determine whether scheduled automations are actually healthy, rather than trusting an expired dashboard summary.4MIT
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of readiness: overall status, next action, blockers, evidence pack assembly, approval request preparation, and static checks. The descriptions explicitly cross-reference each other and clarify 'not for' cases, making misselection unlikely.
All six tools follow a consistent pattern: 'seshat_' prefix plus a verb_noun combination (get_status, get_next_action, explain_blockers, export_evidence_pack, prepare_approval_request, run_static_check). Naming is uniform and predictable.
Six tools is well-scoped for the server's purpose. Each tool covers a distinct operation within readiness governance, and none feel redundant or superfluous.
The tool set comprehensively covers the read-only readiness governance domain: status, next step, blockers, evidence export, approval preparation, and static checks. It intentionally avoids write operations, but for its stated scope (reports and preparation only) there are no obvious gaps.