SofiaStage Events
REMOTE · API.SOFIASTAGE.COM · SCANNED SEP 21
Read-only tools for current SofiaStage events, venues, cities, performers, and editorial.
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 Security69
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 535 tokens (~76/item across 7 items; 5 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
- 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 current MCP spec version (2026-07-28).Pass
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.
remote · api.sofiastage.com
claude mcp add --transport http com-sofiastage-events 'https://api.sofiastage.com/mcp'
{
"mcpServers": {
"com-sofiastage-events": {
"url": "https://api.sofiastage.com/mcp"
}
}
} {
"servers": {
"com-sofiastage-events": {
"type": "http",
"url": "https://api.sofiastage.com/mcp"
}
}
} [mcp_servers.com-sofiastage-events] url = "https://api.sofiastage.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-sofiastage-events": {
"type": "remote",
"url": "https://api.sofiastage.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-sofiastage-events --url 'https://api.sofiastage.com/mcp' --transport streamable-http
mcp_servers:
com-sofiastage-events:
url: "https://api.sofiastage.com/mcp" {
"McpServers": {
"com-sofiastage-events": {
"Transport": "http",
"Url": "https://api.sofiastage.com/mcp"
}
}
} assistant mcp add com-sofiastage-events -t streamable-http -u 'https://api.sofiastage.com/mcp'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 7 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.
- 5 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.
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://api.sofiastage.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sofiastage.com | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ed8f5afcaf8a5b070ec4a9e948c51a58 |
| SANs: sofiastage.com, *.sofiastage.com | ||||||
| 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 api.sofiastage.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sofiastage.com. | 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 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sofiastage.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.sofiastage.com/mcp | Inconclusive | 405 |
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 →
get_editorial Get an editorial profile ~47
Get a SofiaStage editorial collection, article metadata, and precomputed upcoming events by exact title or route slug.
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_slug | string | yes | Exact public name/title or route slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| editorial | object | yes | – |
No examples provided.
get_event Get a SofiaStage event ~58
Get one event by canonical show_stable_id or legacy source ID, optionally including related performers and editorial entries.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Canonical show_stable_id (preferred) or legacy source ID. |
| include | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | – |
No examples provided.
get_performer Get a performer profile ~53
Get a SofiaStage performer or creative-team profile, biography metadata, public links, and precomputed upcoming events by exact name or route slug.
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_slug | string | yes | Exact public name/title or route slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| performer | object | yes | – |
No examples provided.
search_catalog Search the SofiaStage catalog ~70
Search cities, venues, production titles, performers, or editorial collections. Performer and editorial results are compact; use their detail tools next.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| kind | string | yes | – |
| limit | integer | – | – |
| query | string | – | – |
| scope | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| kind | string | yes | – |
| truncated | boolean | yes | – |
No examples provided.
search_events Search SofiaStage events ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| applied_filters | object | yes | – |
| events | array | yes | – |
| has_more | boolean | yes | – |
| page_token | – | yes | – |
| timezone | string | yes | – |
No examples provided.
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 82 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.