Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HornLib — Interactive French Horn F/Bb Double Horn Fingering & Harmonics Engine

REMOTE · HORNLIB.COM

Look up French Horn F/Bb double horn valve fingerings, trigger combinations & partials.

Available components

+2 this week 74 Trust /100

Last scanned (22 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 969 tokens (~121/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +48
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.10 ▲ functional
  • 10 Nov 26 −47
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.03 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://hornlib.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hornlib.com CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 6a6c4cb4500d75db0eac900472b69d08
SANs: hornlib.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of hornlib.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
hornlib.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hornlib.com/api/mcp Verified 200
http (plaintext) http://hornlib.com/api/mcp HTTPS enforced 301 https://hornlib.com/api/mcp
MCP tools · 8 exposed · ~945 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_horn_harmonic_series ~148

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.

NameTypeReqDescription
hornSidestringyesHorn side tube length: "F" (open fundamental F1) or "Bb" (trigger fundamental Bb1)
valvesstring–Valve combination (e.g. "0", "2", "1", "1-2", "2-3", "1-3", "1-2-3")

No output schema declared.

No examples provided.

diagnose_horn_intonation_and_hand_position ~79

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).

NameTypeReqDescription
topicstringyesAcoustic or intonation topic to diagnose

No output schema declared.

No examples provided.

generate_daily_horn_warmup_routine ~100

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.

NameTypeReqDescription
durationMinutesnumberyesAvailable warm-up duration in minutes (e.g. 15, 30, 45, 60)
focusAreastring–Primary technical focus area for the session

No output schema declared.

No examples provided.

get_orchestral_horn_excerpt_guide ~145

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).

NameTypeReqDescription
composerOrWorkstringyesComposer or orchestral work name (e.g. "Mozart 4", "Strauss Till", "Tchaikovsky 5", "Brahms 3", "Beethoven 7", "Mahler 5")

No output schema declared.

No examples provided.

lookup_french_horn_fingering ~113

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").

NameTypeReqDescription
notestringyesWritten note name with octave (e.g. "C4", "F4", "G4", "Bb4", "C5", "F5")

No output schema declared.

No examples provided.

lookup_horn_trill_fingering ~124

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).

NameTypeReqDescription
baseNotestringyesPrincipal written note of the trill (e.g. "F#4", "G4", "A4", "B4", "C5", "D5")
intervalstring–Trill interval above the principal note ("half-step" or "whole-step")

No output schema declared.

No examples provided.

recommend_beginner_horn_and_mouthpiece ~92

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.

NameTypeReqDescription
playerLevelstringyesPlayer experience level or orchestral role

No output schema declared.

No examples provided.

transpose_french_horn_pitch ~144

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.

NameTypeReqDescription
sourceCrookstringyesHistorical horn crook marked in the score (e.g. "Eb" for Beethoven Eroica, "D" for Bach/Mozart, "C" for Brahms)
writtenNotestringyesWritten note in the original orchestral score (e.g. "C4", "G4", "E5")

No output schema declared.

No examples provided.

Install

How do I install the HornLib — Interactive French Horn F/Bb Double Horn… MCP server?

HornLib — Interactive French Horn F/Bb Double Horn… is a hosted endpoint at https://hornlib.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · hornlib.com

# add to Claude Code
claude mcp add --transport http com-hornlib-mcp 'https://hornlib.com/api/mcp'
Common questions

What is the HornLib — Interactive French Horn F/Bb Double Horn… MCP server?

HornLib — Interactive French Horn F/Bb Double Horn… is an MCP server listed in the public MCP registry as com.hornlib/mcp. Look up French Horn F/Bb double horn valve fingerings, trigger combinations & partials. This page covers its hosted endpoint (https://hornlib.com/api/mcp).

Is the HornLib — Interactive French Horn F/Bb Double Horn… MCP server safe to use?

HornLib — Interactive French Horn F/Bb Double Horn… scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the HornLib — Interactive French Horn F/Bb Double Horn… MCP server expose?

HornLib — Interactive French Horn F/Bb Double Horn… exposes 8 tools: lookup_french_horn_fingering, transpose_french_horn_pitch, analyze_horn_harmonic_series, lookup_horn_trill_fingering, get_orchestral_horn_excerpt_guide, and 3 more. Their descriptions and schemas cost roughly 945 tokens of context every time the server is loaded.

Does the HornLib — Interactive French Horn F/Bb Double Horn… MCP server require authentication?

No. We connected to HornLib — Interactive French Horn F/Bb Double Horn… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the HornLib — Interactive French Horn F/Bb Double Horn… MCP server still maintained?

HornLib — Interactive French Horn F/Bb Double Horn… is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the HornLib — Interactive French Horn F/Bb Double Horn… MCP server?

VerifyMCP ran 13 checks on HornLib — Interactive French Horn F/Bb Double Horn…, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.