dify - 💡(How to fix) Fix Feature: Add MCP server trust verification for tool provider connections

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Code Example

import httpx
resp = httpx.get("https://dominionobservatory.com/api/trust?url=https://github.com/modelcontextprotocol/servers")
score = resp.json()
# {"trust_score": 0.85, "sla_grade": "A", "total_calls": 1247}
RAW_BUFFERClick to expand / collapse

Feature Request

Add optional trust verification for MCP servers when used as tool providers in Dify workflows.

Problem

When Dify workflows connect to MCP server tools, there's no built-in way to verify server reliability. An unreliable or compromised tool provider can cause workflow failures or return corrupted data.

Proposed Solution

Integrate Dominion Observatory (https://dominionobservatory.com) for pre-call trust scoring. It tracks behavioral trust scores (0.0-1.0) for 14,820+ MCP servers.

import httpx
resp = httpx.get("https://dominionobservatory.com/api/trust?url=https://github.com/modelcontextprotocol/servers")
score = resp.json()
# {"trust_score": 0.85, "sla_grade": "A", "total_calls": 1247}

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

dify - 💡(How to fix) Fix Feature: Add MCP server trust verification for tool provider connections