com.mukoko/nhimbe-events
REMOTE · EVENTS.MUKOKO.COM
Discover and manage community events across Africa on Nhimbe (Mukoko Events).
Available components
Last scanned (14 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
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.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://events.mukoko.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=events.mukoko.com | CN=WE1,O=Google Trust Services,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | a86bef8b8e37bffe0e89acb8f8b83a7f |
| SANs: events.mukoko.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 events.mukoko.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| mukoko.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://events.mukoko.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://events.mukoko.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" | Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
| www-authenticate | Bearer realm="OAuth", resource_metadata="https://events.mukoko.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" |
Protected resource metadata
| Document | https://events.mukoko.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://events.mukoko.com/mcp |
| Authorisation server | https://events.mukoko.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://events.mukoko.com/mcp | Auth required | 401 | |
| http (plaintext) | http://events.mukoko.com/mcp | HTTPS enforced | 301 | https://events.mukoko.com/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 →
create_event Create an event ~242
Create a new Mukoko event as the signed-in host. Requires the caller to be authenticated with WorkOS. Returns the created event card.
| Name | Type | Req | Description |
|---|---|---|---|
| addressCountry | string | – | – |
| addressLocality | string | – | City. |
| category | string | – | Primary category, e.g. "Music". |
| description | string | – | Event description. |
| endDate | string | – | ISO-8601 end instant (optional; defaults to start + 1h). |
| isFree | boolean | – | True if the event is free (default true). |
| isOnline | boolean | – | True for an online event. |
| maximumAttendeeCapacity | integer | – | – |
| meetingUrl | string | – | Join URL (online events). |
| name | string | yes | Event title. |
| startDate | string | yes | ISO-8601 start instant, e.g. 2026-08-01T18:00:00Z. |
| streetAddress | string | – | – |
| ticketUrl | string | – | External ticketing URL (paid events). |
| venue | string | – | Venue name (in-person events). |
| visibility | string | – | Defaults to public. |
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | – |
No examples provided.
event_analytics Event analytics ~58
Get attendance analytics for an event you host — views, RSVPs, check-ins and check-in rate. Requires WorkOS authentication and hosting the event. Returns a stats card.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | Id of the event you host. |
| Name | Type | Req | Description |
|---|---|---|---|
| analytics | object | yes | – |
No examples provided.
events_matching_interests Find events matching interests ~83
Find Mukoko Events matching one or more interests/categories (e.g. "Music", "Tech"). Optionally scope to a city. Returns a carousel.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city to scope the search to. |
| interests | array | yes | Interest or category names to match. |
| limit | integer | – | Max events to return (default 12). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| events | array | yes | – |
No examples provided.
events_near_me Find events near me ~70
Find upcoming Mukoko Events (Nhimbe) near a place. Pass a city (recommended). Returns a carousel of event cards.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City to search in, e.g. "Harare". |
| limit | integer | – | Max events to return (default 12). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| events | array | yes | – |
No examples provided.
get_event Get an event ~45
Look up a single Mukoko event by id, slug, or short code. Returns one event card.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | Event id, slug, or short code. |
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | – |
No examples provided.
list_event_registrations List event registrations ~62
List the attendees (RSVPs) for an event you host — names, contact, and check-in status. Requires WorkOS authentication and hosting the event. Returns an attendee card.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | Id of the event you host. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| registrations | array | yes | – |
No examples provided.
manage_registration Manage a registration ~97
Manage one attendee registration on an event you host: approve or reject a pending RSVP, cancel a registration, or check the attendee in at the door. Requires WorkOS authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | approve/reject a pending RSVP, cancel a registration, or check the attendee in. |
| eventId | string | yes | Id of the event you host. |
| registrationId | string | yes | Registration id (from list_event_registrations). |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| message | string | yes | – |
| registrationId | string | – | – |
| status | string | – | – |
No examples provided.
search_events Search events ~115
Search Mukoko Events by free-text query, optionally narrowed by category and/or city. Use this for open-ended discovery ("jazz nights in Harare", "startup meetups"). Returns a carousel.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter, e.g. "Music". |
| city | string | – | Optional city filter, e.g. "Harare". |
| limit | integer | – | Max events to return (default 12). |
| query | string | – | Free-text search, e.g. "open-mic poetry". |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| events | array | yes | – |
No examples provided.
send_event_blast Send an attendee blast ~111
Post an announcement to an event you host and (optionally) notify all attendees (in-app Campfire message + email). Requires WorkOS authentication. Returns a confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | Id of the event you host. |
| notifyAttendees | boolean | – | When true, fan the announcement out to attendees (Campfire + email). Default false. |
| text | string | yes | The announcement text to send. |
| updateType | string | – | Kind of update (defaults to announcement). |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| notified | boolean | yes | – |
| updateId | string | – | – |
No examples provided.
update_event Update or manage an event ~117
Update or manage an event you host — edit details or change its status (e.g. cancel). Requires WorkOS authentication. Returns the updated event card.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| endDate | string | – | ISO-8601 end instant. |
| eventId | string | yes | Id of the event to update. |
| name | string | – | – |
| startDate | string | – | ISO-8601 start instant. |
| status | string | – | New lifecycle status (e.g. "cancelled" to cancel the event). |
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | – |
No examples provided.
How do I install the com.mukoko/nhimbe-events MCP server?
com.mukoko/nhimbe-events is a hosted endpoint at https://events.mukoko.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 · events.mukoko.com
claude mcp add --transport http com-mukoko-nhimbe-events 'https://events.mukoko.com/mcp'
What is the com.mukoko/nhimbe-events MCP server?
com.mukoko/nhimbe-events is an MCP server listed in the public MCP registry as com.mukoko/nhimbe-events. Discover and manage community events across Africa on Nhimbe (Mukoko Events). This page covers its hosted endpoint (https://events.mukoko.com/mcp).
Is the com.mukoko/nhimbe-events MCP server safe to use?
com.mukoko/nhimbe-events scores 36 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 com.mukoko/nhimbe-events MCP server expose?
com.mukoko/nhimbe-events exposes 10 tools: events_near_me, events_matching_interests, get_event, search_events, create_event, and 5 more. Their descriptions and schemas cost roughly 1,000 tokens of context every time the server is loaded.
Does the com.mukoko/nhimbe-events MCP server require authentication?
Yes. com.mukoko/nhimbe-events asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.mukoko/nhimbe-events MCP server still maintained?
com.mukoko/nhimbe-events 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 com.mukoko/nhimbe-events MCP server?
VerifyMCP ran 5 checks on com.mukoko/nhimbe-events, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about com.mukoko/nhimbe-events: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.