Presentr Practice
REMOTE · PRACTICE.PRESENTR.ME
Mock job interviews: prepare a spoken practice interview for any role, get a link. No sign-in.
Available components
Last scanned (22 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 13 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 18 Nov 26 −4
- Stability: 0.30 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “create_practice_interview” dropped its output schema ▼ functional
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 11 Nov 26 0
- Tool “create_practice_interview” rewrote its description, which is the text the model reads security
- Schema quality: 259 → 289 ▼ functional
- 9 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 71
First indexed and scored.
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://practice.presentr.me/api/mcp/practice
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=practice.presentr.me | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 10 Sept 2026 | 26 Mar 2027 | RSA 2048 | SHA256-RSA | 11fbef04923dfcf4e45bb51748ba2bc |
| SANs: practice.presentr.me | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of practice.presentr.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| me. | DS published | 45352 | 8 | Verified |
| presentr.me. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.google.com https://www.gstatic.com https://js.recurly.com/v4/recurly.js; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://practice.presentr.me/api/mcp/practice | Verified | 200 | |
| http (plaintext) | http://practice.presentr.me/api/mcp/practice | HTTPS enforced | 308 | https://practice.presentr.me/api/mcp/practice |
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_practice_interview Create a practice interview ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The job the user is interviewing for, e.g. "Dental Assistant". |
No output schema declared.
No examples provided.
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.
remote · practice.presentr.me
claude mcp add --transport http michaelw-pr-presentr-practice 'https://practice.presentr.me/api/mcp/practice'
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.