# Presentr Practice (remote · practice.presentr.me)

Mock job interviews: prepare a spoken practice interview for any role, get a link. No sign-in.

- Trust score: 71/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `practice.presentr.me`: 71/100 (this document), [markdown](https://verifymcp.io/servers/michaelw-pr-presentr-practice/api-mcp-practice.md), [page](https://verifymcp.io/servers/michaelw-pr-presentr-practice/api-mcp-practice)

## Channel facts

- Endpoint: `https://practice.presentr.me/api/mcp/practice`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 289 tokens (~289/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 13 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Presentr Practice MCP server?

Presentr Practice is a hosted endpoint at https://practice.presentr.me/api/mcp/practice, 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 michaelw-pr-presentr-practice 'https://practice.presentr.me/api/mcp/practice'
```

### Cursor

```json
{
  "mcpServers": {
    "michaelw-pr-presentr-practice": {
      "url": "https://practice.presentr.me/api/mcp/practice"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "michaelw-pr-presentr-practice": {
      "type": "http",
      "url": "https://practice.presentr.me/api/mcp/practice"
    }
  }
}
```

### Codex

```toml
[mcp_servers.michaelw-pr-presentr-practice]
url = "https://practice.presentr.me/api/mcp/practice"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "michaelw-pr-presentr-practice": {
      "type": "remote",
      "url": "https://practice.presentr.me/api/mcp/practice",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add michaelw-pr-presentr-practice --url 'https://practice.presentr.me/api/mcp/practice' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  michaelw-pr-presentr-practice:
    url: "https://practice.presentr.me/api/mcp/practice"
```

### Netclaw

```json
{
  "McpServers": {
    "michaelw-pr-presentr-practice": {
      "Transport": "http",
      "Url": "https://practice.presentr.me/api/mcp/practice"
    }
  }
}
```

### Vellum

```bash
assistant mcp add michaelw-pr-presentr-practice -t streamable-http -u 'https://practice.presentr.me/api/mcp/practice'
```

### Other

```json
{
  "mcpServers": {
    "michaelw-pr-presentr-practice": {
      "type": "http",
      "url": "https://practice.presentr.me/api/mcp/practice"
    }
  }
}
```

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-18 (score 71, −4)

- [security regression] Stability: 0.30 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [functional regression] Tool “create_practice_interview” dropped its output schema

### 2026-11-17 (score 75, +1)

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

### 2026-11-15 (score 74, +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-13 (score 73, +1)

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

### 2026-11-11 (score 72, 0)

- [security] Tool “create_practice_interview” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 259 → 289

### 2026-11-09 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 71)

First indexed and scored.

## MCP tools (1)

### `create_practice_interview` (~216 tokens)

Create a practice interview

Prepares a spoken mock interview on Presentr Practice for a specific job and returns a link to start it. Use it when the user wants to practise or prepare for a job interview for a role or a job posting. Pass the job title; pass the company and the job posting text only if the user gave them. The interview runs on Presentr Practice in the user's browser: an AI interviewer asks the questions out loud and follows up, and the user answers by voice or by typing. Starting it needs a Presentr Practice account with a verified email (signing in with Google verifies it at once); the link opens in any browser. Give the user the link; do not run the interview in the chat.

Input parameters:

- `company` (string): The employer, only if the user named one.
- `job_posting` (string): The job posting text exactly as the user pasted it, only if they did.
- `job_title` (string, required): The job the user is interviewing for, e.g. "Dental Assistant".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/michaelw-pr-presentr-practice/api-mcp-practice#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 73
- 2026-11-13: 73
- 2026-11-12: 72
- 2026-11-11: 72
- 2026-11-10: 72
- 2026-11-09: 72
- 2026-11-08: 71

## Common questions

### What is the Presentr Practice MCP server?

Presentr Practice is an MCP server listed in the public MCP registry as io.github.michaelw-pr/presentr-practice. Mock job interviews: prepare a spoken practice interview for any role, get a link. No sign-in. This page covers its hosted endpoint (https://practice.presentr.me/api/mcp/practice).

### Is the Presentr Practice MCP server safe to use?

Presentr Practice scores 71 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 Presentr Practice MCP server expose?

Presentr Practice exposes 1 tool: create_practice_interview. Their descriptions and schemas cost roughly 216 tokens of context every time the server is loaded.

### Does the Presentr Practice MCP server require authentication?

No. We connected to Presentr Practice without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Presentr Practice MCP server still maintained?

Presentr Practice 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 Presentr Practice MCP server?

VerifyMCP ran 13 checks on Presentr Practice, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://practice.presentr.me/api/mcp/practice
- Website: https://practice.presentr.me/
- Changelog RSS feed: https://verifymcp.io/servers/michaelw-pr-presentr-practice/api-mcp-practice.xml
- Changelog JSON feed: https://verifymcp.io/servers/michaelw-pr-presentr-practice/api-mcp-practice/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/michaelw-pr-presentr-practice/api-mcp-practice.json
- HTML version of this page: https://verifymcp.io/servers/michaelw-pr-presentr-practice/api-mcp-practice
