# Presso Events (remote · events.pressonetwork.com)

Run ticketed events from your AI assistant: create events, sell tickets via Stripe, check in.

- Trust score: 37/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

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

## Channel facts

- Endpoint: `https://events.pressonetwork.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `2026.1101.5`

## 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-11-06.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**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.

## Install

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

Presso Events is a hosted endpoint at https://events.pressonetwork.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 pressonetwork-presso-events 'https://events.pressonetwork.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pressonetwork-presso-events": {
      "url": "https://events.pressonetwork.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  pressonetwork-presso-events:
    url: "https://events.pressonetwork.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "pressonetwork-presso-events": {
      "type": "http",
      "url": "https://events.pressonetwork.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-11-06 (score 37, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-01 (score 37, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-10-31 (score 32)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

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

## Score history

- 2026-11-06: 37
- 2026-11-05: 37
- 2026-11-04: 37
- 2026-11-03: 37
- 2026-11-02: 37
- 2026-11-01: 37
- 2026-10-31: 32

## Common questions

### What is the Presso Events MCP server?

Presso Events is an MCP server listed in the public MCP registry as io.github.PressoNetwork/presso-events. Run ticketed events from your AI assistant: create events, sell tickets via Stripe, check in. This page covers its hosted endpoint (https://events.pressonetwork.com/mcp).

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

Presso Events scores 37 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.

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

Yes. Presso 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 Presso Events MCP server still maintained?

Presso Events is still listed as active in the MCP registry. We last reached this channel on 6 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 Presso Events MCP server?

VerifyMCP ran 5 checks on Presso 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 Presso 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.

## Links

- Remote endpoint: https://events.pressonetwork.com/mcp
- Website: https://events.pressonetwork.com/
- Changelog RSS feed: https://verifymcp.io/servers/pressonetwork-presso-events/events.xml
- Changelog JSON feed: https://verifymcp.io/servers/pressonetwork-presso-events/events/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pressonetwork-presso-events/events.json
- HTML version of this page: https://verifymcp.io/servers/pressonetwork-presso-events/events