# PPT.now MCP Server (remote · ppt.now)

Convert PowerPoint files between PPT, PPTX, PPS, PPSX, POT, POTX and supported formats.

- Trust score: 37/100 (low)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `ppt.now`: 37/100 (this document), [markdown](https://verifymcp.io/servers/chrisyau83-ppt-now/ppt.md), [page](https://verifymcp.io/servers/chrisyau83-ppt-now/ppt)

## Channel facts

- Endpoint: `https://ppt.now/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## 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-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **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 not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 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 PPT.now MCP Server server?

PPT.now MCP Server is a hosted endpoint at https://ppt.now/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 chrisyau83-ppt-now 'https://ppt.now/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "chrisyau83-ppt-now": {
      "url": "https://ppt.now/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chrisyau83-ppt-now": {
      "type": "http",
      "url": "https://ppt.now/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chrisyau83-ppt-now]
url = "https://ppt.now/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chrisyau83-ppt-now": {
      "type": "remote",
      "url": "https://ppt.now/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chrisyau83-ppt-now --url 'https://ppt.now/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chrisyau83-ppt-now:
    url: "https://ppt.now/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "chrisyau83-ppt-now": {
      "Transport": "http",
      "Url": "https://ppt.now/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chrisyau83-ppt-now -t streamable-http -u 'https://ppt.now/mcp'
```

### Other

```json
{
  "mcpServers": {
    "chrisyau83-ppt-now": {
      "type": "http",
      "url": "https://ppt.now/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-04 (score 37, 0)

- [security improvement] Transport: fail → pass

### 2026-11-03 (score 37, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified

### 2026-11-02 (score 37, −29)

- [security regression] HSTS header: unverified → fail
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] MCP protocol: unverified → pass
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-01 (score 66, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 66, +44)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fair
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-30 (score 22, −5)

- [security regression] Transport: pass → fail

### 2026-10-29 (score 27, 0)

- [security regression] HSTS header: fail → unverified
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.

### 2026-10-28 (score 27, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: unverified → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified

## 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/chrisyau83-ppt-now/ppt#diagnostics

## Score history

- 2026-11-04: 37
- 2026-11-03: 37
- 2026-11-02: 37
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 22
- 2026-10-29: 27
- 2026-10-28: 27
- 2026-10-27: 27

## Common questions

### What is the PPT.now MCP Server server?

PPT.now MCP Server is listed in the public MCP registry as io.github.chrisyau83/ppt-now. Convert PowerPoint files between PPT, PPTX, PPS, PPSX, POT, POTX and supported formats. This page covers its hosted endpoint (https://ppt.now/mcp).

### Is the PPT.now MCP Server server safe to use?

PPT.now MCP Server 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 PPT.now MCP Server server require authentication?

Its publisher declares that PPT.now MCP Server requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

### Is the PPT.now MCP Server server still maintained?

PPT.now MCP Server is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 2 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ppt.now/mcp
- Authorisation metadata: https://ppt.now/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/chrisyau83/ppt-now
- Changelog RSS feed: https://verifymcp.io/servers/chrisyau83-ppt-now/ppt.xml
- Changelog JSON feed: https://verifymcp.io/servers/chrisyau83-ppt-now/ppt.json
- HTML version of this page: https://verifymcp.io/servers/chrisyau83-ppt-now/ppt