# Monte Carlo MCP Server and SYNQ MCP (Coalesce Quality), field by field: 15 and 134 tools named

SIDE BY SIDE, read 10 Nov 2026

**The short answer.** Monte Carlo MCP Server (Monte Carlo, remote (hosted)) names 15 tools; SYNQ MCP (Coalesce Quality) (SYNQ, remote (hosted)) names 134. Versions read on 10 Nov 2026: no version number published and no version number published. The page puts the same fields in the same rows and draws no conclusion.

| Field | Monte Carlo MCP Server | SYNQ MCP (Coalesce Quality) |
| --- | --- | --- |
| Data tool | [Monte Carlo](/mcp/monte-carlo/) | [SYNQ](/mcp/synq/) |
| Publisher | Monte Carlo | SYNQ (docs titled Coalesce Quality) |
| Kind | Official | Official |
| Repository or docs | [docs.getmontecarlo.com/docs/mcp-server](https://docs.getmontecarlo.com/docs/mcp-server) | [docs.synq.io/scout/mcp.md](https://docs.synq.io/scout/mcp.md) |
| Version or commit | Hosted at mcp.getmontecarlo.com/mcp, no version published | Hosted, no version published |
| Last release | none found on 10 Nov 2026 | none found on 10 Nov 2026 |
| Transport | Remote (hosted) | Remote (hosted) |
| Auth | OAuth 2.1 with Dynamic Client Registration (user identity, Editor role or above), or MCP-server-type API key id:secret as Bearer token via mcp-remote. | OAuth 2 with PKCE per user with selectable permission tier (read, write, governance, deploy); legacy workspace token (st-...) as Bearer. |
| Access | Configurable | Configurable |
| Tools listed | 15 named in the evidence | 134 named in the evidence |
| Tool definitions read at | none found on 10 Nov 2026 | [docs.synq.io/scout/mcp.md](https://docs.synq.io/scout/mcp.md) |
| Context weight | Not measured: no published tool-definition text was read on 10 Nov 2026 | 4,550 tokens for 134 tool definitions (134 with a description), measured from the docs page read |
| Status | Exists on 10 Nov 2026 as a hosted first-party server; tool names are partial (those named in the docs), full tool definitions were not published as text, so no schema file was saved. | Exists on 10 Nov 2026; docs.synq.io now titles itself Coalesce Quality Documentation and its MCP page calls the product Coalesce Quality; regional hosted endpoints EU/US/AU. |
| Read | 10 Nov 2026 | 10 Nov 2026 |

The same fourteen fields for both servers, read 10 Nov 2026.

## In one sentence each

- [Monte Carlo MCP Server](/servers/monte-carlo-mcp/): Monte Carlo's hosted observability server uses per-user OAuth or scoped keys, a per-request read-only header and tool allow-lists.
- [SYNQ MCP (Coalesce Quality)](/servers/synq-mcp/): SYNQ's hosted observability and lineage server uses per-user OAuth with tiered consent scopes, and tools hide when a scope is not granted.

## The read facts, topic by topic

| Topic | Monte Carlo MCP Server | SYNQ MCP (Coalesce Quality) |
| --- | --- | --- |
| Publisher and releases | The server is first-party, run by Monte Carlo at mcp.getmontecarlo.com/mcp, not distributed as a package. No version number or public release date is published for the hosted server; the docs page carries an updatedAt of 2 Nov 2026. | The server is hosted by SYNQ at regional URLs (EU mcp.synq.io, US, AU) and needs no workspace setup; no version or release date is published. None found: A GitHub repository, package version or release date for the SYNQ MCP server on the docs page. |
| Clients, auth and scoping | Monte Carlo says connected agents can investigate alerts, explore assets and lineage, and create and manage monitors. OAuth lets any HTTP-transport MCP client connect with no API keys, and the connector is listed in the Claude Connectors Directory. An Editor role or above is required to use the server. An agent_observability toolset adds get_agent_metadata, get_agent_conversation and get_agent_trace for inspecting AI agents. | OAuth 2 with PKCE means actions are recorded as the real user with a via MCP badge. The set of tools an assistant sees depends on the permissions the user grants at consent, and the consent screen offers only what the user's role allows. The iam tool reports the caller's workspace, granted scopes and user. |
| Access and safety | An x-mcp-readonly header hides write tools such as update_alert and create_or_update_* monitors and blocks calls to them. Per-request x-mcp-tools allow-lists narrow tools and are enforced on call, not only on listing. API-key access uses MCP-server-specific scoped keys; standard API keys do not work. The MCP server can be restricted by IP using Network Access Control Lists. External security audits and penetration tests are done at least annually, covering MCP surfaces. | Four permission tiers (read-only, write, governance, deploy) each grant only the scopes asked for; read-only makes no changes. Write tools do not appear in the client if the user granted only read-only access. Admins can switch off OAuth access to the API for third-party clients, including MCP, with the Disable user API access setting; legacy static workspace tokens (st-...) are also accepted. |
| What it reaches | None found: A list of warehouses and BI systems on the MCP pages (the server fronts the Monte Carlo account's monitored assets). | The docs name dbt, SQLMesh, Coalesce, Airflow and warehouse query history as sources the tools draw on. |
| Lineage and impact | Monte Carlo's MCP server includes a get_asset_lineage tool, used to see how data flows into a table. None found: Documentation that get_asset_lineage returns column-level lineage, transformation SQL, BI fields or metrics; the MCP pages name only asset lineage. | SYNQ (docs now titled Coalesce Quality) serves the same lineage graph as its lineage view, including column-level lineage where the warehouse supports it. Lineage tools include get_lineage (up/down/both with depth), upstream and downstream dependencies, common upstream, and upstream sources such as dbt sources. Get_code returns the latest source code defining an entity, including SQL definitions and dbt models. Impact tools list the entities and systems affected by an entity or an issue. |
| Definitions, ownership and rules | None found: Glossary terms, definitions or classification tools in the Monte Carlo MCP server docs; the tools are alerts, monitors, assets, lineage and data operations. Governance-like context comes from use cases and critical-table groupings (get_use_cases, get_use_case_tables) in the extended toolset. | Knowledge tools read entity descriptions and knowledge pages pinned to entities, including owners and certified pages. The Governance permission tier lets the assistant manage data products, domains, owners, alert routing and check categories. List_annotations and batch_entity_annotations read annotations carried by entities. |
| Freshness and upkeep | None found: A freshness statement on the MCP pages (the server reads live alert and monitor state from the Monte Carlo account). | Tools return execution history and latest executions for monitors, dbt models and Airflow tasks; join patterns use the last 30 days of warehouse query history. |
| Profile | Monte Carlo also publishes an Agent Toolkit (mc-agent-toolkit) of skills for monitoring and code-change validation, separate from the server. | SYNQ's documentation is titled Coalesce Quality Documentation; the relationship between the names is not explained on the pages read. |

Each cell joins the facts read for that topic; the full list with sources is on each entry. Read 10 Nov 2026.

## Tool names, as published

### Monte Carlo MCP Server

`search`, `get_table`, `get_asset_lineage`, `get_alerts`, `alert_assessment`, `update_alert`, `get_monitors`, `create_or_update_table_monitor`, `get_use_cases`, `get_use_case_tables`, `get_use_case_table_summary`, `get_agent_metadata`, `get_agent_conversation`, `get_agent_trace`, `create_agent_metric_monitor`

### SYNQ MCP (Coalesce Quality)

`add_comment`, `apply_service_account_changes`, `batch_entity_annotations`, `batch_entity_details`, `batch_executions`, `batch_urls`, `browse_folders`, `create_incident`, `create_monitors`, `create_sql_tests`, `create_table_stats_monitor`, `decide_recommendation`, `delete_alert`, `delete_check_categorisation_rule`, `delete_data_product`, `delete_deployment_rule`, `delete_domain`, `delete_monitors`, `delete_owner`, `delete_saved_view`, `delete_sql_test_deployment_rule`, `delete_sql_tests`, `deploy_deployment_rule`, `deploy_sql_test_deployment_rule`, `describe_check_categorisation`, `describe_check_types`, `describe_resolver_ql`, `exclude_from_monitoring`, `execute_monitor`, `folder_of`, `get_alert`, `get_code`, `get_commit_diff`, `get_common_upstream_dependencies`, `get_coverage_summary`, `get_data_product`, `get_database_change_details`, `get_database_coordinates_from_entity`, `get_deployment_rule`, `get_domain`, `get_downstream_dependencies`, `get_entity_access`, `get_entity_details`, `get_entity_from_database_coordinates`, `get_entity_impact`, `get_entity_knowledge`, `get_entity_metrics`, `get_entity_overlays`, `get_immediate_downstream_dependencies`, `get_immediate_upstream_dependencies`, `get_incident_details`, `get_issue`, `get_issue_comments`, `get_issue_details`, `get_issue_impact`, `get_join_patterns`, `get_knowledge_pages`, `get_latest_executions`, `get_lineage`, `get_monitor`, `get_monitor_predictions`, `get_owner`, `get_query_activity`, `get_saved_view`, `get_schema`, `get_sql_test_deployment_rule`, `get_upstream_dependencies`, `get_upstream_sources`, `iam`, `list_access_signals`, `list_alerts`, `list_annotations`, `list_categorised_checks`, `list_check_categories`, `list_check_categorisation_rules`, `list_checks`, `list_commits`, `list_data_product_members`, `list_data_products`, `list_database_changes`, `list_deployment_rules`, `list_domain_members`, `list_domains`, `list_entity_coverage`, `list_executions`, `list_folder_members`, `list_history`, `list_integration_health`, `list_knowledge_pages`, `list_monitor_segments`, `list_monitoring_exclusions`, `list_monitors`, `list_open_incidents`, `list_open_issues`, `list_owners`, `list_ownerships`, `list_platform_users`, `list_recommendations`, `list_saved_views`, `list_service_account_suggestions`, `list_service_accounts`, `list_sql_test_deployment_rules`, `list_sql_tests`, `list_table_stats_monitors`, `list_users`, `plan_service_account_changes`, `preview_check_categorisation_rule`, `preview_deployment_rule`, `preview_sql_test_deployment_rule`, `profile_columns`, `resolve_query`, `run_sql_test_again`, `sample_column_values`, `sample_entities`, `save_alert`, `save_check_categorisation_rule`, `save_data_product`, `save_domain`, `save_owner`, `save_saved_view`, `search_entities`, `send_test_alert`, `set_alert_enabled`, `set_check_category`, `set_issue_status`, `set_monitor_segment_labels`, `set_saved_view_pin`, `submit_feature_request`, `summarise_executions`, `unexclude_from_monitoring`, `update_incident`, `update_monitors`, `update_sql_tests`, `update_table_stats_monitor`

## Read next

- [Monte Carlo MCP Server, the full entry](/servers/monte-carlo-mcp/)
- [SYNQ MCP (Coalesce Quality), the full entry](/servers/synq-mcp/)
- [Every side-by-side](/compare/)

## Sources

- docs.getmontecarlo.com/docs/mcp-server: https://docs.getmontecarlo.com/docs/mcp-server (read 10 Nov 2026)
- docs.getmontecarlo.com/docs/mcp-server-reference-and-operations: https://docs.getmontecarlo.com/docs/mcp-server-reference-and-operations (read 10 Nov 2026)
- docs.getmontecarlo.com/docs/ai-security: https://docs.getmontecarlo.com/docs/ai-security (read 10 Nov 2026)
- docs.synq.io/scout/mcp.md: https://docs.synq.io/scout/mcp.md (read 10 Nov 2026)
- docs.synq.io/llms.txt: https://docs.synq.io/llms.txt (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datamcpservers.com/compare/monte-carlo-mcp-vs-synq-mcp/
