MCP server for Atlassian Confluence Data Center - access and manage content
MintPage is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Publish Markdown or HTML as a live, shareable web page in one tool call. Guest mode needs no key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mintpage-mcp https://mintpage.ai/mcp
# 2 — ask your agent for something these tools do
# publish_page, update_page, mint_page and 6 more
MintPage costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mintpage-mcp https://mintpage.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take Authorization header (Optional. 'Bearer mp_…' with a free API key from https://mintpage.ai/start for 7-day pages and stats. Omit for guest mode (24-hour pages).) if you want to set it.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Publish a new web page and get its public URL. Content is Markdown (GFM: tables, task lists, code fences) or HTML (sanitized: no scripts, forms or iframes; inline styles and <style> allowed). Returns the URL to show the user. Pages are public to anyone with the link. Publish only content the user asked for; to test the connection, call get_account instead of publishing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Page title (also the browser tab title). |
| content | string | yes | The page body in Markdown or HTML. |
| format | string | no | How to interpret content. |
| theme | string | no | Visual theme: paper (light), ink (dark), terminal (dark monospace). |
| byline | string | no | Shown above the page, e.g. 'Prepared by Claude for Alex'. |
| slug | string | no | Custom URL slug (Pro only). Lowercase letters, digits, hyphens. |
| expires_in_hours | no | Hours until the page expires. Omit for the plan default (guest 24h, free 7 days, Pro never). Pro can pass null for never. |
Replace the title, content, theme, byline, slug or expiry of a page you own. Omitted fields are kept. A new slug (Pro, or a minted page) changes the URL: the old link then shows 'revoked' and can't be reused. Minted pages stay permanent (expires_in_hours is ignored). Requires an API key (guest pages can't be edited).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The page_id returned by publish_page or list_pages. |
| title | string | no | — |
| content | string | no | — |
| format | string | no | — |
| theme | string | no | — |
| byline | string | no | — |
| slug | string | no | New custom URL slug (Pro or minted pages). Lowercase letters, digits, hyphens. |
| expires_in_hours | no | — |
Make one page permanent with one mint: it never expires, loses the MintPage badge, gets Pro limits (2 MB, custom slug via update_page, indexable) and stops counting toward the live-page limit. Costs 1 mint from the account's balance, once per page; no charge if the page is already minted or the account is on Pro (already permanent). Mints come in a Peppermint pack (10 for $5, one-time, never expir
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | The page_id returned by publish_page or list_pages. |
List the pages in this account (newest first) with URLs, view counts and expiry. Requires an API key.
No parameter schema on file.
Permanently take a page offline. The URL will show 'This page was removed'. Irreversible — confirm with the user first. Requires an API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | — |
Temporarily hide a page (paused: true) or bring it back (paused: false). While paused, the URL shows 'This page is paused' to everyone except the signed-in owner; nothing is deleted and the URL doesn't change. Requires an API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | — |
| paused | boolean | no | — |
Turn off a page's current link and give it a new random one, e.g. when the link reached the wrong people. The old URL shows 'This link was revoked' forever; content, stats and page_id are kept. Share the new url only with the right people. Requires an API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | — |
View count, last viewed time and a 30-day daily breakdown for a page you own. Requires an API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_id | string | yes | — |
Show the current plan, usage against limits, and where to upgrade or get a key. Works for guests too.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MintPage or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| publish_page | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| update_page | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| mint_page | state-write | state-write: declares readOnlyHint: false |
| list_pages | no tags | |
| delete_page | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| pause_page | state-write | state-write: declares readOnlyHint: false |
| revoke_link | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_page_stats | untrusted-input | untrusted-input: keyword "get_page" |
| get_account | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish MintPage can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.