Documarium MCP server
com.documarium/documariumdocumarium.comstreamable-httpv1.0.3Scanned
Your docs site. No editor to open. Just ask Claude.
12 tools: 6 can delete or cancel things, 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Documarium MCP server can do
The Documarium MCP server is published by documarium.com, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (6 tools: propose_edit, apply_edit, publish, rollback and 2 more) and create or change data (1 tool: create_preview). 5 tools only read.
1 tool can send data out of your system (publish).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 1.0.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 6Claude Code: deny
apply_editKeeps changes.No findings
Why it is in this group
- The name "apply_edit" says "apply": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Keeps changes. On a kept site it takes the proposal_id that propose_edit returned, or that site_status lists, and saves that staged set as the site's next numbered version, all at once or not at all. It does not publish: readers see the change after publish. A staged set is not kept if someone else changed the same pages in the meantime or if it is more than a day old, and the answer says which. A member whose role does not allow keeping leaves the change waiting for an editor. On a preview, given its draft_id, there is no staged set: it takes the operations themselves and saves them into the preview at once, and the preview's link shows them. rollback undoes a kept version.
Annotations the server declares
- title: Keep a change
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
claim_draftKeeps a preview nobody has kept yet as a site in the signed-in person's own account, at the web address named by subdomain.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Keeps a preview nobody has kept yet as a site in the signed-in person's own account, at the web address named by subdomain. Its pages come over as they are and nothing is published: the site gets a private link, and readers see it only after publish. Keeping needs no paid plan. Without a subdomain, or with one that is taken, the answer offers names that are free and nothing is kept. It is the tool for keeping a preview without publishing it; publish with the same draft_id and subdomain keeps and publishes in one call, which needs a paid plan. The subdomain is the web address, not the name shown at the top of the pages, which set_branding sets. Keeping a preview confirms the content is yours, or that you have permission to publish it; this is recorded.
Annotations the server declares
- title: Keep this site
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
propose_editStages a set of page changes (create, update, delete or move) for review, without keeping any of them.No findings
Why it is in this group
- The name "propose_edit" says "edit": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Stages a set of page changes (create, update, delete or move) for review, without keeping any of them. On a kept site it returns a link that shows the site with the changes for 24 hours and can be shared, the reference apply_edit takes to keep them, and any links the changes would break; readers see nothing until the set is kept and published. On a preview, given its draft_id, it only reports what the changes would do, and apply_edit with the same operations saves them. The operations are checked together: if one is refused, none is staged. A change that would take the site past its plan's room for pages or storage is refused. It is the first step of every change to a kept site's pages, except going back to an earlier version, which rollback does; a preview of new content starts with create_preview.
Annotations the server declares
- title: Propose a change
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
publishPublishes a kept site: its latest kept version goes out to readers at the site's address and replaces what they saw.Can send data outNo findings
Why it is in this group
- The name "publish" says "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "publish" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Publishes a kept site: its latest kept version goes out to readers at the site's address and replaces what they saw. It answers at once, the publish starts in about a minute and readers see it shortly after, and site_status shows the progress. Only kept versions go out, so changes from propose_edit need apply_edit first, and the site needs a front page at /. Publishing needs a paid plan with room for the site; without one nothing goes out and the answer says so. When the site has already published as often as its plan allows that day or month, the version waits and goes out on its own later. A writer on the site cannot publish; an editor or admin can. A site whose content was brought from somewhere else needs, once, the person's confirmation that it is theirs to publish (rights_confirmed). Given the draft_id of a preview nobody has kept yet, it first keeps the preview exactly as claim_draft does, under the name given as subdomain, and then publishes it; if it cannot publish, the preview stays kept and the answer says why. To keep a preview without publishing it, claim_draft is the tool, and it needs no paid plan. rollback goes back to an earlier version.
Annotations the server declares
- title: Publish
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
rollbackPuts a kept site, or chosen pages of it, back to how they were at an earlier version.No findings
Why it is in this group
- The description's first verb is "put": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Puts a kept site, or chosen pages of it, back to how they were at an earlier version. The result is saved as a new version, so no version is lost and a rollback can be undone by going back again; when nothing would change, no version is saved. If the site is published, it republishes by itself and readers see the restored pages, unless the site has already published as often as its plan allows that day or month, when it goes out on its own later. Only versions the site's plan lets it see can be chosen, by the numbers history lists. A writer on the site cannot roll back, and someone who looks after part of a site names those pages. It is for going back to a version; propose_edit makes a new change to a page.
Annotations the server declares
- title: Go back
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
set_brandingChange how a site looks: its theme, main colour, typeface, header links, logo and icon, and whether it has an Articles section.No findings
Why it is in this group
- The name "set_branding" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Change how a site looks: its theme, main colour, typeface, header links, logo and icon, and whether it has an Articles section. Only the site's owner can do this. Give only the things to change; the rest stay as they are. The changes show from the site's next publish. Every look change (theme, Articles, colour, typeface, header links, logo and icon) waits for the owner to publish; until then it shows in the site's preview. Before turning Articles on, tell the owner that readers won't see anything yet: they can look at it in the site's Preview, change anything, then publish, or ask to turn it off again. Offer to move pages that read like articles (comparisons, guides, news) under /articles with propose_edit; moved pages keep their old addresses. Page text is changed with propose_edit, not here. A logo or icon is taken from an address you give; say images_are_ours: true only when the owner has told you the pictures are theirs to use — otherwise they are kept but not shown until the owner confirms them on the site's preview. site_name is the name shown at the top of every page, not the web address: a preview's web address is chosen when it is kept, as claim_draft's or publish's subdomain, and no argument here changes it. On a preview nobody has kept yet, give its draft_id to set its name or its logo. Give languages to change the language the site's own words — Previous, Next, Search — are in.
Annotations the server declares
- title: Change how a site looks
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 1Claude Code: ask
create_previewCreates a temporary preview site from pages already converted to markdown, and returns its link and its draft_id.1 finding
Why it is in this group
- The name "create_preview" says "create": a word for a change.
Findings
- Info
The description is 2,254 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ess under /<code>/ (/es/guides/setup), with its code listed after the site's own."
Description, as the server wrote it Creates a temporary preview site from pages already converted to markdown, and returns its link and its draft_id. The preview belongs to no one until somebody keeps it, and expires if nobody does. The result says what to check, page by page, before the link is shared. It is the tool for content that has no site yet. A preview's pages are then changed with apply_edit and its draft_id; claim_draft keeps it, and publish keeps and publishes it in one call. A kept site is changed with propose_edit and apply_edit. It takes one entry per page; a record of where the content came from, exactly as it happened: a code repository, a documentation site, a product landing page, writing supplied in this conversation, a file attached to it, or nothing, when it was drafted from what the person described, with the address when there is one; the product's name; and, when the source shows one, the address of its logo. It reads no source itself: a call with no pages is answered with what to send instead. A source past the preview's page or size limit is refused, and the answer gives the limits. Which pages come over from a source with many pages is the person's choice, made after they see what was found and before it is converted: everything, one part, or a new structure. When they have already named the pages, that choice is made. Pages arrive finished, with no notes, placeholders, open questions or marks. A page with a note to its author, such as [GAP], [?] or TODO, is refused. Where the source is silent, a page carries the best answer and what was assumed is said in the conversation. On a legal page, the business's legal name, its address, the country whose law applies and who else handles its customers' data come only from the person or their source; a page missing one of them still reads complete without it, and what was assumed is said in the conversation. The page list is short: every page should be one a reader would open on its own; contact details and short notes belong inside another page. Every page, title and heading is in the site's language, passed as languages, like ["de"]. A translated copy is every page again, translated, at the same address under /<code>/ (/es/guides/setup), with its code listed after the site's own.
Annotations the server declares
- title: Create a preview site
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 5Show 5 read-only tools
find_referencesFinds the passages in a site that state a fact, and returns each with its page address, its line numbers and its text, best match first.No findings
Why it is in this group
- The name "find_references" says "find": a word for reading.
Description, as the server wrote it Finds the passages in a site that state a fact, and returns each with its page address, its line numbers and its text, best match first. On a kept site it matches meaning, so passages that say the fact in other words are found too, each with a confidence from 0 to 1; if that search cannot answer in time or fails, a plain word match comes back instead and the answer says so. On a preview, given its draft_id, it matches words only. Before a fact such as a refund window, a limit or a product name changes, it shows every page that states it, so one propose_edit can change them all. read_page reads a whole page.
Annotations the server declares
- title: Find every mention
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
historyLists a kept site's numbered versions, newest first, a page of them at a time: each line is the version number, what changed, who changed it and the date.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it Lists a kept site's numbered versions, newest first, a page of them at a time: each line is the version number, what changed, who changed it and the date. When older visible versions remain, the answer gives the starting_before value that lists the next page. Given compare_from and compare_to, it instead lists each page that differs between those two versions, as added, removed or the number of lines added and removed. How far back versions can be seen depends on the site's plan; older ones are still kept, and the answer says where the visible ones start. It answers what changed and when: site_status says what readers see now, and rollback takes these version numbers. A preview has no history until it is kept.
Annotations the server declares
- title: See what changed
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_pagesLists every page of a kept site, or of a preview given its draft_id, in one answer with no paging.No findings
Why it is in this group
- The name "list_pages" says "list": a word for reading.
Description, as the server wrote it Lists every page of a kept site, or of a preview given its draft_id, in one answer with no paging. Each line is a page's address and title, indented by depth, and on a kept site the date it last changed. A kept site lists the top-level pages first, then each deeper level, in alphabetical order of address within a level; a preview lists all its pages in alphabetical order of address. It is how page addresses are found: read_page reads one page in full, find_references finds the pages that state a given fact, and site_status says whether the site is published.
Annotations the server declares
- title: List pages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_pageReads one page of a kept site, or of a preview given its draft_id.No findings
Why it is in this group
- The name "read_page" says "read": a word for reading.
Description, as the server wrote it Reads one page of a kept site, or of a preview given its draft_id. It returns the page's address, its title and its full markdown; on a kept site also the date it last changed and the settings at the top of the page, as key: value lines. When no page has that address, it returns the five closest addresses instead (on a preview, every address the preview has). The markdown it returns is what a propose_edit update replaces. list_pages lists the addresses, and find_references finds which pages mention something without reading each one.
Annotations the server declares
- title: Read a page
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
site_statusReports the state of one site, or of a preview given its draft_id, at the moment of the call.No findings
Why it is in this group
- The name "site_status" says "status": a word for reading.
Description, as the server wrote it Reports the state of one site, or of a preview given its draft_id, at the moment of the call. For a kept site: its name and address; whether readers can see it, and at which version; whether a publish is under way; when it was last published; whether the last publish failed, and at which file and line; and, when the site has published as often as its plan allows for the day or month, when waiting changes go out. Someone whose role lets them keep changes also gets the changes waiting to be kept, each with a link to read it and the reference apply_edit takes. For a preview: its link, its number of pages, how many hours it has left and, for someone not signed in, how many more changes it can take before it is kept. With site left out on a connection that covers several sites, it lists them by name and address. It answers what readers see now and what is waiting: history lists past versions and who made them, and list_pages lists the pages.
Annotations the server declares
- title: Check a site
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.documarium.com/.well-known/oauth-protected-resource
- Authorization servers
- https://auth.documarium.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (6 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.documarium.com: tools/list returned 12 tools to an anonymous client, including propose_edit (destructive), apply_edit (destructive), publish (destructive), rollback (destructive), claim_draft (destructive) and 2 more
Posture changes
- Nov 11, 2026
- Tools that change things, listed without credentials: 8 to 7
Findings
Matches of fixed checks, with the text they matched.
- Infocreate_preview
The description is 2,254 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ess under /<code>/ (/es/guides/setup), with its code listed after the site's own."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools12 changed.~12 changedView diff
- Changed:apply_editDeletes or cancelsdescriptioninputSchema
- Changed:claim_draftDeletes or cancelsdescriptioninputSchema
- Changed:create_previewChanges thingsdescription
- Changed:find_referencesOnly readsdescriptioninputSchema
- Changed:historyOnly readsdescriptioninputSchema
- Changed:list_pagesOnly readsdescriptioninputSchema
- Changed:propose_editDeletes or cancelsdescriptioninputSchema
- Changed:publishDeletes or cancelsdescriptioninputSchema
- Changed:read_pageOnly readsdescriptioninputSchema
- Changed:rollbackDeletes or cancelsdescriptioninputSchema
- Changed:set_brandingDeletes or cancelsdescriptioninputSchema
- Changed:site_statusOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 7.View diff
- Tools that change things, listed without credentials: 8 to 7
Tools12 changed.~12 changedView diff
- Changed:apply_editDeletes or cancelsdescriptioninputSchema
- Changed:claim_draftDeletes or cancelsdescriptioninputSchema
- Changed:create_previewChanges thingsinputSchema
- Changed:find_referencesOnly readsdescriptioninputSchema
- Changed:historyOnly readsdescriptioninputSchema
- Changed:list_pagesOnly readsdescriptioninputSchema
- Changed:propose_editDeletes or cancelsdescriptioninputSchema
- Changed:publishDeletes or cancelsdescriptioninputSchema
- Changed:read_pageOnly readsdescriptioninputSchema
- Changed:rollbackDeletes or cancelsdescriptioninputSchema
- Changed:set_brandingDeletes or cancelsdescriptioninputSchema
- Changed:site_statusOnly readsdescriptioninputSchema
Install
Pinned to version 1.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http documarium https://mcp.documarium.comclaude mcp add --transport http documarium https://mcp.documarium.comRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__documarium__list_pages",
"mcp__documarium__read_page",
"mcp__documarium__find_references",
"mcp__documarium__history",
"mcp__documarium__site_status"
],
"ask": [
"mcp__documarium__create_preview"
],
"deny": [
"mcp__documarium__propose_edit",
"mcp__documarium__apply_edit",
"mcp__documarium__publish",
"mcp__documarium__rollback",
"mcp__documarium__claim_draft",
"mcp__documarium__set_branding"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as documarium. Review it before you use it.
Capability tags behind 1 rule
- mcp__documarium__publish outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.documarium/documarium/verify?hash=18c5ac6a776b361b6181a399e6a32f4661468cd220cfb8083ff4f4a99f64be72" | jq -e '.changed == false'Pinned hash 18c5ac6a776b, from Nov 14, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.documarium/documarium/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.documarium/documarium)Source: MCP Registry · repository. Synced Nov 14, 2026, 18:17 UTC.
Documarium MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Documarium MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Documarium MCP server delete data?
- Yes. 6 tools can delete, cancel or revoke something: propose_edit, apply_edit, publish, rollback, claim_draft and set_branding.
Can the Documarium MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Documarium MCP server have?
- 12 tools: 6 destructive, 1 write, 5 read. propose_edit, apply_edit, publish, rollback, claim_draft, set_branding, create_preview, list_pages and 4 more.
Does the Documarium MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Documarium MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish.
Has the Documarium MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.