Skip to main content
Glama
649,985 tools. Updated 2026-10-08 14:57

"Edge Impulse" matching MCP tools:

  • Record that an owned ticket cannot complete until another owned ticket is done. The edge is never erased: correct a mistake with ticket_dependency_remove, which marks the edge removed and appends to a ledger rather than deleting anything. Re-adding the same prerequisite reinstates that original edge instead of creating a second one, so an edge removed and restored says so. An edge stops blocking when the prerequisite reaches done, and only then — archiving the prerequisite does not release it. Only epics are gated, so an edge on a task is recorded and reported but never blocks its completion. Rejections carry a stable code: dependency_self (422), dependency_duplicate, dependency_cycle, dependency_graph_too_large (409), ticket_not_found (404).
    ConnectorNo auth
  • Set how a layer ENTERS at the start of its on-timeline window and LEAVES at the end, instead of popping. The transition is EDGE-RELATIVE — only a length and a look are stored — so it rides the edge through every later trim, slide or clip retime. Prefer this over fade_layer / apply_preset whenever the intent is 'enters and leaves nicely': those write opacity keyframes at ABSOLUTE frames, which strand themselves the moment the edge moves, and clutter the timeline lanes. A layer created WITH a `block` is born carrying a short fade at each edge — whether you passed the block or the editor minted one — so check `inspect_layers` before adding one, rather than assuming there is none. Layers created before this default existed, and any edge cleared to "cut", carry nothing and do need setting. A layer with NO block is always-present, has no edges, and a transition on it is inert. Video clips default to a hard cut, because a hard cut between shots is the grammar of short-form video. kind "cut" clears the edge back to a hard cut. The length is a request: when the window is too short to hold both ramps they are squeezed proportionally at render time, and the stored values are left intact.
    Connector
    Destructive
    No auth
  • Permanently delete a dynamic endpoint (the server purges its public edge URL first). Unlike unpublish, this removes the resource entirely — it no longer appears in list_dynamic_endpoints. Cannot be undone.
    Connector
    Destructive
    OAuth
  • Only when the user asks to open or see their Edge page or Edge activity (for example "open my Edge page"): returns a private one-time link to it, single use, valid for 10 minutes. Reply with the returned line exactly. Never call it on your own initiative, never open the link yourself, and never put it in files, commits, issues or shared documents.
    ConnectorNo auth
  • Get a personalized market news briefing based on your validated edge library. Profiles your strategies, searches today's news for the instruments and setups you actually trade, and writes a concise digest connecting each headline to your specific book. Each news item includes a ↳ line tying it to your actual positions and edges (e.g. 'your ES momentum setups', 'your GC mean-reversion edge'). Requires at least 5 strong edges in your library. Costs credits.
    ConnectorNo auth
  • Records only an Edge rating of a skill you used: it does not change the user's files or task output and takes no action outside Edge. Retries with the same request_id never add a second rating. When the work is done, call it once, after the work rather than right after loading; its result is the Edge closing line to end your answer with. Rate a skill you actually followed with helped, hurt, no_difference or unclear, plus one short line on why; unclear and no_difference are fine. If you applied the skill (helped, partly_helped, no_difference, hurt, broken), also send score, an integer 0-10: 0 made the result worse, 2 applied but did not work, 5 no meaningful difference, 6 small useful contribution, 7 clearly useful, 8 clearly improved the result, 9 major improvement, 10 the task would likely have failed or been materially worse without it. A failure is a low score, not a skipped rating. Omit score for wrong_skill, loaded_not_used and unclear. The note is required for scores 0-2 and 9-10. Judge the outcome yourself; never ask the user. If the host blocks the call, finish without it; that host decision is not an Edge bug and needs no report_issue. The server identifies the skill from this request_id. Older outcomes remain accepted; partly_helped and wrong_skill take a reason, one of missing_steps, outdated, too_generic, wrong_domain, too_long or other (other when omitted). Notes over 280 characters are cut. If use_skill listed named parts for the skill, send applied_component_ids with up to two you actually applied. Keep the note free of the user's query, code, names and private data. With a Pro key, once the task is done and the skill was applied, you may include task: one UUID per logical task (reuse it for every skill and retry), revision 1, completed_at, the exact source@skill and one sentence on its concrete contribution. Raise revision only to correct a report. Edge returns the user's weekly tally; never invent or change that count. For a bug or idea about Edge itself, use report_issue instead.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    A Model Context Protocol server that exposes Microsoft Edge browsing history across multiple profiles, allowing listing profiles and fetching history for a given day.
    3
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Generates room impulse responses as WAV files from natural language descriptions, enabling agents to create realistic or arbitrary reverb for audio production.
    1
    MIT

