Unverified50% confidenceFactExact time
MCP connectors require the link to be a public HTTPS address; local services cannot be connected directly.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/30/2026
First Seen
Valid until: 1/28/2027
Sources
Related Entities
Related Claims
UnverifiedThe event capability depends on support on the MCP server side—if the server does not expose webhooks, Connect has nothing to subscribe to.74% similarUnverifiedThe older version of MCP (1.0) required remote servers to use persistent connections or sticky routing.74% similarUnverifiedUnder the old MCP specification, GitHub MCP and many distributed MCP servers could not support elicitation, because it requires cross-server communication to coordinate state and sessions.73% similarUnverifiedMCP connectors largely exist as community-driven open-source projects, lacking unified security review and signed distribution mechanisms.73% similarUnverifiedSiteCheck offers both OpenAPI and a remote MCP server as access methods, and the MCP endpoint address is https://api.sitecheck-api.workers.dev/mcp.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1115760API
curl https://kongchang.com/api/v1/knowledge/claims/1115760MCP
get_claim(id=1115760)