Golova.Wiki — event equipment registry
REMOTE · GOLOVA.WIKI
Open registry of event & AV equipment: models, specs, compatibility, rig weight and power.
Available components
Last scanned (22 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 Nov 2026.
Category IoT and Hardware
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 Security57
- 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 5 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
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 378 tokens (~75/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_compatible” rewrote its description, which is the text the model reads security
- Tool “get_item” rewrote its description, which is the text the model reads security
- Tool “list_services” rewrote its description, which is the text the model reads security
- Tool “rig_metrics” rewrote its description, which is the text the model reads security
- Tool “search_equipment” rewrote its description, which is the text the model reads security
- Schema quality: 89 → 75 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- “find_compatible” reworded the description of “code” cosmetic
- “get_item” reworded the description of “code” cosmetic
- “list_services” reworded the description of “group” cosmetic
- “list_services” reworded the description of “lang” cosmetic
- “rig_metrics” reworded the description of “codes” cosmetic
- “search_equipment” reworded the description of “fits” cosmetic
- “search_equipment” reworded the description of “limit” cosmetic
- “search_equipment” reworded the description of “query” cosmetic
- “search_equipment” reworded the description of “section” cosmetic
- 15 Nov 26 60
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 21 Nov 2026 · Probed https://golova.wiki/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=golova.wiki | CN=YR2,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | RSA 4096 | SHA256-RSA | 5462a232d1fb846a958dc404e3c60e95059 |
| SANs: golova.wiki, www.golova.wiki | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of golova.wiki. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| wiki. | DS published | 46628 | 13 | Verified |
| golova.wiki. | 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://golova.wiki/api/mcp | Verified | 200 | |
| http (plaintext) | http://golova.wiki/api/mcp | HTTPS enforced | 301 | https://golova.wiki/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 →
find_compatible ~65
What fits an item and what it fits: compatibility links (stands, amplifiers, cases, cables, accessories, consumables) with conditions and trust level, plus amplifiers and processors named in the specs. By code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Canonical item code |
No output schema declared.
No examples provided.
get_item ~47
Item card by canonical code (GW-XXXXXX): specifications, brand, section, compatible amplification.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Canonical code, e.g. GW-KBVNPE |
No output schema declared.
No examples provided.
list_services ~79
Registry of event industry services: groups (sound, lighting, rigging, logistics, crew…) and the services in them with canonical slugs. Optionally one group and a language (ru|en).
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Group slug (audio, lighting, logistics…), optional |
| lang | string | – | en (default) or ru |
No output schema declared.
No examples provided.
rig_metrics ~40
Rig metrics for a list of item codes: total weight and power draw, plus a check for missing amplifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | yes | Item codes |
No output schema declared.
No examples provided.
search_equipment ~111
Search the equipment registry by model name, brand or code, ranked by relevance. Optionally narrow to a section (slug, e.g. line-array, moving-head).
| Name | Type | Req | Description |
|---|---|---|---|
| fits | string | – | Item code: return only what is compatible with it (optional) |
| limit | integer | – | How many to return (1-20, default 10) |
| query | string | yes | Search query (model, brand, code) |
| section | string | – | Section slug to narrow the search (optional) |
No output schema declared.
No examples provided.
How do I install the Golova.Wiki — event equipment registry MCP server?
Golova.Wiki — event equipment registry is a hosted endpoint at https://golova.wiki/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 · golova.wiki
claude mcp add --transport http wiki-golova-registry 'https://golova.wiki/api/mcp'
What is the Golova.Wiki — event equipment registry MCP server?
Golova.Wiki — event equipment registry is an MCP server listed in the public MCP registry as wiki.golova/registry. Open registry of event & AV equipment: models, specs, compatibility, rig weight and power. This page covers its hosted endpoint (https://golova.wiki/api/mcp).
Is the Golova.Wiki — event equipment registry MCP server safe to use?
Golova.Wiki — event equipment registry scores 63 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 Golova.Wiki — event equipment registry MCP server expose?
Golova.Wiki — event equipment registry exposes 5 tools: search_equipment, get_item, find_compatible, list_services, rig_metrics. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.
Does the Golova.Wiki — event equipment registry MCP server require authentication?
No. We connected to Golova.Wiki — event equipment registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Golova.Wiki — event equipment registry MCP server still maintained?
Golova.Wiki — event equipment registry 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 Golova.Wiki — event equipment registry MCP server?
VerifyMCP ran 12 checks on Golova.Wiki — event equipment registry, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Golova.Wiki — event equipment registry: Authorization. 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.