II.
ToolServer JSON
Structured · livetool-server:mcp-dbt-candidate
dbt MCP candidate json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "tool-server:mcp-dbt-candidate",
"_kind": "ToolServer",
"_file": "extensions/tool-servers/ora-business-ops-mcp-candidates.yaml",
"_cluster": "extensions",
"attributes": {
"displayName": "dbt MCP candidate",
"description": "Candidate MCP server for dbt project metadata, model lineage, tests, runs, and warehouse transformation workflows.\nRecorded from Ora data-engineering discovery because Atlas did not have a dbt-specific ToolServer.\n",
"protocol": "mcp-stdio",
"provenance": "custom",
"category": "analytics",
"maintainer": "Candidate",
"sourceRef": "source-ref:ora-discover-api",
"candidateStatus": "needs-source-verification",
"ora": {
"domain": "getdbt.com",
"score": 0,
"grade": "F"
}
},
"outgoingEdges": [
{
"from": "tool-server:mcp-dbt-candidate",
"to": "tool:dbt-labs",
"kind": "integrates_with",
"attributes": {}
},
{
"from": "tool-server:mcp-dbt-candidate",
"to": "source-ref:ora-discover-api",
"kind": "sourced_from",
"attributes": {}
},
{
"from": "tool-server:mcp-dbt-candidate",
"to": "role:data-engineer",
"kind": "supports_work",
"attributes": {
"confidence": "medium",
"evidence": "dbt metadata and run status would support data engineering and analytics-engineering workflows."
}
},
{
"from": "tool-server:mcp-dbt-candidate",
"to": "workflow:data-pipeline-monitoring",
"kind": "supports_work",
"attributes": {
"confidence": "medium",
"evidence": "dbt tests, lineage, and run results are pipeline-monitoring projection points."
}
}
],
"incomingEdges": []
}