Matching MCP Connectors

  • Phase III (FRC) — pre-promotion quality gate. Scores .faf content (edge Mk4) + estimates tokens and returns a deterministic promote/hold verdict BEFORE it goes to a Grok Collection. Promote IFF score >= min_score AND tokens <= max_tokens (defaults 85/8000). Edge parity with the local gate; the hold-hint can't list empty slots at the edge.
    ConnectorNo auth
  • Walk and verify a stamp's full provenance lineage by merkle_root. Use this when a stamp was created with derived_from links, to map what an output was built from. Returns a MAP of the graph (not a yes/no verdict): each node carries hash_binds and anchored, each edge carries edge_verified, and `valid` is true only if every node and edge checks out. A node whose payload was never published is an unresolved frontier (resolved:false). Read-only. Provenance, not truth.
    ConnectorNo auth
  • Phase III (FRC) — pre-promotion quality gate. Scores .faf content (edge Mk4) + estimates tokens and returns a deterministic promote/hold verdict BEFORE it goes to a Grok Collection. Promote IFF score >= min_score AND tokens <= max_tokens (defaults 85/8000). Edge parity with the local gate; the hold-hint can't list empty slots at the edge.
    ConnectorNo auth
  • Spot-ETF net flows (USD millions) — is the flow impulse turning or accelerating? The summary only gives point-in-time deltas; this exposes the trend: 30d/90d net flow, a direction label (inflows/outflows/flat) and a daily series (every US trading day: cumulative inflow + that day's net flow; `resolution` states points and spacing) so direction and speed are visible, not just a single delta. Read `impulse` for what the flow is doing — it has four states (accelerating / decelerating / reversal / flat) and is the field to quote. Two neighbouring fields measure different things and are easy to confuse: `acceleration_usd_m` is the signed difference last-30d minus prior-30d and gets LARGE precisely when the flow reverses, while the older boolean `accelerating` requires the same direction AND a bigger magnitude — so a swing from outflows to inflows shows a big positive `acceleration_usd_m` together with `accelerating: false`, which is correct and reads like a contradiction. `impulse` reports that case as 'reversal'. When `impulse` is 'reversal', `reversal_recovered_pct` says how much of the preceding counter-move has actually come back, with its denominator in `reversal_basis_usd_m` — quote it alongside, because a reversal in direction is not yet a reversal in the stock. Both are null otherwise. `source_inconsistencies` lists the days on which the source's own daily net flow and the change of its cumulative disagree (BTC: 2 of ~700 days, 2026-04-23/24 — the two-day sum matches, the day split does not); cumulative deltas and the 30d/90d windows are unaffected, per-day sums over those dates are. NYSE closing days that the source still lists come back with net_flow_usd_m null and market_closed: true (a closed market is not a zero flow). `availability` states when a day's flow was first known (measured from our own ingest; the source has no publication time) — use it for point-in-time work. For long windows pass `format: 'columns'` (parallel arrays, far smaller). Default BTC; pass asset=ETH or asset=SOL. Source SoSoValue. [Free tier]
    ConnectorNo auth
  • When: Use to relabel, retype, restyle (dashed, colour), reverse, put arrowheads on both ends, or re-point an existing edge, instead of disconnecting and reconnecting it. Change existing connections in place: relabel, retype, restyle (solid/dashed/dotted, colour), reverse the direction, put arrowheads on both ends, or re-point one end to another node. Identify each edge by source and target, or by `edge` (an id or "Source -> Target"). Change only the edges the user asked about: a request and its response are two edges on purpose, never merge them into one two-headed edge to tidy the drawing. Batch: `updates` (up to 60) takes a list; put every item in one call rather than one call per item. Operates on one Datadef diagram, named by diagram_id. Returns compact JSON: the ids it created, changed or removed, the diagram revision, a one-line summary and the next step. A viewer-role account is refused. Next: canvas_view to check the result.
    Connector
    Destructive
    API key
  • Mark an old version of your model as replaced by a newer one. The old id keeps working and its commons dedication (if any) stands — only the listing moves on to the successor. Both models must be yours. It also records a supersededBy edge (old → new), so sim_edges(old) and sim_neighbors(old, "supersededBy") show that the supersession happened. Re-pointing an old model to a different successor keeps the earlier edge too, and these edges carry no timestamp, so their order says nothing about which came last: the current successor is the `current` this tool returns (the model's own supersededBy record), not the edge list. Taxonomic edges on the old model are offered for migration to the current successor (sim_migration_offers, accepted with sim_accept_migration), never moved; structural and tool-written edges stay with it.
    Connector
    Destructive
    OAuth
  • Wire or unwire ONE edge between two EXISTING blocks of a canvas rig — 'connect the fetch step to the judge', 'route the critique back to revise when it says REVISE', 'disconnect A from B'. Identify both ends by node id, label, skill name, or 1-based position. Add `guard` ({source, op, value?}) to make the edge a CONDITIONAL route — how a loop gets its exit condition on a stateful_graph. `remove: true` drops the from→to edge instead. Re-wiring an edge that already exists UPDATES its kind/guard in place. Returns the fresh block-by-block summary incl. the full edge topology; the Builder canvas updates live. (rig_node_add's `after` wires only at creation — this is the tool for every rewiring after that.)
    ConnectorNo auth
  • Carry offered taxonomic edges of a superseded model forward to its current successor. edges lists 1 to 25 edge ids that sim_migration_offers(model) offered; pass successor (the current it returned) so a different current successor — a re-point or a chain that grew since — is refused rather than followed. Every edge is checked before anything is written (it must touch model, be offered, pass sim_link's check, you must own model or have authored the edge, and the edge it becomes must pass its predicate's write rule for you — hasMember only for the collection's owner); one failure refuses the call and writes nothing. Each accepted edge is written on the successor attributed to you, with no timestamp, plus a migratedFrom edge from it to the old edge (provenance; sim_edges(<new edge>) shows it, and sim_query closure over migratedFrom traces it back across several supersessions). The old edge stays. Re-running converges on the same ids; an edge you already linked the same way is reused (existing: true, keeping its own timestamp). A call stopped after some edges were written says which were and which were not. Needs sign-in with write scope (opens OAuth the first time); MCP only. Costs 1 compute token per call.
    Connector
    Destructive
    OAuth
  • Returns the free recoil of one to five firearms firing a load: the velocity each is pushed back at, the energy it takes and the impulse, by the free recoil formula SAAMI publishes, from the firearm's recorded mass and the muzzle velocity its own barrel gives the load. Use this tool when the question is how hard one firearm kicks against another. The catalog holds no powder charge, so without powder_charge_g only the bullet is counted and every figure is a lower bound; say so when you quote it. It is free recoil, not felt recoil, and does not count a muzzle brake.
    ConnectorAPI key
  • Creates a typed, directed edge between two pages — the knowledge graph's connective tissue. Canonical directions: PERSON owns WORKFLOW/SYSTEM, PERSON involved_in WORKFLOW, WORKFLOW uses SYSTEM, SYSTEM uses SYSTEM, PAIN_POINT affects WORKFLOW/SYSTEM/PERSON, DOCUMENT documents anything, relates_to as fallback. Idempotent on (from, to, kind) — re-creating an existing edge returns it. May return `needs_confirmation`; tell the user what you're proposing, wait for their approval, then re-call with the approvalId.
    ConnectorNo auth
  • Creates a typed, directed edge between two pages — the knowledge graph's connective tissue. Canonical directions: PERSON owns WORKFLOW/SYSTEM, PERSON involved_in WORKFLOW, WORKFLOW uses SYSTEM, SYSTEM uses SYSTEM, PAIN_POINT affects WORKFLOW/SYSTEM/PERSON, DOCUMENT documents anything, relates_to as fallback. Idempotent on (from, to, kind) — re-creating an existing edge returns it. May return `needs_confirmation`; tell the user what you're proposing, wait for their approval, then re-call with the approvalId.
    ConnectorNo auth
  • Report a bug or idea about Edge itself: an Edge call that failed or answered wrongly, a skill suggestion that did not fit, setup trouble, or a feature idea. You may call this on your own when an Edge call fails. A host approval denial is not an Edge failure; skip the blocked call and do not report it as an Edge bug. For how well a loaded skill did on the task, use rate_skill instead. Describe what happened without secrets or private user data. Include contact only if the user explicitly gave an email for this.
    ConnectorNo auth
  • Fetch complete details for a single organization (company, government entity, holding company) by canonical Scrutica ID. Returns: legal name, country of HQ, organization type, parent / subsidiary references, supply-chain edge counts. Use scrutica_query_export_controls for BIS designation details. Use scrutica_get_supply_chain for full edge graphs.
    ConnectorNo auth
  • List every published (public) Edge Lab research study: slug, title, published date, and URL. Returns the authoritative catalog so the answer comes from the real index rather than a guess. Takes no arguments.
    ConnectorNo auth
  • Surface the largest gaps between the model's win probability and the market. De-vigs each market's 1X2 decimal odds (removes the margin so implied probabilities sum to 1) and compares them to this server's own match-outcome probabilities — the same Elo/Poisson path ``football_match_predictor`` uses. Where the model probability exceeds the de-vigged market probability by at least ``min_edge``, the outcome is flagged with its edge and the model's fair odds. Args: team: Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to scan every WC 2026 odds event. min_edge: Minimum edge (model_prob - devigged_market_prob), 0..1. Default 0.05 (5 percentage points). Returns: data.value_bets: list of {event_id, home, away, outcome, model_prob, fair_odds, market_odds, edge, bookmaker}, sorted by edge descending. data.events_analysed: events with both teams rated (model-comparable). meta.estimated: true. meta.is_stale reflects the odds freshness.
    ConnectorNo auth