eurorack

{
  "id": "aix_95e9d73c78",
  "name": "eurorack",
  "operator": "(unclaimed - source: registry-official · publisher: com.eurorackref)",
  "description": "Citation-anchored Eurorack module reference: specs, compatibility, and patch techniques.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-25",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "citation-check",
    "inventory-check",
    "media-catalog"
  ],
  "protocols": {
    "mcp": "https://eurorackref.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 1077,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 57,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-25T02:00:55.698Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://eurorackref.com/"
    },
    {
      "label": "repository",
      "url": "https://github.com/jallen/eurorack-reference"
    }
  ],
  "avatar": "https://github.com/jallen.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/jallen"
    }
  ],
  "profile": {
    "mcp_server": "eurorack-reference-mcp-server",
    "mcp_version": "0.16.0",
    "tool_count": 17,
    "tools": [
      {
        "name": "get_module",
        "description": "Return the full citation-anchored specification for one Eurorack module by id.\n\nUse this when the user names a specific module and you want its specs (HP, power, jacks, parameters), capabilities (envelope, quantizer, logic, etc.), or firmware history.\n\nThe typed prose fields (jack/parameter/mode descriptions) are paraphrased summaries; manual_outline → get_manual_chunk give the verbatim manual prose to quote against. How much to quote and overall answer shape live in SKILL.md (the \"Answer shape\" section + §8 citation) — this description is the data contract.\n\n## Provenance fields\n\nEvery typed "
      },
      {
        "name": "get_modules",
        "description": "Batched get_module — returns `{ modules: [...], errors: [...] }` with full citation-anchored specs for up to 25 modules in one call.\n\nPrefer this over multiple get_module calls when you have a known list of modules to fetch (e.g. preparing to call draw_patch_diagram across N modules, comparing several candidates side-by-side). One round trip vs. N.\n\nArgs:\n  - module_ids: array of \"<manufacturer-id>/<module-slug>\" strings. Up to 25 per call; duplicates are deduplicated.\n\nOptional args (apply to every module in the batch, same semantics as get_module):\n  - view: \"concise\" returns the id-card sub"
      },
      {
        "name": "visualize_module",
        "description": "Module visualization tool. Use when the user wants to understand how a module's modes work, how parameters change between modes, or what a specific mode does — a visualization communicates the per-mode behavior better than prose. The host renders the result inline in the chat as an interactive visualization (mode buttons, per-mode descriptions, schematic curves); you do not need to build an artifact yourself — just call this tool.\n\nDo not use for general module specs (HP, jacks, capabilities) — call get_module instead.\n\nAfter calling, your prose can reference what the user is seeing in the vis"
      },
      {
        "name": "search_modules",
        "description": "Search the corpus for Eurorack modules matching a combination of filters.\n\nFilters compose with AND. Omit any filter to leave that dimension unrestricted. The result is sorted by module name; pagination metadata in the response envelope lets you page through long result sets.\n\nArgs:\n  - capability  (string): capability id, e.g. 'envelope-generator', 'clock-source'. Run a search with NO capability filter to get the full capability taxonomy (ids + labels + counts) in _meta.taxonomy. Retired/variant slugs resolve via the capability_aliases layer (e.g. 'low-pass-gate' → 'lowpass-gate', 'quantiser'"
      },
      {
        "name": "resolve_modules",
        "description": "Bulk fuzzy name → id resolver. Pass a list of module NAMES (the way a user writes their rack — \"Maths\", \"Plaits\", \"Pamela's New Workout\", \"Morph 4\") and get back, per name, the best-matching corpus module id plus recovery affordances. This is the \"import my rack\" tool: resolving a 60-module inventory is ONE call here, not 60 search_modules calls.\n\nUse this the moment a user gives you a list of module names to map onto the corpus — before get_modules / draw_patch_diagram / reachable_techniques / rack_redundancy, all of which want ids. Feed the resolved best_match.id into those.\n\nFor each input "
      },
      {
        "name": "search_manual",
        "description": "Full-text search across parsed module manuals, product pages, and firmware release notes.\n\nUse this only when the question is about content that lives in continuous prose rather than in typed fields:\n  - Procedural: calibration sequences, button combos, factory-reset steps, save/load procedures.\n  - Diagnostic: LED color meanings, error indicators, troubleshooting trees.\n  - Firmware specifics beyond the short notes on firmware_versions (which only carry the headline change).\n  - Panel walkthroughs and prose explanations that aren't captured as parameters/jacks/zones.\n\nDo NOT call this for con"
      },
      {
        "name": "get_manual_chunk",
        "description": "Read one manual chunk by id to ground your answer in the manufacturer's documentation — the drill-in partner to get_module's manual_outline. Use it when a claim (voltage range, behavior, calibration step) benefits from the source's own account.\n\n**Read the chunk, then answer in your own words and point the user to the source (audit_url) to verify.** Paraphrase the substance; do not paste the chunk back as your reply. Quote verbatim only when the exact wording is load-bearing for a specific contested detail, and then only a short phrase. Citation style is SKILL.md §8 (cite-and-point, don't repr"
      },
      {
        "name": "find_compatible_with",
        "description": "Return modules that have a typed compatibility relationship with the given module. Both edge directions are returned and tagged via the per-match `direction` field — so a single call answers both \"what is X a R for?\" and \"what is a R for X?\".\n\n`relationship` is OPTIONAL. Omit it to get EVERY edge touching the module across all relationship kinds — the bare \"what pairs with / relates to X?\" question — with each match self-describing via its own `relationship`. Pass a relationship to restrict to that one kind. Prefer the relationship-less call when you don't already know which kind exists; reach"
      },
      {
        "name": "reachable_pairings",
        "description": "Given a rack (a set of module ids the user owns), rank the modules NOT in the rack by how many rack members they pair with. The set-level companion to find_compatible_with: where that answers \"what pairs with module X?\", this answers \"given my whole rack, what single module should I add — the one that pairs with the most of what I already have?\".\n\nThe ranking signal is `pair_count` — the number of DISTINCT rack members a candidate pairs with. A module that modulates five of your modules ranks above one that modulates one. This aggregate is the point: you can't get it from per-module find_compa"
      },
      {
        "name": "search_techniques",
        "description": "Return canonical synthesis / patching techniques with role-keyed module realizations drawn from the corpus.\n\nUse this when the user asks \"how do I do X?\" with X being a recognisable technique (low-pass-gate plucks, pinged-filter percussion, parallel multiband processing, complex-oscillator FM, karplus-strong pluck, clocked-delay feedback, modal-resonator excitation, wavefolder harmonics, envelope-follower ducking, Maths-style function-generator omnibus). It's also the right tool when the user has a module and asks \"what's this good for?\" — pass filter.module_id to retrieve every technique that"
      },
      {
        "name": "find_role_realizations",
        "description": "For a (technique_id, role_id) pair, return modules that can fill the role, ranked by affordance match.\n\nUse this when the user has named a technique and you need to recommend modules for a specific role within it (e.g., \"what should I use for the lpg role in a lowpass-gate-pluck patch?\"). Optionally pass available_modules to restrict the search to the user's rack — the tool surfaces both documented realizations in the rack AND undocumented candidates whose capability tags match the role's required affordances (or, for roles that declare only optional affordances, those optional ones).\n\nThis to"
      },
      {
        "name": "reachable_techniques",
        "description": "Given a rack (the module ids the user owns), return which canonical patch techniques the rack can realize, and which it is one module away from. The set-level companion to find_role_realizations: where that answers \"which module fills role R in technique T?\", this answers the rack owner's actual question — \"given everything I own, what can I actually do, and what am I close to?\".\n\nThis is the right tool the moment a user gives you their modules and asks an open \"what can I do / what can this rack do / what am I missing?\" question — instead of guessing techniques from training priors or calling"
      },
      {
        "name": "rack_redundancy",
        "description": "Call this when the user asks what they can SELL, remove, downsize, or trim — \"what can I sell?\", \"which modules are redundant?\", \"what's doing double duty?\", \"I have too many modules, what can go?\", \"what's not pulling its weight?\". The inverse of reachable_techniques: where that adds, this prunes.\n\nGiven the user's COMPLETE rack, it runs a leave-one-out over the same technique matcher reachable_techniques uses — for each module, does removing it cost any currently-reachable technique? Returns three buckets plus the overlap map:\n  - load_bearing: removing the module drops ≥1 reachable techniqu"
      },
      {
        "name": "lookup_concept",
        "description": "Return a canonical definition for a primitive Eurorack / synthesis concept and its relations to other concepts in the corpus.\n\nUse this for VOCABULARY questions, not module questions — when the user is asking what a term means or how two terms relate, not which modules implement it. Typical shapes:\n\n  - \"Is four-quadrant mult the same as through-zero AM?\" → lookup_concept(\"four-quadrant mult\")\n  - \"What's the difference between a gate and a trigger?\" → lookup_concept(\"gate\")\n  - \"Modular signal level vs line level — when does it matter?\" → lookup_concept(\"modular signal level\")\n  - \"Are clock "
      },
      {
        "name": "get_source",
        "description": "Return provenance metadata for one source by integer source_id.\n\nSources include manufacturer manuals, product pages, firmware notes, schematics, errata, and (in v2) field notes. Source ids are surfaced wherever facts cite their origin — in get_module's reference list, in the audit page citation links, and (in v2) in the claims table.\n\nArgs:\n  - source_id (integer, required)\n\nReturns metadata only — not the document content. The audit_url field links to the audit site's per-source page where the document can be viewed. The archived_url field is a path on the worker that streams the archived by"
      },
      {
        "name": "draw_patch_diagram",
        "description": "Patch diagram tool. Use when the user describes routing across multiple Eurorack corpus modules. Renders modules as boxes laid out by wire topology (matrix-shaped patches anchor on a hub; otherwise modules step left-to-right by signal-flow rank), jacks as colored ports keyed to signal type, wires as bezier curves. Inline SVG on claude.ai surfaces (web, Desktop chat, mobile); JSON elsewhere. (When to *offer* a diagram unprompted: SKILL.md §4.)\n\n**Trigger phrases:** \"show me the patch\", \"draw what I just described\", \"remind me what's connected to what\", \"explain the routing\", or any time you'd o"
      },
      {
        "name": "report_gap",
        "description": "Report when this MCP server couldn't fully answer a question. Not a query tool — calling this writes a feedback record.\n\nCall this proactively — without being asked — whenever you hit one of:\n  - missing_field: a field you expected on a module wasn't present (e.g. \"I needed the LFO frequency range on Pamela's New Workout and parameter_zones didn't have it\").\n  - missing_module: a module the user asked about isn't in the corpus yet.\n  - tool_confusion: a tool's behavior surprised you (wrong shape, missing filter, ambiguous enum value, unclear description).\n  - empty_result: a reasonable query c"
      }
    ],
    "profiled_at": "2026-09-25T02:00:55.698Z"
  },
  "unreachable": false
}