HumMatch
REMOTE · HUMMATCH.ME · SCANNED SEP 21
Match singers to songs by vocal range: score fit, karaoke difficulty, and voice type.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 862 tokens (~143/item across 6 items; 5 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the HumMatch MCP server?
HumMatch is a hosted endpoint at https://hummatch.me/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 · hummatch.me
claude mcp add --transport http me-hummatch-hummatch 'https://hummatch.me/api/mcp'
{
"mcpServers": {
"me-hummatch-hummatch": {
"url": "https://hummatch.me/api/mcp"
}
}
} {
"servers": {
"me-hummatch-hummatch": {
"type": "http",
"url": "https://hummatch.me/api/mcp"
}
}
} [mcp_servers.me-hummatch-hummatch] url = "https://hummatch.me/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"me-hummatch-hummatch": {
"type": "remote",
"url": "https://hummatch.me/api/mcp",
"enabled": true
}
}
} openclaw mcp add me-hummatch-hummatch --url 'https://hummatch.me/api/mcp' --transport streamable-http
mcp_servers:
me-hummatch-hummatch:
url: "https://hummatch.me/api/mcp" {
"McpServers": {
"me-hummatch-hummatch": {
"Transport": "http",
"Url": "https://hummatch.me/api/mcp"
}
}
} assistant mcp add me-hummatch-hummatch -t streamable-http -u 'https://hummatch.me/api/mcp'
{
"mcpServers": {
"me-hummatch-hummatch": {
"type": "http",
"url": "https://hummatch.me/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 31 Aug 26 +1
- Stability: 0.97 → pass security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 0
- Schema quality: 168 → 143 ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- First check of Schema quality: 100 functional
- New resource “hummatch-matches-widget” functional
- 12 Aug 26 0
- Tool “check_song_fit” now declares an output schema ▲ functional
- Tool “get_vocal_profile” now declares an output schema ▲ functional
- Tool “group_song_fit” now declares an output schema ▲ functional
- Tool “recommend_songs” now declares an output schema ▲ functional
- Tool “search_songs” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
- MCP protocol version: 2026-07-28 → 2025-11-25 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 Sept 2026 · Probed https://hummatch.me/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hummatch.me | CN=WE1,O=Google Trust Services,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 928ec90626327dc00ee39c78b9cf3996 |
| SANs: hummatch.me | ||||||
| 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 hummatch.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| hummatch.me. | absent | 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://hummatch.me/api/mcp | Verified | 200 | |
| http (plaintext) | http://hummatch.me/api/mcp | HTTPS enforced | 301 | https://hummatch.me/api/mcp |
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 →
check_song_fit Score one song for a voice ~167
Score a specific catalog song against a singer's range and explain why it fits or does not, including a suggested key to transpose to. Call this when someone asks whether they can sing a particular song. Resolve the song with search_songs first to get its slug.
| Name | Type | Req | Description |
|---|---|---|---|
| rangeHigh | string | yes | Highest comfortable note, as a note name like "C5" or a raw MIDI number. |
| rangeLow | string | yes | Lowest comfortable note, as a note name like "D3" or a raw MIDI number. |
| slug | string | yes | The catalog slug of the song, from search_songs. |
| voiceType | string | – | Optional voice type hint (soprano, mezzo, alto, tenor, baritone, bass). Inferred from the range when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | yes | – |
| difficultyScore | integer|null | – | Karaoke difficulty, 0-100. Higher is harder. |
| fitDetails | object | – | Labels behind the scores. |
| genre | string | – | – |
| highNote | integer|null | – | Highest note of the song as a MIDI number. |
| highNoteName | string | – | Same as highNote, as a note name like "C#5". |
| likelyVoiceFit | string | – | – |
| lowNote | integer|null | – | Lowest note of the song as a MIDI number. |
| lowNoteName | string | – | Same as lowNote, as a note name like "G2". |
| matchScore | integer | yes | Overall suitability for this voice, 0-100. |
| rangeConfidence | string | yes | How the range was established, strongest first. "manual_research" was researched against sheet music or a score and is the most trustworthy tier. "estimated" was derived from published sources rather… |
| rangeSource | string | – | Provenance tag for the range, e.g. "estimated_curated_seed". |
| reason | string | – | Plain-language verdict. |
| riskWarning | string | – | – |
| slug | string | yes | Catalog slug; the identifier check_song_fit takes. |
| suggestedKey | string | – | Transposition advice, e.g. "Try a lower key". |
| tessituraScore | integer | – | How comfortable the song sits where the voice spends most time, 0-100. |
| title | string | yes | – |
| url | string | – | Canonical HumMatch page for the song. |
| vocalFitScore | integer | – | How well the song range sits inside the singer range, 0-100. |
| voiceTypeFitScore | integer | – | Fit against the voice type lane, 0-100. Can be high while matchScore is low when the range still exceeds the singer. |
| whyItFits | string | – | – |
| year | integer|null | – | – |
No examples provided.
get_vocal_profile Build a vocal profile ~144
Turn a singer's vocal range into a normalized HumMatch vocal profile: a persistent Vocal ID, voice type, and tone label. Call this first when you know someone's range and want a profile to reuse across the other HumMatch tools.
| Name | Type | Req | Description |
|---|---|---|---|
| rangeHigh | string | yes | Highest comfortable note, as a note name like "C5" or a raw MIDI number. |
| rangeLow | string | yes | Lowest comfortable note, as a note name like "D3" or a raw MIDI number. |
| voiceType | string | – | Optional voice type hint (soprano, mezzo, alto, tenor, baritone, bass). Inferred from the range when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| humProfile | object | – | Underlying measurements. Timbre fields stay null until an actual hum recording has been analyzed. |
| rangeHigh | integer | yes | Highest comfortable note as MIDI. |
| rangeLow | integer | yes | Lowest comfortable note as MIDI. |
| toneLabel | string | – | – |
| vocalId | string | yes | Human-readable profile label, e.g. "Tenor - Balanced tone". |
| voiceType | string | yes | – |
No examples provided.
group_song_fit Find songs a group can sing together ~79
Given two or more singers' ranges, find the vocal range they share and the songs that sit inside it. Call this for karaoke night with friends, a duet, a choir or worship team, or any "what can we all sing" question.
| Name | Type | Req | Description |
|---|---|---|---|
| profiles | array | yes | Two or more singers, each with a rangeLow and rangeHigh. |
| Name | Type | Req | Description |
|---|---|---|---|
| sharedRange | object | yes | The overlap every supplied singer can reach. Null bounds mean no shared range exists. |
| songs | array | yes | – |
No examples provided.
recommend_songs Find songs that fit a voice ~195
Rank the HumMatch catalog for one singer and return the songs they can actually sing, scored for range fit, karaoke difficulty, and voice-type suitability. Call this when someone asks what they should sing, what suits their voice or range, or wants karaoke song suggestions. Returns a ranked list plus named buckets (safest picks, easy wins, crowd pleasers, songs to avoid).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many songs to return per bucket (default 12, max 50). |
| rangeHigh | string | yes | Highest comfortable note, as a note name like "C5" or a raw MIDI number. |
| rangeLow | string | yes | Lowest comfortable note, as a note name like "D3" or a raw MIDI number. |
| voiceType | string | – | Optional voice type hint (soprano, mezzo, alto, tenor, baritone, bass). Inferred from the range when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| bestSafePicks | array | – | Lowest-risk choices. |
| confidenceTier | string | – | – |
| easyWins | array | – | Comfortable and easy to sing. |
| groupFriendly | array | – | Work well with other singers. |
| matches | array | yes | Ranked best matches overall. |
| popularCrowdPleasers | array | – | Well-known songs that still fit. |
| rangeHigh | integer | – | – |
| rangeLow | integer | – | – |
| riskyPicksToAvoid | array | – | Scored, but they exceed the comfortable range. |
| vocalId | string | yes | – |
| voiceType | string | yes | – |
No examples provided.
search_songs Search the song catalog ~154
Search HumMatch by song title or artist. Use this to resolve a song someone named into the catalog slug that check_song_fit needs, or to look up a song's measured vocal range. Pass rangeLow/rangeHigh as well to score every result against that voice and get the hits ranked by fit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results (default 20, max 50). |
| q | string | yes | Search text: a song title, an artist, or both. |
| rangeHigh | string | – | Optional. Highest note of the singer, to score and rank the results by fit. |
| rangeLow | string | – | Optional. Lowest note of the singer, to score and rank the results by fit. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| query | string | yes | – |
| songs | array | yes | Results. Scored fields are present only when rangeLow and rangeHigh were supplied. |
No examples provided.
What is the HumMatch MCP server?
HumMatch is an MCP server listed in the public MCP registry as me.hummatch/hummatch. Match singers to songs by vocal range: score fit, karaoke difficulty, and voice type. This page covers its hosted endpoint (https://hummatch.me/api/mcp).
Is the HumMatch MCP server safe to use?
HumMatch scores 87 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 HumMatch MCP server expose?
HumMatch exposes 5 tools: get_vocal_profile, recommend_songs, search_songs, check_song_fit, group_song_fit. Their descriptions and schemas cost roughly 739 tokens of context every time the server is loaded.
Does the HumMatch MCP server require authentication?
No. We connected to HumMatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HumMatch MCP server still maintained?
HumMatch is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.