# SofiaStage Events (remote · api.sofiastage.com)

Read-only tools for current SofiaStage events, venues, cities, performers, and editorial.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `api.sofiastage.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-sofiastage-events/api.md), [page](https://verifymcp.io/servers/com-sofiastage-events/api)

## Channel facts

- Endpoint: `https://api.sofiastage.com/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-09-22.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 535 tokens (~76/item across 7 items; 5 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 42% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the SofiaStage Events MCP server?

SofiaStage Events is a hosted endpoint at https://api.sofiastage.com/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 com-sofiastage-events 'https://api.sofiastage.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-sofiastage-events": {
      "url": "https://api.sofiastage.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-sofiastage-events": {
      "type": "http",
      "url": "https://api.sofiastage.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-sofiastage-events]
url = "https://api.sofiastage.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sofiastage-events": {
      "type": "remote",
      "url": "https://api.sofiastage.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-sofiastage-events --url 'https://api.sofiastage.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-sofiastage-events:
    url: "https://api.sofiastage.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-sofiastage-events": {
      "Transport": "http",
      "Url": "https://api.sofiastage.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-sofiastage-events -t streamable-http -u 'https://api.sofiastage.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-sofiastage-events": {
      "type": "http",
      "url": "https://api.sofiastage.com/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-09-22 (score 83, +1)

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

### 2026-09-20 (score 82, +1)

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

### 2026-09-18 (score 81, +1)

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

### 2026-09-16 (score 80, +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.

### 2026-09-14 (score 79, +1)

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

### 2026-09-12 (score 78, +1)

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

### 2026-09-10 (score 77, +1)

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

### 2026-09-07 (score 76, +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.

## MCP tools (5)

### `search_events` (~218 tokens)

Search SofiaStage events

Search current cultural events by Sofia/all-city scope, city, date, local time, venue, title, performer, or editorial collection. Returns stable event IDs and cursor pagination.

Input parameters:

- `city` (string): City name. Providing a city takes precedence over the Sofia default.
- `date_from` (string)
- `date_to` (string)
- `editorial` (string): Editorial collection or extra name.
- `include` (array)
- `limit` (integer)
- `page_token` (string)
- `performer` (string): Performer or creative-team name.
- `query` (string): Performance-title search text. Bulgarian and Latin transliteration are supported.
- `relative_date` (string)
- `scope` (string): Default Sofia-only scope, or all cities.
- `time_from` (string): Local Europe/Sofia lower boundary for the first requested date.
- `time_to` (string): Local Europe/Sofia upper boundary for the last requested date.
- `title` (string)
- `venue` (string)

Output parameters:

- `applied_filters` (object)
- `events` (array)
- `has_more` (boolean)
- `page_token`
- `timezone` (string)

### `get_event` (~58 tokens)

Get a SofiaStage event

Get one event by canonical show_stable_id or legacy source ID, optionally including related performers and editorial entries.

Input parameters:

- `event_id` (string, required): Canonical show_stable_id (preferred) or legacy source ID.
- `include` (array)

Output parameters:

- `event` (object)

### `search_catalog` (~70 tokens)

Search the SofiaStage catalog

Search cities, venues, production titles, performers, or editorial collections. Performer and editorial results are compact; use their detail tools next.

Input parameters:

- `city` (string)
- `kind` (string, required)
- `limit` (integer)
- `query` (string)
- `scope` (string)

Output parameters:

- `items` (array)
- `kind` (string)
- `truncated` (boolean)

### `get_performer` (~53 tokens)

Get a performer profile

Get a SofiaStage performer or creative-team profile, biography metadata, public links, and precomputed upcoming events by exact name or route slug.

Input parameters:

- `name_or_slug` (string, required): Exact public name/title or route slug.

Output parameters:

- `performer` (object)

### `get_editorial` (~47 tokens)

Get an editorial profile

Get a SofiaStage editorial collection, article metadata, and precomputed upcoming events by exact title or route slug.

Input parameters:

- `name_or_slug` (string, required): Exact public name/title or route slug.

Output parameters:

- `editorial` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-sofiastage-events/api#diagnostics

## Score history

- 2026-09-22: 83
- 2026-09-21: 82
- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 73
- 2026-09-01: 73
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 70
- 2026-08-26: 70
- 2026-08-25: 68
- 2026-08-24: 67

## Common questions

### What is the SofiaStage Events MCP server?

SofiaStage Events is an MCP server listed in the public MCP registry as com.sofiastage/events. Read-only tools for current SofiaStage events, venues, cities, performers, and editorial. This page covers its hosted endpoint (https://api.sofiastage.com/mcp).

### Is the SofiaStage Events MCP server safe to use?

SofiaStage Events scores 83 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 SofiaStage Events MCP server expose?

SofiaStage Events exposes 5 tools: search_events, get_event, search_catalog, get_performer, get_editorial. Their descriptions and schemas cost roughly 446 tokens of context every time the server is loaded.

### Does the SofiaStage Events MCP server require authentication?

No. We connected to SofiaStage Events without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SofiaStage Events MCP server still maintained?

SofiaStage Events is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.sofiastage.com/mcp
- Repository: https://github.com/lordcris/api.sofiastage.com
- Website: https://sofiastage.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-sofiastage-events/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-sofiastage-events/api.json
- HTML version of this page: https://verifymcp.io/servers/com-sofiastage-events/api