_ registry / mcp streamable-http · checked 28m ago

copilot-studio-friction-index

https://pcghrrzwqshejvifoxjq.supabase.co

Registry code: 6ee563600185aa3c

api record

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 or keywords; get_friction_record for the full dated record incl. solutions and evidence; list_frictions to browse; get_current_drift for what is currently broken or regressed; list_patterns/get_pattern for reusable prevention patterns. When…

endpoint
https://pcghrrzwqshejvifoxjq.supabase.co/functions/v1/friction-mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is copilot-studio-friction-index live?
Yes — it answered the hub's last check (checked 28m ago). It answered 100% of checks over the last 30 days.
Is copilot-studio-friction-index free to use?
Yes — the hub reached it with no key and no payment.
What tools does copilot-studio-friction-index have?
7 tools: lookup_error, get_pattern, search_frictions, get_friction_record, get_current_drift, list_frictions, list_patterns.
Is copilot-studio-friction-index safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.7%· all time 99.7%

latency
151ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 592 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • look up a copilot studio error
  • search known copilot studio issues
  • get current regressions
  • get prevention patterns
takes → gives
text → text, data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
3 open 4 never probed 3 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_current_drift reads open 5h ago

    What is currently broken or regressed in Microsoft Copilot Studio, per the continuously verified Friction Index: all records with status open or regressed (newest status change first) plus register health counts (total records, share verified within 90 days, status distribution).

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_frictions reads open 5h ago

    Browse the register: compact list of all published friction records, sorted by last-verified date (newest first). Filter by status and/or category.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "status": {
          "enum": [
            "open",
            "mitigated",
            "fixed",
            "regressed"
          ],
          "type": "string",
          "description": "Optional status filter: \"open\" (problem exists), \"mitigated\" (reliable workaround), \"fixed\" (resolved and re-verified), \"regressed\" (was fixed, is back)."
        },
        "category": {
          "enum": [
            "knowledge-grounding",
            "publish-channel",
            "auth-identity",
            "orchestration",
            "agent-flows",
            "llm-steps",
            "topics-variables",
            "tools",
            "alm-deployment",
            "licensing-cost",
            "governance-dlp",
            "observability",
            "security-defaults"
          ],
          "type": "string",
          "description": "Optional category filter."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • list_patterns reads open 5h ago

    All reusable build patterns that prevent whole classes of Copilot Studio friction before they happen (e.g. async continuation for the 100-second flow limit), each with its problem class and related records.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • lookup_error reads unknown 7h ago

    Exact/substring match against all known Copilot Studio error codes and error messages in the register. The fastest path when you have a verbatim error string (e.g. "FlowActionTimedOut"). Returns the matching record(s) with the citable URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "error"
      ],
      "properties": {
        "error": {
          "type": "string",
          "minLength": 3,
          "description": "The error code or error message, as verbatim as possible."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_pattern reads unknown 7h ago

    The complete prevention pattern for a slug: the pattern, when to use it, and step-by-step instructions as markdown, plus the friction records it protects against.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Pattern slug, e.g. \"async-continuation\" (from list_patterns)."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_frictions reads unknown 28m ago

    Ranked search over the Copilot Studio Friction Index. Exact error-code/message hits rank first, then title, alias, summary and symptom-checklist matches (solution bodies are NOT searched — an empty result means no record is indexed under these terms, not that the register lacks a fix). Use this when the user describes a Copilot Studio problem, symptom or keyword. Returns compact records with slug, status, severity, last-verified date and the citable powerleap.ch URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 25,
          "minimum": 1,
          "description": "Maximum results."
        },
        "query": {
          "type": "string",
          "minLength": 2,
          "description": "Error string, symptom or keywords, e.g. \"flow times out after 100 seconds\"."
        },
        "status": {
          "enum": [
            "open",
            "mitigated",
            "fixed",
            "regressed"
          ],
          "type": "string",
          "description": "Optional status filter: \"open\" (problem exists), \"mitigated\" (reliable workaround), \"fixed\" (resolved and re-verified), \"regressed\" (was fixed, is back)."
        },
        "category": {
          "enum": [
            "knowledge-grounding",
            "publish-channel",
            "auth-identity",
            "orchestration",
            "agent-flows",
            "llm-steps",
            "topics-variables",
            "tools",
            "alm-deployment",
            "licensing-cost",
            "governance-dlp",
            "observability",
            "security-defaults"
          ],
          "type": "string",
          "description": "Optional category filter."
        }
      },
      "additionalProperties": false
    }
    arguments 50 lines
  • get_friction_record reads unknown 7h ago

    The complete friction record for a slug: status, dates, confidence, severity, time cost, categories, channels, license context, error codes/messages, dated evidence list, and the six body sections as markdown (symptom checklist, cause, fix with solution classes, verification steps, fallback, prevention). Cite the returned URL; a German version exists at the german_version URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Record slug, e.g. \"flowactiontimedout\" (from search/list results)."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6ee563600185aa3c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6ee563600185aa3c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6ee563600185aa3c/badge.svg)](https://brick.blue/agent/6ee563600185aa3c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on supabase.co 123 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

115 more sit on this domain. All of them.