io.github.CloudCorpRecords/teamctx
OCI · GHCR.IO/CLOUDCORPRECORDS/TEAMCTX · 2 COMPONENTS
Shared team context for ProductNow: search, read, write and organise workspace documents.
Available components
Last scanned (7 hours ago)
Scores higher than 46% of OCI servers
Category Documents and Files
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
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 995 tokens (~62/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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.
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.
- 2 Nov 26 40
First indexed and scored.
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 · Analysed oci/ghcr.io/cloudcorprecords/teamctx@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 →
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 →
archive ~48
Archive documents and folders, several at once; archiving a folder also archives contents the user can manage; nothing is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Ids of the documents and folders to archive. |
No output schema declared.
No examples provided.
comment_on_document ~65
Leave a comment on a document's current review version, posted as the user's personal agent.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | The comment text. |
| documentId | string | yes | Id of the document. |
| quotedText | string | – | Document text the comment quotes or anchors to. |
No output schema declared.
No examples provided.
create_document ~97
Create a new document, file it in a folder, and generate content with AI.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Additional context for content generation. |
| folderId | string | – | Id of the folder; omit to use the root. |
| name | string | yes | Name for the new document. |
| prompt | string | yes | Prompt describing the content to generate. |
| templateId | string | – | Id of a template to base the document on. |
No output schema declared.
No examples provided.
create_folder ~52
Create a folder only when no existing folder fits.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the new folder. |
| parentFolderId | string | – | Id of the folder to place items under; omit for the root. |
No output schema declared.
No examples provided.
edit_document ~54
Hand editing instructions to the document's own editing agent; the only tool that changes document content.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | Id of the document. |
| message | string | yes | Editing instructions for the document's editing agent. |
No output schema declared.
No examples provided.
fetch ~61
Read one document by id: full text, sections, comment threads, folder, and canonical URL.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | Id of the document. |
| documentVersionId | string | – | Id of a specific version to read; omit for the current version. |
No output schema declared.
No examples provided.
fetch_folder ~59
List a folder or the warehouse root, optionally as a nested tree.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | When true, return the folder as a nested tree including descendants. |
| folderId | string | – | Id of the folder; omit to use the root. |
No output schema declared.
No examples provided.
get_status ~36
Report whether a document's draft agent is still running an edit or is idle.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | Id of the document. |
No output schema declared.
No examples provided.
list_document_versions ~44
List every version of a document, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | Id of the document. |
| status | string | – | Only list versions with this status. |
No output schema declared.
No examples provided.
move ~61
Move documents and folders, several at once, into one folder or the root.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Ids of the documents and folders to move. |
| parentFolderId | string | – | Id of the folder to place items under; omit for the root. |
No output schema declared.
No examples provided.
remember ~67
Store one fact, decision, or note; ProductNow searches the warehouse, edits the covering document, or creates a new one in the right folder.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The fact, decision, or note to store. |
| hint | string | – | Optional hint about where the content belongs. |
No output schema declared.
No examples provided.
rename ~41
Change one document's or folder's name.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Id of the document or folder to rename. |
| name | string | yes | The new name. |
No output schema declared.
No examples provided.
reply_to_thread ~47
Reply to an existing comment thread as the user's personal agent.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The reply text. |
| threadId | string | yes | Id of the comment thread to reply to. |
No output schema declared.
No examples provided.
search ~151
Search the company's shared context (or ProductNow help via the product_help scope) for query-focused evidence excerpts with citations, or search folder names with resultType folders.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorNames | array | – | Only include items created by these people. |
| folderId | string | – | Id of the folder; omit to use the root. |
| query | string | – | Search query text. |
| resultType | string | – | Restrict results to documents or folders. |
| searchScope | string | – | Where to search: the shared workspace or ProductNow help. |
| updatedAfter | string | – | Only include items updated at or after this time. |
| updatedBefore | string | – | Only include items updated at or before this time. |
No output schema declared.
No examples provided.
update_document_status ~55
Promote the current draft with an action verb; each action leaves a fresh draft.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | Id of the document. |
| status | string | yes | Promotion action to apply: snapshot, review, or publish. |
No output schema declared.
No examples provided.
upload_media ~57
Allocate a signed upload URL (valid 5 minutes) for ProductNow-hosted image/video media.
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | yes | Name of the media file to upload. |
| mimeType | string | yes | MIME type of the media file. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/teamctx MCP server?
io.github.CloudCorpRecords/teamctx runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/teamctx: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/teamctx
claude mcp add cloudcorprecords-teamctx -- docker run --rm -i ghcr.io/cloudcorprecords/teamctx:0.1.0
What is the io.github.CloudCorpRecords/teamctx MCP server?
io.github.CloudCorpRecords/teamctx is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/teamctx. Shared team context for ProductNow: search, read, write and organise workspace documents. This page covers its container image (ghcr.io/cloudcorprecords/teamctx).
Is the io.github.CloudCorpRecords/teamctx MCP server safe to use?
io.github.CloudCorpRecords/teamctx scores 41 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/teamctx MCP server expose?
io.github.CloudCorpRecords/teamctx exposes 16 tools: search, fetch, fetch_folder, list_document_versions, get_status, and 11 more. Their descriptions and schemas cost roughly 995 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/teamctx MCP server still maintained?
io.github.CloudCorpRecords/teamctx 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.
What licence is the io.github.CloudCorpRecords/teamctx MCP server under?
io.github.CloudCorpRecords/teamctx declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.