AttachPage
REMOTE · ATTACHPAGE.COM
Publish webpages and documents, send private review links, and collect comments and approvals.
Available components
Last scanned (9 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security46
- 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 (publish_document). See how to fix → View diagnostics → Fail
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1422 tokens (~129/item across 11 items; 11 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 Management80
- Stability observed for 24 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
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 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
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 Nov 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.
- 3 Nov 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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “publish_anonymous_page” rewrote its description, which is the text the model reads security
- “publish_anonymous_page” added an optional parameter “reminderEmail” cosmetic
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://attachpage.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=attachpage.com | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e73793696c29cbae0ebf995a6c346a4d |
| SANs: attachpage.com, preview.attachpage.com, *.preview.attachpage.com | ||||||
| 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 insecure
Validation of attachpage.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| attachpage.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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://attachpage.com/mcp | Verified | 200 | |
| http (plaintext) | http://attachpage.com/mcp | Served over HTTP | 200 |
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 →
get_feedback Get feedback ~79
Read recipient comments, page paths, pointed-at elements (selector and visible text), and approval or change-request decisions. The status filter selects open, resolved, or all feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | yes | Page id (siteId) returned by a publish tool or list_pages. |
| status | string | – | Which feedback to return (default all). |
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | array | – | Approvals and change requests. |
| items | array | – | Comments with page path and pointed-at element. |
No examples provided.
get_page Get page ~111
Details for one page: address, visibility, recipients and who opened it. Optional filePaths reads exact uploaded source files from that version, up to 20 files and 256 KB total, with text or base64 encoding. An empty filePaths array returns a bounded manifest without file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| filePaths | array | – | Source files to read from the current version; [] returns only the file list. |
| siteId | string | yes | Page id (siteId) returned by a publish tool or list_pages. |
| Name | Type | Req | Description |
|---|---|---|---|
| deployments | array | – | Recent versions, newest first. |
| id | string | – | Page id (siteId). |
| name | string | – | Page name. |
| shares | array | – | Sends, each with recipients and when they opened the page. |
| url | string | – | Page address. |
| visibility | string | – | private or public. |
No examples provided.
get_profile Get profile ~18
Identify the AttachPage account connected to this agent.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| id | string | yes | – |
| name | string | – | – |
No examples provided.
list_pages List pages ~18
List the user's pages with recipient and open counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| pages | array | – | The user's pages with recipient and open counts. |
No examples provided.
notify_recipients Notify recipients ~86
Email existing active recipients that a page has been updated, with an optional note. Each recipient receives a fresh personal link. Sends email immediately; sent email cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional note about what changed, up to 1,000 characters. |
| siteId | string | yes | Page id (siteId) returned by a publish tool or list_pages. |
| Name | Type | Req | Description |
|---|---|---|---|
| notified | number | – | How many people were emailed. |
No examples provided.
publish_anonymous_page Publish anonymous page ~209
Publish a public web page without an account or API key. It is deleted 48 hours after publishing unless the user opens the returned claimUrl and signs in. Returns the page URL, the claimUrl and tellUser: always relay tellUser and the claimUrl, and tell the user to keep the page before sending it to anyone. If the user gives an email address, pass it as reminderEmail: the claim link is emailed now and again before deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files of the page. The complete resulting page includes index.html at the top level. |
| reminderEmail | string | – | Optional. The user's email address, only if they give it: we email them the claim link now and before the page is deleted. |
| siteName | string | – | Name shown to the user and recipients, e.g. "Q3 report". |
| slug | string | – | Optional address label, 3-40 lowercase letters, digits or hyphens. Random when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimUrl | string | – | Show to the user: opening it while signed in keeps the page. |
| deletesAt | string | – | When the page is deleted, for people to read (UTC). |
| expiresAt | number | – | When the page is deleted (ms since epoch). |
| fileCount | number | – | Files published. |
| reminderEmailSent | boolean | – | Present when reminderEmail was given. |
| siteId | string | – | Page id. |
| tellUser | string | – | Tell the user this, with the claimUrl: when the page is deleted and how to keep it. |
| url | string | – | Public page address (works for 48 hours). |
No examples provided.
publish_document Publish document ~224
Publish a PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx/.xls), or CSV file as a browser-viewable page, private by default. Accepts filename and base64 content, up to 4 MB decoded. Documents become readable PDFs, slides have presentation controls, and spreadsheets have searchable sheet tabs. Preserves the original for download. A siteId replaces the page at the same address. Does not send invitations.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Base64 file bytes, not a local path or URL. |
| filename | string | yes | Original file name with extension, e.g. proposal.docx. |
| siteId | string | – | Replace this existing page at the same address. |
| siteName | string | – | Name shown to the user and recipients, e.g. "Q3 report". |
| slug | string | – | Optional address label, 3-40 lowercase letters, digits or hyphens. Random when omitted. |
| visibility | string | – | private (invitation-only, default) or public (anyone with the link). |
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | – | Page id. |
| url | string | – | Page address. |
No examples provided.
publish_page Publish page ~226
Publish a web page as the connected user. A siteId replaces an existing page at the same address. preserveFiles retains omitted assets and requires the baseDeploymentId of that version; stale edits are refused. Visibility is private (invitation-only, default) or public. Requires an authenticated AttachPage connection.
| Name | Type | Req | Description |
|---|---|---|---|
| baseDeploymentId | string | – | Expected current version. A changed page is refused rather than overwritten. |
| files | array | yes | Files of the page. The complete resulting page includes index.html at the top level. |
| preserveFiles | boolean | – | Retain files not included in this edit. Requires siteId and baseDeploymentId. |
| siteId | string | – | Replace this existing page at the same address. |
| siteName | string | – | Name shown to the user and recipients, e.g. "Q3 report". |
| slug | string | – | Optional address label, 3-40 lowercase letters, digits or hyphens. Random when omitted. |
| visibility | string | – | private (invitation-only, default) or public (anyone with the link). |
| Name | Type | Req | Description |
|---|---|---|---|
| deploymentId | string | – | Id of this version. |
| fileCount | number | – | Files published. |
| siteId | string | – | Page id; pass it to replace the page later. |
| slug | string | – | Address label. |
| url | string | – | Page address. |
| visibility | string | – | private or public. |
No examples provided.
resolve_feedback Resolve feedback ~62
Mark recipient feedback as resolved, or reopen it with resolved: false. The recipient sees the updated resolution status.
| Name | Type | Req | Description |
|---|---|---|---|
| feedbackId | string | yes | Feedback id from get_feedback. |
| resolved | boolean | – | true (default) marks it resolved; false reopens it. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | – | true when saved. |
No examples provided.
send_page Send page ~115
Email personal invitations for a page to the specified recipient addresses, with an optional message and access expiry. Sends email immediately; sent email cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresInDays | integer | – | Days the links work (default 7). 0 means they never expire. |
| message | string | – | Optional note included in the invitation email. |
| recipients | array | yes | Email addresses; each person gets their own personal link. |
| siteId | string | yes | Page id (siteId) returned by a publish tool or list_pages. |
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | number | – | When the links stop working (ms since epoch; year 9999 means never). |
| shareId | string | – | Id of this send. |
| siteId | string | – | Page id. |
No examples provided.
update_page Update page ~102
Rename a page, change its address label (slug), or switch private/public.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | New page name. |
| siteId | string | yes | Page id (siteId) returned by a publish tool or list_pages. |
| slug | string | – | New address label, 3-40 lowercase letters, digits or hyphens. |
| visibility | string | – | private (invitation-only, default) or public (anyone with the link). |
| Name | Type | Req | Description |
|---|---|---|---|
| deployments | array | – | Recent versions, newest first. |
| id | string | – | Page id (siteId). |
| name | string | – | Page name. |
| shares | array | – | Sends, each with recipients and when they opened the page. |
| url | string | – | Page address. |
| visibility | string | – | private or public. |
No examples provided.
How do I install the AttachPage MCP server?
AttachPage is a hosted endpoint at https://attachpage.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 · attachpage.com
claude mcp add --transport http com-attachpage-attachpage 'https://attachpage.com/mcp'
What is the AttachPage MCP server?
AttachPage is an MCP server listed in the public MCP registry as com.attachpage/attachpage. Publish webpages and documents, send private review links, and collect comments and approvals. This page covers its hosted endpoint (https://attachpage.com/mcp).
Is the AttachPage MCP server safe to use?
AttachPage scores 69 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 AttachPage MCP server expose?
AttachPage exposes 11 tools: publish_document, get_profile, publish_anonymous_page, publish_page, send_page, and 6 more. Their descriptions and schemas cost roughly 1,250 tokens of context every time the server is loaded.
Does the AttachPage MCP server require authentication?
No. We connected to AttachPage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AttachPage MCP server still maintained?
AttachPage is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.