MCP server list / copilot-studio-friction-index
Evidence-based register of known Copilot Studio errors and limits, with dated, human-verified fixes.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 199.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 312 ms.
- Address
- https://pcghrrzwqshejvifoxjq.supabase.co/
functions/ v1/ friction-mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.AdrianStauffer/
copilot-studio-friction-index - Transport
- streamable HTTP
streamable-http - Host
pcghrrzwqshejvifoxjq.supabase.co
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- copilot-studio-friction-index
- Version:
- 1.0.0
- MCP features it lists:
- tools
- Tool names:
search_frictionslookup_errorget_friction_recordlist_frictionsget_current_driftlist_patternsget_pattern- Instructions excerpt:
- The Copilot Studio Friction Index (https://powerleap.ch/friction/) is a living, versioned, evidence-based register of known obstacles, errors and limits when building Microsoft Copilot Studio agents — every record is dated, human-verified and carries a fix path. Use lookup_error when you have a verbatim error code or message; search_frictions for symptoms …
Reported Aug 17, 2026, 05:06 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 187 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 173 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 212 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 312 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.