com.sendpageapp/sendpage
REMOTE · SENDPAGEAPP.COM · SCANNED SEP 22
Publish an HTML document as a link anyone can open in one tap, plus PDF, image and Word export.
Available components
Recent critical change
Authorization (9 Aug 2026). See the changelog before you install this server.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_document). See how to fix → View diagnostics → Fail
- 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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 885 tokens (~110/item across 8 items; 7 tools + 1 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
- 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 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
- Supports UI / widget rendering.Pass
How do I install the com.sendpageapp/sendpage MCP server?
com.sendpageapp/sendpage is a hosted endpoint at https://sendpageapp.com/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 · sendpageapp.com
claude mcp add --transport http com-sendpageapp-sendpage 'https://sendpageapp.com/mcp'
{
"mcpServers": {
"com-sendpageapp-sendpage": {
"url": "https://sendpageapp.com/mcp"
}
}
} {
"servers": {
"com-sendpageapp-sendpage": {
"type": "http",
"url": "https://sendpageapp.com/mcp"
}
}
} [mcp_servers.com-sendpageapp-sendpage] url = "https://sendpageapp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-sendpageapp-sendpage": {
"type": "remote",
"url": "https://sendpageapp.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-sendpageapp-sendpage --url 'https://sendpageapp.com/mcp' --transport streamable-http
mcp_servers:
com-sendpageapp-sendpage:
url: "https://sendpageapp.com/mcp" {
"McpServers": {
"com-sendpageapp-sendpage": {
"Transport": "http",
"Url": "https://sendpageapp.com/mcp"
}
}
} assistant mcp add com-sendpageapp-sendpage -t streamable-http -u 'https://sendpageapp.com/mcp'
{
"mcpServers": {
"com-sendpageapp-sendpage": {
"type": "http",
"url": "https://sendpageapp.com/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.
- 5 Sept 26 0
- Stability: 0.97 → pass security
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- 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
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 0
- Schema quality: 752 → 885 ▼ functional
- New tool “export_document” 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://sendpageapp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.sendpageapp.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 31 Jul 2026 | 13 Feb 2027 | RSA 2048 | SHA256-RSA | 6033ea3feb34b33a2c14bc06a09a4b8 |
| SANs: *.sendpageapp.com, sendpageapp.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| 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 sendpageapp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sendpageapp.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sendpageapp.com/mcp | Verified | 200 | |
| http (plaintext) | http://sendpageapp.com/mcp | HTTPS enforced | 301 | https://sendpageapp.com/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 →
check_document Check a document before sending ~158
Check an HTML document for the problems a recipient will notice and you cannot: links that lead nowhere, images that will not load, placeholder text left in, http:// references the viewer blocks. Call this BEFORE handing someone a share link — a hallucinated URL or a dead CDN image is invisible while writing and obvious when reading. Pass `html` to check a draft, or `shortId` to re-check something already published after fixing it.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | – | The edit token, if this key did not publish the document. |
| html | string | – | A draft to check before publishing. Use this or `shortId`. |
| shortId | string | – | An already-published document to check. Use this or `html`. |
No output schema declared.
No examples provided.
export_document Export a document as an image, PDF or Word file ~133
Get a downloadable PNG image, PDF, or Word (.docx) file of a document already published to SendPage. Use this when the user wants a file copy — to attach, print, or hand over — not just the link. Returns a URL to fetch the file. PNG and PDF are free (free-tier documents carry a small watermark); Word export requires Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | The file format: "png" (image), "pdf", or "docx" (Word, Pro only). |
| shortId | string | yes | The document's id, the last part of its share link. |
No output schema declared.
No examples provided.
get_document Read a published document back ~94
Fetch the current HTML of a document you published, so it can be edited rather than rewritten. Call this before update_document: acting on feedback usually means one small change, and regenerating the whole file loses everything else about it.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | – | The edit token, if this key did not publish the document. |
| shortId | string | yes | The document's id, the last part of its share link. |
No output schema declared.
No examples provided.
list_comments Read feedback on a document ~101
Read the feedback people have left on a document you published. Call this when the user asks whether anyone has responded or replied, and always before revising a document — the comments say what to change. Returns each comment with who left it and when, oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | – | The edit token, if this key did not publish the document. |
| shortId | string | yes | The document's id, the last part of its share link. |
No output schema declared.
No examples provided.
list_documents List published documents ~48
List the documents published with this API key, newest first, with their share links and view counts. Use it to find a document the user published earlier so it can be updated or re-sent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_document Publish an HTML document ~177
Publish an HTML document to SendPage and get a shareable link the recipient can open in one tap on any device. Use this whenever the user has an HTML document and wants to send, share, or deliver it to someone — it is the delivery step after the document is written. The link renders the page as designed, previews with a title and preview card in WhatsApp/Telegram/Slack/email, and can be exported to PDF, image or Word. Returns the share link plus an edit token for later updates.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The complete HTML document, from <!DOCTYPE html> onwards. |
| senderName | string | – | Who the document is from, shown to the recipient. Optional. |
| title | string | – | Title shown in the link preview and document header. Taken from the HTML's <title> if omitted. |
No output schema declared.
No examples provided.
update_document Update a published document ~114
Replace the contents or title of a document already published to SendPage. The share link stays exactly the same, so use this to fix a typo or update figures instead of publishing again — anyone who already has the link sees the correction.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | – | The edit token returned when the document was published. |
| html | string | – | Replacement HTML. Optional. |
| shortId | string | yes | The document's id, the last part of its share link. |
| title | string | – | Replacement title. Optional. |
No output schema declared.
No examples provided.
What is the com.sendpageapp/sendpage MCP server?
com.sendpageapp/sendpage is an MCP server listed in the public MCP registry as com.sendpageapp/sendpage. Publish an HTML document as a link anyone can open in one tap, plus PDF, image and Word export. This page covers its hosted endpoint (https://sendpageapp.com/mcp).
Is the com.sendpageapp/sendpage MCP server safe to use?
com.sendpageapp/sendpage scores 80 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 com.sendpageapp/sendpage MCP server expose?
com.sendpageapp/sendpage exposes 7 tools: publish_document, update_document, list_comments, get_document, list_documents, and 2 more. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.
Does the com.sendpageapp/sendpage MCP server require authentication?
No. We connected to com.sendpageapp/sendpage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.sendpageapp/sendpage MCP server still maintained?
com.sendpageapp/sendpage 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.