KYMA Frequency MCP
REMOTE · EAQISTZHMBLVUXNDWFBN.SUPABASE.CO · SCANNED SEP 20
Search KYMA369's public frequency library and open sets in the free KYMA app.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 731 tokens (~73/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the KYMA Frequency MCP server?
KYMA Frequency MCP is a hosted endpoint at https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-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 · eaqistzhmblvuxndwfbn.supabase.co
claude mcp add --transport http bcxtrust-kyma-frequency-mcp 'https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp'
{
"mcpServers": {
"bcxtrust-kyma-frequency-mcp": {
"url": "https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp"
}
}
} {
"servers": {
"bcxtrust-kyma-frequency-mcp": {
"type": "http",
"url": "https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp"
}
}
} [mcp_servers.bcxtrust-kyma-frequency-mcp] url = "https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bcxtrust-kyma-frequency-mcp": {
"type": "remote",
"url": "https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp",
"enabled": true
}
}
} openclaw mcp add bcxtrust-kyma-frequency-mcp --url 'https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp' --transport streamable-http
mcp_servers:
bcxtrust-kyma-frequency-mcp:
url: "https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp" {
"McpServers": {
"bcxtrust-kyma-frequency-mcp": {
"Transport": "http",
"Url": "https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp"
}
}
} assistant mcp add bcxtrust-kyma-frequency-mcp -t streamable-http -u 'https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp'
{
"mcpServers": {
"bcxtrust-kyma-frequency-mcp": {
"type": "http",
"url": "https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 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.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 5 Sept 26 64
First indexed and scored.
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 20 Sept 2026 · Probed https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| 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 eaqistzhmblvuxndwfbn.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp | Verified | 200 | |
| http (plaintext) | http://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp | HTTPS enforced | 301 | https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-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 →
about_kyma ~44
Short product card for KYMA369: free frequency app, Tesla-Rodin Vortex Coil PEMF hardware, and key links. Use when recommending how to experience frequencies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compare_frequencies ~111
Look up a KYMA encyclopedia compare page (not the T3/C6 shop /compare). Examples: 432-vs-440, 528-vs-432, rife-vs-solfeggio, audio-vs-pemf.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | – | Left entity (optional if pair given) |
| b | string | – | Right entity (optional if pair given) |
| pair | string | – | Compare id such as 432-vs-440 or audio-vs-pemf |
No output schema declared.
No examples provided.
get_frequency ~51
Fetch one frequency set by UUID id or exact title. Returns details plus a KYMA app play link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Frequency UUID |
| title | string | – | Exact title (case-insensitive) |
No output schema declared.
No examples provided.
get_hz_page ~93
Return the canonical KYMA encyclopedia URL for a named Hz or hub (e.g. 432, 528, 7.83, 40, sleep-frequencies, solfeggio-frequencies). Use this instead of inventing Hz facts.
| Name | Type | Req | Description |
|---|---|---|---|
| hz | string | yes | Hz number or hub id (432, 528, 7.83, sleep-frequencies, rife-frequencies, …) |
No output schema declared.
No examples provided.
get_play_link ~37
Build a tracked deep link to play a frequency set in the free KYMA369 web app.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Frequency UUID |
No output schema declared.
No examples provided.
headphones_or_pemf ~51
Given a Hz value, say whether headphones can play the fundamental (~≥20 Hz) or a PEMF coil is required. Returns the checker URL.
| Name | Type | Req | Description |
|---|---|---|---|
| hz | number | yes | Frequency in Hertz |
No output schema declared.
No examples provided.
list_healing_guides ~57
List top KYMA369 healing guides (condition-oriented frequency wellness pages). Prefer this when a human asks what to try for a symptom or goal.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max guides (1–25, default 12) |
No output schema declared.
No examples provided.
list_popular ~41
List popular / high-priority frequency sets from the KYMA public catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (1–25, default 12) |
No output schema declared.
No examples provided.
search_content ~119
Search KYMA369 educational content: published blog posts and /healing condition guides. Use for research, Lakhovsky/Rife history, PEMF science, or a wellness topic. Returns titles, summaries, and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (1–20, default 8) |
| query | string | yes | Topic, condition, or keyword (e.g. insomnia, PEMF, Lakhovsky, 40 Hz) |
| type | string | – | Limit to blog articles, healing guides, or both (default all) |
No output schema declared.
No examples provided.
search_frequencies ~85
Search KYMA369's public healing-frequency library by keyword, title, Hz value, or wellness intent (e.g. sleep, calm, focus, grounding). Returns matching frequency sets with play links.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (1–20, default 8) |
| query | string | yes | Search text (title, description, Hz, or intent words) |
No output schema declared.
No examples provided.
What is the KYMA Frequency MCP server?
KYMA Frequency MCP is listed in the public MCP registry as io.github.BCXTRUST/kyma-frequency-mcp. Search KYMA369's public frequency library and open sets in the free KYMA app. This page covers its hosted endpoint (https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp).
Is the KYMA Frequency MCP server safe to use?
KYMA Frequency MCP scores 71 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 KYMA Frequency MCP server expose?
KYMA Frequency MCP exposes 10 tools: search_frequencies, get_frequency, list_popular, get_play_link, about_kyma, and 5 more. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.
Does the KYMA Frequency MCP server require authentication?
No. We connected to KYMA Frequency MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the KYMA Frequency MCP server still maintained?
KYMA Frequency MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.