# Meetup (npm · @pipeworx/mcp-meetup)

Meetup MCP — wraps Meetup's public GraphQL API (api.meetup.com, free, no auth)

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

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-meetup/meetup-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-meetup/meetup-mcp)
- npm · `@pipeworx/mcp-meetup`: 85/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-meetup/pipeworx-mcp-meetup.md), [page](https://verifymcp.io/servers/pipeworx-io-meetup/pipeworx-mcp-meetup)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-meetup`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-meetup).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 540 tokens (~135/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Meetup MCP server?

Meetup runs locally as an npm package, launched with npx -y @pipeworx/mcp-meetup. 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 pipeworx-io-meetup -- npx -y @pipeworx/mcp-meetup
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-meetup": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-meetup"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-meetup": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-meetup"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-meetup -- npx -y @pipeworx/mcp-meetup
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-meetup": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-meetup"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-meetup --command npx --arg -y --arg @pipeworx/mcp-meetup
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-meetup:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-meetup"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-meetup": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-meetup"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-meetup -t stdio -c npx -a -y @pipeworx/mcp-meetup
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-meetup": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-meetup"
      ]
    }
  }
}
```

## 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-05 (score 85, +1)

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

### 2026-11-03 (score 84, +3)

- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (4)

### `meetup_search_events` (~213 tokens)

Search Meetup for upcoming public events by keyword, near a city or a lat/lon point. Returns each event's title, time, URL, status and hosting group — never attendee or RSVP lists. Provide either `city` (geocoded automatically) or `lat`+`lon`.

Input parameters:

- `city` (string): City or place name to search near, e.g. "San Francisco, CA". Geocoded automatically. Omit if you pass lat/lon directly.
- `lat` (number): Latitude of the search center, in decimal degrees. Use instead of `city`.
- `limit` (number): Maximum number of events to return (1-50). Defaults to 10.
- `lon` (number): Longitude of the search center, in decimal degrees. Use instead of `city`.
- `query` (string, required): Keyword to search for, e.g. "music" or "python".
- `radius` (number): Search radius in miles around the center point. Defaults to 25.

### `meetup_event` (~78 tokens)

Get full details for one Meetup event by its numeric ID (the trailing number in a meetup.com event URL, e.g. "316887506"). Returns title, description, time, venue and hosting group — never attendee or RSVP lists.

Input parameters:

- `event_id` (string, required): The event's numeric Meetup ID, e.g. "316887506".

### `meetup_group` (~80 tokens)

Get details for one Meetup group by its urlname (the slug in meetup.com/<urlname>, e.g. "sfpython"). Returns name, description, location, topic category and founding date — never a member list.

Input parameters:

- `urlname` (string, required): The group's urlname, e.g. "sfpython" (from meetup.com/sfpython).

### `meetup_group_events` (~117 tokens)

List a Meetup group's events by the group's urlname. Returns upcoming events by default, or past events with `include_past`. Never returns RSVP or attendee lists.

Input parameters:

- `include_past` (boolean): When true, list the group's past events instead of its upcoming ones. Defaults to false.
- `limit` (number): Maximum number of events to return (1-50). Defaults to 10.
- `urlname` (string, required): The group's urlname, e.g. "sfpython" (from meetup.com/sfpython).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-meetup/pipeworx-mcp-meetup#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Meetup MCP server?

Meetup is an MCP server listed in the public MCP registry as io.github.pipeworx-io/meetup. Meetup MCP, wraps Meetup's public GraphQL API (api.meetup.com, free, no auth). This page covers its npm package (@pipeworx/mcp-meetup).

### Is the Meetup MCP server safe to use?

Meetup scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Meetup MCP server expose?

Meetup exposes 4 tools: meetup_search_events, meetup_event, meetup_group, meetup_group_events. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.

### Is the Meetup MCP server still maintained?

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

### What licence is the Meetup MCP server under?

Meetup declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Meetup MCP server?

VerifyMCP ran 16 checks on Meetup, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-meetup
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-meetup
- Repository: https://github.com/pipeworx-io/mcp-meetup
- Website: https://pipeworx.io/packs/meetup
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-meetup/pipeworx-mcp-meetup.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-meetup/pipeworx-mcp-meetup/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-meetup/pipeworx-mcp-meetup.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-meetup/pipeworx-mcp-meetup