portco-mcp
Related Servers
Alternatives to portco-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.3048 PyPI2MIT
- AlicenseBqualityBmaintenanceA local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.33MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server for data quality that finds suspicious data, explains findings with evidence, tracks drift, and supports human-approved, reversible repair workflows. Deterministic by default, with AI optional.182 PyPI2Apache 2.0

RecoSearchofficial
AlicenseNot gradedqualityCmaintenanceA deterministic MCP server that governs read-only queries across multiple data sources, returning answers with full provenance (every row cited) or a typed refusal, ensuring LLM answers are traceable and contract-enforced.1Apache 2.0- AlicenseBqualityBmaintenanceA read-only MCP server that exposes dbt project artifacts and data quality result tables (BigQuery/Postgres) to LLM clients, enabling deep introspection, run-history analysis, source freshness, test coverage, and lineage walks.2736 npmMIT
- AlicenseNot gradedqualityCmaintenanceLocal-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.1MIT
TDQS
Scored across 12 tools
Most tools map to distinct pipeline stages (profile, propose, review, generate, test, certify, publish), so an agent can largely tell them apart. However, start_onboarding_run and profile_schema both 'start a run' with profiling, and get_run_status overlaps list_pending_reviews on surfacing pending review items, creating minor boundary ambiguity.
Tools follow a clear snake_case verb_noun pattern (start_onboarding_run, get_run_status, resume_run, submit_mapping_review, certify_run, publish_run, etc.). The lone exception is healthcheck, a bare noun that breaks the otherwise consistent convention.
12 tools is well-scoped for a governed data-onboarding pipeline with multiple human gates. Each tool corresponds to a meaningful lifecycle stage or control operation, with no obvious redundancy bloating the surface.
The surface covers the full happy-path lifecycle: start, status, resume, profile, propose mapping, submit review, generate artifacts, sandbox test, certify, and publish, plus review listing and healthcheck. Missing abort/cancel and any run-listing or cleanup operations are minor gaps agents can work around.