MCP servers › events.thisweekend › this-weekend
MCP server · registry snapshot 2026-10-30 · last tested 2026-10-30
this-weekend MCP server
Registry name events.thisweekend/this-weekend
by thisweekend.events · domain (the registry's namespace rule)Website ↗
Festivals, shows and exhibitions across South Korea, searchable by date and area. No auth. — the publisher's description
Summary
events.thisweekend/this-weekend is a remote MCP server listed in the official MCP registry at version 1.8.0, under the namespace of the domain thisweekend.events. On 2026-10-30 ProtocolProbe connected to it in read-only mode and read its inventory: 7 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 7
- Last tested
- 2026-10-30
Tool list size
6,228 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (7 tools). Counted with Anthropic's token counter on 2026-10-30, from the tool list we read on 2026-10-30. Median across 25,738 counted servers: 2,858 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-10-30 (thisweekend.events), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.8.0).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-30
- Mode
- read-only (no tool calls)
- Latest version
- 1.8.0, published 2026-10-29 (registry, as of the 2026-10-30 snapshot)
- First listed version
- 2026-10-29 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-30
- Package and repository
- checked 2026-10-30
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-10-29, listed on 2026-10-30 with version 1.8.0 (published 2026-10-29).
Source: the official MCP Registry list on 2026-10-29 and on 2026-10-30.
What it is
What does this server offer?
Observed inventoryNone of its 7 tools are described as changing anything. For 7 the reading was uncertain, so no mark is shown.
- search_eventson 84 other servers
“날짜, 지역, 검색어로 공개 행사를 찾습니다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
startDatestring“시작 날짜(YYYY-MM-DD).”endDatestring“끝 날짜(YYYY-MM-DD).”areastring“지역 이름.”querystring“행사 이름, 장소, 분야, 주최에서 찾을 낱말.”freeboolean“true면 무료 행사만, false면 유료 행사만 찾습니다.”tagsarray“이 태그가 모두 붙은 행사만 찾습니다.”limitinteger“한 번에 받을 최대 개수.”offsetinteger“앞에서 건너뛸 개수.”
- ask_events
“한 문장으로 물으면(예: 이번 주말 부산 불꽃축제, 来週の土曜日 ソウル 展示, free concerts in Seoul on 2026-11-07) 그 말에서 날짜, 지역, 찾는 낱말을 읽어 행사를 찾습니다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
questionstringrequired“묻고 싶은 말 한 문장(200자 이하).”limitinteger“한 번에 받을 최대 개수.”previousarray“같은 대화에서 앞서 물은 질문들.”
- get_eventon 99 other servers
“행사 id로 일정, 장소, 요금, 예약 안내, 출처 링크를 가져옵니다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
idstringrequired“search_events 결과에 있는 행사 id.”
- get_event_coverage
“지금 담긴 행사 자료의 날짜 범위와 마지막 수집 시각을 알려 줍니다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- submit_eventon 3 other servers
“지도에 없는 행사를 운영자 검토 대기열에 올립니다.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
21 inputs, 13 required
titlestringrequired“행사 이름.”kindstringrequired“행사 종류.”kindOtherstring“kind가 기타일 때 적는 종류 이름(두 글자 이상).”topicstringrequired“분야나 주제(예: 사진, 재즈).”startDatestringrequired“시작 날짜(YYYY-MM-DD, 한국 시간).”endDatestringrequired“끝 날짜(YYYY-MM-DD).”startTimestring“시작 시간(HH:MM, 24시간제).”endTimestring“끝 시간(HH:MM, 24시간제).”locationModestring“offline은 현장 행사, hybrid는 현장과 온라인을 함께 하는 행사입니다.”citystringrequired“행사가 열리는 시·도 id(seoul, busan 등).”districtstringrequired“시·군·구 이름(종로구, 해운대구, 수원시).”placestringrequired“장소 이름(두 글자 이상).”addressstringrequired“장소의 도로명 주소.”latitudenumberrequired“장소의 위도(WGS84, 예: 37.5796).”longitudenumberrequired“장소의 경도(WGS84, 예: 126.9770).”urlstringrequired“운영자가 행사를 확인할 수 있는 http 또는 https 주소.”feestring“free는 무료, paid는 유료, unknown은 모름입니다.”bookingstring“none은 예약 없이 입장, optional은 예약을 받지만 필수는 아님, required는 예약 필수, unknown은 모름입니다.”descriptionstringrequired“행사 설명 10자 이상.”reportIdstring“이미 보낸 제보를 고칠 때 넣는 reportId.”editKeystring“제보를 처음 보냈을 때 받은 editKey.”
- report_event_change
“지도에 있는 행사의 일정, 장소, 요금, 예약 방식이 바뀌었거나 행사가 취소됐다고 알립니다.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
18 inputs, 4 required
eventIdstringrequired“바뀐 행사의 id.”typestringrequired“change는 일정, 장소, 요금, 예약 방식이 바뀐 경우이고 cancel은 행사가 취소된 경우입니다.”descriptionstringrequired“무엇이 어떻게 바뀌었는지 10자 이상.”urlstringrequired“바뀐 내용을 확인할 수 있는 http 또는 https 주소.”startDatestring“새 시작 날짜(YYYY-MM-DD).”endDatestring“새 끝 날짜(YYYY-MM-DD).”startTimestring“새 시작 시간(HH:MM, 24시간제).”endTimestring“새 끝 시간(HH:MM, 24시간제).”placestring“새 장소 이름.”citystring“새 장소의 시·도 id.”districtstring“새 장소의 시·군·구 이름.”addressstring“새 장소의 도로명 주소.”latitudenumber“새 장소의 위도(WGS84).”longitudenumber“새 장소의 경도(WGS84).”feestring“요금이 바뀌었을 때 지금 요금.”bookingstring“예약 방식이 바뀌었을 때 지금 방식.”reportIdstring“이미 보낸 제보를 고칠 때 넣는 reportId.”editKeystring“제보를 처음 보냈을 때 받은 editKey.”
- get_report_statuson 4 other servers
“보낸 제보가 검토 중인지, 반영됐는지, 반려됐는지 알려 줍니다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
reportIdstringrequired“확인할 제보의 reportId.”editKeystringrequired“제보할 때 받은 editKey.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-30.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 53
- Tools with a description
- 100% of 7
- Typical description length
- 147 characters
The tool set
Counted from the listing
- Tools
- 7
- Size of the list
- about 6,354 tokens for an agent to load (characters ÷ 4)
- Naming
- 7 of 7 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 7 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-30 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://thisweekend.events/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"this-weekend": {
"url": "https://thisweekend.events/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"this-weekend": {
"type": "http",
"url": "https://thisweekend.events/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"this-weekend","type":"http","url":"https://thisweekend.events/mcp"}'Claude Code
claude mcp add --transport http this-weekend https://thisweekend.events/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"this-weekend": {
"type": "streamableHttp",
"url": "https://thisweekend.events/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"this-weekend": {
"httpUrl": "https://thisweekend.events/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.this-weekend] url = "https://thisweekend.events/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"this-weekend": {
"url": "https://thisweekend.events/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://thisweekend.events/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint thisweekend.events/mcp | Session opened | matches | our test · 2026-10-30 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-30 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-30. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about events.thisweekend/this-weekend
Answered from the data aboveWho publishes events.thisweekend/this-weekend?
The registry ties the namespace events.thisweekend to the domain thisweekend.events; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does events.thisweekend/this-weekend need an API key or sign-in?
It opened a session without any credential on 2026-10-30. The registry entry declares no required credential; no declaration is not a guarantee.
Has events.thisweekend/this-weekend been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-30, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 678 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 7 tools, 0 resources, 0 prompts.
- 2,481 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “events.thisweekend/this-weekend: MCP server record.” Data checked 2026-10-30. https://protocolprobe.com/mcp/servers/events.thisweekend/this-weekend
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/events.thisweekend/this-weekend)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology