dev.promplate/hmr
REMOTE · PYTH-ON-LINE.PROMPLATE.DEV · SCANNED SEP 22
Docs for hot-module-reload and reactive programming for Python (`hmr` on PyPI)
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 411 tokens (~68/item across 6 items; 3 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the dev.promplate/hmr MCP server?
dev.promplate/hmr is a hosted endpoint at https://pyth-on-line.promplate.dev/hmr/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.
remote · pyth-on-line.promplate.dev
claude mcp add --transport http dev-promplate-hmr 'https://pyth-on-line.promplate.dev/hmr/mcp'
{
"mcpServers": {
"dev-promplate-hmr": {
"url": "https://pyth-on-line.promplate.dev/hmr/mcp"
}
}
} {
"servers": {
"dev-promplate-hmr": {
"type": "http",
"url": "https://pyth-on-line.promplate.dev/hmr/mcp"
}
}
} [mcp_servers.dev-promplate-hmr] url = "https://pyth-on-line.promplate.dev/hmr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-promplate-hmr": {
"type": "remote",
"url": "https://pyth-on-line.promplate.dev/hmr/mcp",
"enabled": true
}
}
} openclaw mcp add dev-promplate-hmr --url 'https://pyth-on-line.promplate.dev/hmr/mcp' --transport streamable-http
mcp_servers:
dev-promplate-hmr:
url: "https://pyth-on-line.promplate.dev/hmr/mcp" {
"McpServers": {
"dev-promplate-hmr": {
"Transport": "http",
"Url": "https://pyth-on-line.promplate.dev/hmr/mcp"
}
}
} assistant mcp add dev-promplate-hmr -t streamable-http -u 'https://pyth-on-line.promplate.dev/hmr/mcp'
{
"mcpServers": {
"dev-promplate-hmr": {
"type": "http",
"url": "https://pyth-on-line.promplate.dev/hmr/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Sept 26 0
- DNSSEC: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 0
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 22 Sept 2026 · Probed https://pyth-on-line.promplate.dev/hmr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pyth-on-line.promplate.dev | CN=YR2,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 5c477484a13b12482724ae7b90714d9c150 |
| SANs: pyth-on-line.promplate.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pyth-on-line.promplate.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| promplate.dev. | absent | 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 |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pyth-on-line.promplate.dev/hmr/mcp | Verified | 200 | |
| http (plaintext) | http://pyth-on-line.promplate.dev/hmr/mcp | HTTPS enforced | 308 | https://pyth-on-line.promplate.dev/hmr/mcp |
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 →
learn-hmr-basics ~73
A brief and concise explanation of the `hmr` library. This tool provides information on how to use reactive programming or use hot module reloading in Python. As long as the user mentions HMR / Reactive Programming, this tool must be called first! Don't manually view the resource, call this tool instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
view-hmr-core-sources ~149
The full source code (core only) of the HMR library. Always call `learn-hmr-concepts` to learn the core concepts before calling this tool. These files are the full source code of the HMR library, which would be very helpful because good code are self-documented. For a brief and concise explanation, please refer to the `hmr-docs://about` MCP resource. Make sure you've read it before calling this tool. To learn how to use HMR for reactive programming, read the unit tests later. The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
view-hmr-unit-tests ~132
The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the dev.promplate/hmr MCP server?
dev.promplate/hmr is an MCP server listed in the public MCP registry as dev.promplate/hmr. Docs for hot-module-reload and reactive programming for Python (`hmr` on PyPI). This page covers its hosted endpoint (https://pyth-on-line.promplate.dev/hmr/mcp).
Is the dev.promplate/hmr MCP server safe to use?
dev.promplate/hmr scores 81 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 dev.promplate/hmr MCP server expose?
dev.promplate/hmr exposes 3 tools: learn-hmr-basics, view-hmr-core-sources, view-hmr-unit-tests. Their descriptions and schemas cost roughly 354 tokens of context every time the server is loaded.
Does the dev.promplate/hmr MCP server require authentication?
No. We connected to dev.promplate/hmr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.promplate/hmr MCP server still maintained?
dev.promplate/hmr is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.