page.notepad/notepad
REMOTE · MCP.NOTEPAD.PAGE · SCANNED SEP 20
Private living HTML pages agents publish, recall, update, and share at name.notepad.page.
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 Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 93 tokens (~93/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the page.notepad/notepad MCP server?
page.notepad/notepad is a hosted endpoint at https://mcp.notepad.page/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 · mcp.notepad.page
claude mcp add --transport http page-notepad-notepad 'https://mcp.notepad.page/mcp'
{
"mcpServers": {
"page-notepad-notepad": {
"url": "https://mcp.notepad.page/mcp"
}
}
} {
"servers": {
"page-notepad-notepad": {
"type": "http",
"url": "https://mcp.notepad.page/mcp"
}
}
} [mcp_servers.page-notepad-notepad] url = "https://mcp.notepad.page/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"page-notepad-notepad": {
"type": "remote",
"url": "https://mcp.notepad.page/mcp",
"enabled": true
}
}
} openclaw mcp add page-notepad-notepad --url 'https://mcp.notepad.page/mcp' --transport streamable-http
mcp_servers:
page-notepad-notepad:
url: "https://mcp.notepad.page/mcp" {
"McpServers": {
"page-notepad-notepad": {
"Transport": "http",
"Url": "https://mcp.notepad.page/mcp"
}
}
} assistant mcp add page-notepad-notepad -t streamable-http -u 'https://mcp.notepad.page/mcp'
{
"mcpServers": {
"page-notepad-notepad": {
"type": "http",
"url": "https://mcp.notepad.page/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.
- 20 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 20 Sept 2026 · Probed https://mcp.notepad.page/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=notepad.page | CN=WE1,O=Google Trust Services,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5caeca5e423888a113dee0e4addf983a |
| SANs: notepad.page, *.notepad.page | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.notepad.page. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| page. | present | 64712 | 8 | Verified |
| notepad.page. | present | 2371 | 13 | Verified |
| mcp.notepad.page. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mcp.notepad.page/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://mcp.notepad.page/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"| Header | Value |
|---|---|
| strict-transport-security | max-age=86400 |
Protected resource metadata
| Document | https://mcp.notepad.page/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.notepad.page/mcp |
| Authorisation server | https://mcp.notepad.page |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.notepad.page/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.notepad.page/mcp | HTTPS enforced | 301 | https://mcp.notepad.page/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 →
ask_notepad Ask notepad.page ~60
Returns relevant public notepad.page documentation excerpts for a product question. Uses deterministic retrieval and does not call an LLM or read account data.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Question about notepad.page, onboarding, tools, sharing, limits, or access. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the page.notepad/notepad MCP server?
page.notepad/notepad is an MCP server listed in the public MCP registry as page.notepad/notepad. Private living HTML pages agents publish, recall, update, and share at name.notepad.page. This page covers its hosted endpoint (https://mcp.notepad.page/mcp).
Is the page.notepad/notepad MCP server safe to use?
page.notepad/notepad scores 91 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 page.notepad/notepad MCP server expose?
page.notepad/notepad exposes 1 tool: ask_notepad. Their descriptions and schemas cost roughly 60 tokens of context every time the server is loaded.
Does the page.notepad/notepad MCP server require authentication?
Yes. page.notepad/notepad 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 page.notepad/notepad MCP server still maintained?
page.notepad/notepad is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.