Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/pageworkspace

OCI · GHCR.IO/CLOUDCORPRECORDS/PAGEWORKSPACE · 2 COMPONENTS

Notion pages, databases and blocks via the REST API, as MCP tools.

40 Trust /100

Last scanned (1 day ago)

Scores higher than 42% of OCI servers

Category Productivity and Notes

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 588 tokens (~49/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_block" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 0
    • Provenance: unverified → fail ▼ security
  • 2 Nov 26 39

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/pageworkspace@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 12 exposed · ~588 tokens

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 →

Tool Tokens
append_block_children ~60

Append child blocks to a Notion block or page.

NameTypeReqDescription
block_idstringyesThe ID of the block or page to append child blocks to.
childrenarrayyesArray of Notion block objects to append as children, in order.

No output schema declared.

No examples provided.

create_database ~82

Create a new Notion database under a parent page.

NameTypeReqDescription
parent_idstringyesThe ID of the parent page under which to create the new database.
propertiesobject–Optional Notion property schema object defining the database columns; when omitted, a single Name title property is used.
titlestringyesThe title text of the new database.

No output schema declared.

No examples provided.

create_page ~57

Create a new Notion page under a parent page with a title.

NameTypeReqDescription
parent_idstringyesThe ID of the parent page under which to create the new page.
titlestringyesThe title text of the new page.

No output schema declared.

No examples provided.

delete_block ~39

Delete (archive) a Notion block by its ID.

NameTypeReqDescription
block_idstringyesThe ID of the Notion block to delete (archive).

No output schema declared.

No examples provided.

get_block ~34

Retrieve a Notion block by its ID.

NameTypeReqDescription
block_idstringyesThe ID of the Notion block to retrieve.

No output schema declared.

No examples provided.

get_block_children ~60

List the child blocks of a Notion block or page.

NameTypeReqDescription
block_idstringyesThe ID of the block or page whose child blocks to list.
page_sizenumber–Optional maximum number of child blocks to return in one page.

No output schema declared.

No examples provided.

get_database ~34

Retrieve a Notion database by its ID.

NameTypeReqDescription
database_idstringyesThe ID of the Notion database to retrieve.

No output schema declared.

No examples provided.

get_page ~34

Retrieve a Notion page by its ID.

NameTypeReqDescription
page_idstringyesThe ID of the Notion page to retrieve.

No output schema declared.

No examples provided.

list_users ~17

List all users in the Notion workspace.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

query_database ~53

Query a Notion database and return its rows.

NameTypeReqDescription
database_idstringyesThe ID of the Notion database to query.
page_sizenumber–Optional maximum number of rows to return in one page.

No output schema declared.

No examples provided.

search ~58

Search Notion pages and databases by title.

NameTypeReqDescription
page_sizenumber–Optional maximum number of results to return in one page.
querystring–Optional search text matched against page and database titles; when omitted, recent items are returned.

No output schema declared.

No examples provided.

update_page ~60

Update a Notion page, for example to archive or restore it.

NameTypeReqDescription
archivedboolean–Optional archived state to set: true archives the page, false restores it.
page_idstringyesThe ID of the Notion page to update.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/pageworkspace MCP server?

io.github.CloudCorpRecords/pageworkspace runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/pageworkspace:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cloudcorprecords/pageworkspace

# add to Claude Code
claude mcp add cloudcorprecords-pageworkspace -- docker run --rm -i ghcr.io/cloudcorprecords/pageworkspace:0.1.0
Common questions

What is the io.github.CloudCorpRecords/pageworkspace MCP server?

io.github.CloudCorpRecords/pageworkspace is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/pageworkspace. Notion pages, databases and blocks via the REST API, as MCP tools. This page covers its container image (ghcr.io/cloudcorprecords/pageworkspace).

Is the io.github.CloudCorpRecords/pageworkspace MCP server safe to use?

io.github.CloudCorpRecords/pageworkspace scores 40 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 io.github.CloudCorpRecords/pageworkspace MCP server expose?

io.github.CloudCorpRecords/pageworkspace exposes 12 tools: search, list_users, get_page, create_page, update_page, and 7 more. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/pageworkspace MCP server still maintained?

io.github.CloudCorpRecords/pageworkspace is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/pageworkspace MCP server under?

io.github.CloudCorpRecords/pageworkspace declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.