Blender integration through the Model Context Protocol
Look up standard F-side and Bb-trigger valve fingerings, concert pitch transposition (down a perfect fifth), and harmonic tendency notes for any written French Horn note (e.g. "C4", "F4", "G4", "Bb4", "C5", "F5").
A call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
What it does
Look up French Horn F/Bb double horn valve fingerings, trigger combinations & partials.
Quickstart
# 1 — sign in once: npx mcprush@latest login
# it asks for a key from mcprush.com/dashboard#access
# 2 — install
npx mcprush@latest add locatepic/hornlib-interactive-french-horn-f-bb-double-h-mcp
# 3 — ask your agent for something these tools do
# lookup_french_horn_fingering, transpose_french_horn_pitch, analyze_horn_harmonic_series and 5 more
Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.
HornLib — Interactive French Horn F/Bb Double Horn Fingering costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Claude Code reads MCPRUSH_KEY each time it connects, so the key stays out of its config: export your key from Access in your shell profile (macOS, Linux), or run setx MCPRUSH_KEY <your key> and open a new terminal (Windows). Or let npx mcprush@latest add locatepic/hornlib-interactive-french-horn-f-bb-double-h-mcp write the entry with the key for you; --scope user makes it available in every project.
claude mcp add --transport http --scope user hornlib-interactive-french-horn-f-bb-double-h-mcp https://mcprush.com/gw/hornlib-interactive-french-horn-f-bb-double-h-mcp/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Look up standard F-side and Bb-trigger valve fingerings, concert pitch transposition (down a perfect fifth), and harmonic tendency notes for any written French Horn note (e.g. "C4", "F4", "G4", "Bb4", "C5", "F5").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| note | string | yes | Written note name with octave (e.g. "C4", "F4", "G4", "Bb4", "C5", "F5") |
Transpose written French Horn parts from historical orchestral crooks (Horn in Eb, D, C, G, A, E, Bb-alto, Bb-basso) to modern Horn in F written pitch and Concert Pitch, with interval semitone shifts and clef rules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| writtenNote | string | yes | Written note in the original orchestral score (e.g. "C4", "G4", "E5") |
| sourceCrook | string | yes | Historical horn crook marked in the score (e.g. "Eb" for Beethoven Eroica, "D" for Bach/Mozart, "C" for Brahms) |
Analyze the natural harmonic overtone series (partials 2 through 16) for any F-horn or Bb-horn valve combination, returning equal-temperament cent deviations (e.g. -14 cents on 5th partial, -31 cents on 7th partial) and alternate valve solutions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hornSide | string | yes | Horn side tube length: "F" (open fundamental F1) or "Bb" (trigger fundamental Bb1) |
| valves | string | no | Valve combination (e.g. "0", "2", "1", "1-2", "2-3", "1-3", "1-2-3") |
Find optimal whole-tone and half-step trill fingerings on the F/Bb double horn, identifying whether a trill should be executed as a mechanical valve trill or a harmonic lip trill (common above written E5 on the F side).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseNote | string | yes | Principal written note of the trill (e.g. "F#4", "G4", "A4", "B4", "C5", "D5") |
| interval | string | no | Trill interval above the principal note ("half-step" or "whole-step") |
Retrieve audition preparation notes, recommended F/Bb trigger fingerings, breathing plans, and historical crook transpositions for standard orchestral French Horn excerpts (Mozart 4, Beethoven 3/7/9, Brahms 1/3, Mahler 5, Strauss Till Eulenspiegel / Ein Heldenleben, Tchaikovsky 5).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| composerOrWork | string | yes | Composer or orchestral work name (e.g. "Mozart 4", "Strauss Till", "Tchaikovsky 5", "Brahms 3", "Beethoven 7", "Mahler 5") |
Diagnose pitch tendencies, right-hand bell acoustics, and Stopped Horn (gestopft / +) transposition rules (transpose down a half-step on the F horn side to compensate for the +1/2 step acoustic shortening when sealing the bell).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Acoustic or intonation topic to diagnose |
Compare Kruspe wrap (Conn 8D style, dark orchestral projection, larger bell throat) vs Geyer/Knopf wrap (Yamaha 667/671, Alexander 103 style, smooth slurs, medium throat) and recommend mouthpiece cup depths and rim diameters by player level.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| playerLevel | string | yes | Player experience level or orchestral role |
Generate a structured daily French Horn warm-up schedule covering harmonic lip slurs, Farkas long tones, double/triple tonguing, low-register pedal tones, and dynamic control tailored to available practice time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| durationMinutes | number | yes | Available warm-up duration in minutes (e.g. 15, 30, 45, 60) |
| focusArea | string | no | Primary technical focus area for the session |
- Every tool, no call limit, and mcprush charges nothing
- A buyer key from your dashboard — the gateway refuses a call without one
- Answers through our gateway, so every call is in your log
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install HornLib — Interactive French Horn F/Bb Double Horn Fingering or to call it, and its free tier carries no monthly call limit.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| lookup_french_horn_fingering | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
The gateway serves every install the publisher’s current release, so a release cannot be pinned or rolled back to here yet. The history below is for reading; the current release on file is 1.0.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish HornLib — Interactive French Horn F/Bb Double Horn Fingering can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.