Microsoft Fabric RTI MCP
Capped at 90: 2 of 3 real tool calls passed in our test; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 90 because not every real tool call passed. Not a quality or security rating. Why scores are capped
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested pypi microsoft-fabric-rti-mcp 0.6.2 (MIT; repo microsoft/fabric-rti-mcp). Installed pinned with scripts off (uv venv, Python 3.13) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 39 tools (39 annotated by the server: 21 read-only, 11 destructive). Real calls: 2 of 3 real function calls passed. eventstream_list needs Azure credentials (DefaultAzureCredential failed).
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): partial. 2 of 3 real function calls passed. eventstream_list needs Azure credentials (DefaultAzureCredential failed). Evidence: local test run, Nov 18, 2026 UTC.
Transport (tested 2026-11-18 UTC): stdio
Token cost (estimate): approx. 7555 tokens, cl100k estimate (39 tools, measured 2026-11-18 UTC, version 0.6.2). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 14 read, 16 write (state-changing), 9 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
activator_create_trigger— write (state-changing)activator_list_artifacts— readeventstream_add_custom_endpoint_destination— write (state-changing)eventstream_add_custom_endpoint_source— write (state-changing)eventstream_add_derived_stream— write (state-changing)eventstream_add_eventhouse_destination— write (state-changing)eventstream_add_sample_data_source— write (state-changing)eventstream_clear_definition— write (state-changing)eventstream_create— write (state-changing)eventstream_create_from_definition— write (state-changing)eventstream_delete— write (state-changing)eventstream_get— readeventstream_get_current_definition— readeventstream_get_definition— readeventstream_list— readeventstream_list_available_components— readeventstream_start_definition— write (state-changing)eventstream_update— write (state-changing)eventstream_validate_definition— unclassifiedkusto_command— unclassifiedkusto_deeplink_from_query— unclassifiedkusto_describe_database— readkusto_describe_database_entity— readkusto_diagnostics— unclassifiedkusto_graph_query— unclassifiedkusto_ingest_inline_into_table— unclassifiedkusto_known_services— unclassifiedkusto_list_entities— readkusto_query— unclassifiedkusto_sample_entity— unclassifiedkusto_show_command— readkusto_show_queryplan— readmap_create— write (state-changing)map_delete— write (state-changing)map_get— readmap_get_definition— readmap_list— readmap_update— write (state-changing)map_update_definition— write (state-changing)
handshake and tools listed without a recorded key or OAuth
Score 90/100 · Tools 39 · Token cost approx. 7,555 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 0.6.2 · Package microsoft-fabric-rti-mcp · Repo microsoft/fabric-rti-mcp
Summary: Microsoft Fabric RTI MCP completed an MCP handshake without credentials and exposed 39 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 39
- Context cost
- approx. 7555 tokens, cl100k estimate (39 tools, measured 2026-11-18 UTC, version 0.6.2; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install microsoft-fabric-rti-mcp (Python venv, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 39 tools listed in 3.1s. |
| maintenance | pass | 25 | Repo pushed 1 days before test; 134 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 7555 tokens, cl100k estimate for 39 tools · about 92% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-18 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 39 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
c74993471758: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "microsoft-fabric-rti-mcp",
"version": "0.6.2",
"registry": "pypi",
"status": "working",
"tested": "2026-11-18",
"tools_count": 39,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`uv pip install microsoft-fabric-rti-mcp` (Python venv, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 39 tools listed in 3.1s."
],
"maintenance": [
"pass",
25,
"Repo pushed 1 days before test; 134 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-18T04:17:32.737Z"
}Install
uvx microsoft-fabric-rti-mcp
Pin the version we tested
uvx microsoft-fabric-rti-mcp==0.6.2
pip install microsoft-fabric-rti-mcp==0.6.2
tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"microsoft-fabric-rti-mcp": {
"command": "uvx",
"args": [
"microsoft-fabric-rti-mcp==0.6.2"
]
}
}
}Tools listed
kusto_known_services, kusto_query, kusto_command, kusto_show_command, kusto_list_entities, kusto_describe_database, kusto_describe_database_entity, kusto_graph_query, kusto_sample_entity, kusto_ingest_inline_into_table, kusto_deeplink_from_query, kusto_show_queryplan, kusto_diagnostics, eventstream_list, eventstream_get, eventstream_get_definition, eventstream_create, eventstream_update, eventstream_delete, eventstream_start_definition, eventstream_get_current_definition, eventstream_clear_definition, eventstream_add_sample_data_source, eventstream_add_custom_endpoint_source, eventstream_add_derived_stream, eventstream_add_eventhouse_destination, eventstream_add_custom_endpoint_destination, eventstream_validate_definition, eventstream_create_from_definition, eventstream_list_available_components, activator_list_artifacts, activator_create_trigger, map_list, map_get, map_get_definition, map_create, map_update_definition, map_update, map_delete
Quick config
{
"mcpServers": {
"microsoft-fabric-rti-mcp": {
"command": "uvx",
"args": [
"microsoft-fabric-rti-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
uv pip install microsoft-fabric-rti-mcp(Python venv). This is the exact command we ran on 2026-11-18 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (39 in our test).
{
"mcpServers": {
"microsoft-fabric-rti-mcp": {
"command": "uvx",
"args": [
"microsoft-fabric-rti-mcp"
]
}
}
}Test history
- 2026-11-18 UTC: New
Related: Best cloud MCP servers
FAQ
Is Microsoft Fabric RTI MCP deprecated?
No. Microsoft Fabric RTI MCP was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces Microsoft Fabric RTI MCP?
Nothing; Microsoft Fabric RTI MCP is not deprecated as of 2026-11-18 UTC.
Does Microsoft Fabric RTI MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 39 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.