# Golova.Wiki — event equipment registry (remote · golova.wiki)

Open registry of event & AV equipment: models, specs, compatibility, rig weight and power.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `golova.wiki`: 63/100 (this document), [markdown](https://verifymcp.io/servers/wiki-golova-registry/api-mcp.md), [page](https://verifymcp.io/servers/wiki-golova-registry/api-mcp)

## Channel facts

- Endpoint: `https://golova.wiki/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 378 tokens (~75/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http wiki-golova-registry 'https://golova.wiki/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "wiki-golova-registry": {
      "url": "https://golova.wiki/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wiki-golova-registry": {
      "type": "http",
      "url": "https://golova.wiki/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.wiki-golova-registry]
url = "https://golova.wiki/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wiki-golova-registry": {
      "type": "remote",
      "url": "https://golova.wiki/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wiki-golova-registry --url 'https://golova.wiki/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wiki-golova-registry:
    url: "https://golova.wiki/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "wiki-golova-registry": {
      "Transport": "http",
      "Url": "https://golova.wiki/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add wiki-golova-registry -t streamable-http -u 'https://golova.wiki/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "wiki-golova-registry": {
      "type": "http",
      "url": "https://golova.wiki/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 63, +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.

### 2026-11-19 (score 62, +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.

### 2026-11-17 (score 61, +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.

### 2026-11-16 (score 60, 0)

- [security] 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
- [functional improvement] Schema quality: 89 → 75
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “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”

### 2026-11-15 (score 60)

First indexed and scored.

## MCP tools (5)

### `search_equipment` (~111 tokens)

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

Input parameters:

- `fits` (string): Item code: return only what is compatible with it (optional)
- `limit` (integer): How many to return (1-20, default 10)
- `query` (string, required): Search query (model, brand, code)
- `section` (string): Section slug to narrow the search (optional)

### `get_item` (~47 tokens)

Item card by canonical code (GW-XXXXXX): specifications, brand, section, compatible amplification.

Input parameters:

- `code` (string, required): Canonical code, e.g. GW-KBVNPE

### `find_compatible` (~65 tokens)

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.

Input parameters:

- `code` (string, required): Canonical item code

### `list_services` (~79 tokens)

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

Input parameters:

- `group` (string): Group slug (audio, lighting, logistics…), optional
- `lang` (string): en (default) or ru

### `rig_metrics` (~40 tokens)

Rig metrics for a list of item codes: total weight and power draw, plus a check for missing amplifiers.

Input parameters:

- `codes` (array, required): Item codes

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/wiki-golova-registry/api-mcp#diagnostics

## Score history

- 2026-11-21: 63
- 2026-11-20: 62
- 2026-11-19: 62
- 2026-11-18: 61
- 2026-11-17: 61
- 2026-11-16: 60
- 2026-11-15: 60

## Common questions

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

## Links

- Remote endpoint: https://golova.wiki/api/mcp
- Website: https://golova.wiki/
- Changelog RSS feed: https://verifymcp.io/servers/wiki-golova-registry/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wiki-golova-registry/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/wiki-golova-registry/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wiki-golova-registry/api-mcp
