# io.github.CloudCorpRecords/teamctx (oci · ghcr.io/cloudcorprecords/teamctx)

Shared team context for ProductNow: search, read, write and organise workspace documents.

- Trust score: 41/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/teamctx`: 69/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-teamctx/reneturcios-teamctx.md), [page](https://verifymcp.io/servers/cloudcorprecords-teamctx/reneturcios-teamctx)
- oci · `ghcr.io/cloudcorprecords/teamctx`: 41/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-teamctx/ghcr-io-cloudcorprecords-teamctx.md), [page](https://verifymcp.io/servers/cloudcorprecords-teamctx/ghcr-io-cloudcorprecords-teamctx)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/teamctx`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 995 tokens (~62/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add cloudcorprecords-teamctx -- docker run --rm -i ghcr.io/cloudcorprecords/teamctx:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-teamctx": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/teamctx:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-teamctx": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/teamctx:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-teamctx -- docker run --rm -i ghcr.io/cloudcorprecords/teamctx:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-teamctx": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/teamctx:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-teamctx:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/teamctx:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-teamctx": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/teamctx:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-teamctx": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/teamctx:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 41, +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.

### 2026-11-02 (score 40)

First indexed and scored.

## MCP tools (16)

### `search` (~151 tokens)

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.

Input parameters:

- `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.

### `fetch` (~61 tokens)

Read one document by id: full text, sections, comment threads, folder, and canonical URL.

Input parameters:

- `documentId` (string, required): Id of the document.
- `documentVersionId` (string): Id of a specific version to read; omit for the current version.

### `fetch_folder` (~59 tokens)

List a folder or the warehouse root, optionally as a nested tree.

Input parameters:

- `deep` (boolean): When true, return the folder as a nested tree including descendants.
- `folderId` (string): Id of the folder; omit to use the root.

### `list_document_versions` (~44 tokens)

List every version of a document, newest first.

Input parameters:

- `documentId` (string, required): Id of the document.
- `status` (string): Only list versions with this status.

### `get_status` (~36 tokens)

Report whether a document's draft agent is still running an edit or is idle.

Input parameters:

- `documentId` (string, required): Id of the document.

### `remember` (~67 tokens)

Store one fact, decision, or note; ProductNow searches the warehouse, edits the covering document, or creates a new one in the right folder.

Input parameters:

- `content` (string, required): The fact, decision, or note to store.
- `hint` (string): Optional hint about where the content belongs.

### `create_document` (~97 tokens)

Create a new document, file it in a folder, and generate content with AI.

Input parameters:

- `context` (string): Additional context for content generation.
- `folderId` (string): Id of the folder; omit to use the root.
- `name` (string, required): Name for the new document.
- `prompt` (string, required): Prompt describing the content to generate.
- `templateId` (string): Id of a template to base the document on.

### `edit_document` (~54 tokens)

Hand editing instructions to the document's own editing agent; the only tool that changes document content.

Input parameters:

- `documentId` (string, required): Id of the document.
- `message` (string, required): Editing instructions for the document's editing agent.

### `update_document_status` (~55 tokens)

Promote the current draft with an action verb; each action leaves a fresh draft.

Input parameters:

- `documentId` (string, required): Id of the document.
- `status` (string, required): Promotion action to apply: snapshot, review, or publish.

### `create_folder` (~52 tokens)

Create a folder only when no existing folder fits.

Input parameters:

- `name` (string, required): Name for the new folder.
- `parentFolderId` (string): Id of the folder to place items under; omit for the root.

### `move` (~61 tokens)

Move documents and folders, several at once, into one folder or the root.

Input parameters:

- `ids` (array, required): Ids of the documents and folders to move.
- `parentFolderId` (string): Id of the folder to place items under; omit for the root.

### `rename` (~41 tokens)

Change one document's or folder's name.

Input parameters:

- `id` (string, required): Id of the document or folder to rename.
- `name` (string, required): The new name.

### `archive` (~48 tokens)

Archive documents and folders, several at once; archiving a folder also archives contents the user can manage; nothing is deleted.

Input parameters:

- `ids` (array, required): Ids of the documents and folders to archive.

### `comment_on_document` (~65 tokens)

Leave a comment on a document's current review version, posted as the user's personal agent.

Input parameters:

- `comment` (string, required): The comment text.
- `documentId` (string, required): Id of the document.
- `quotedText` (string): Document text the comment quotes or anchors to.

### `reply_to_thread` (~47 tokens)

Reply to an existing comment thread as the user's personal agent.

Input parameters:

- `message` (string, required): The reply text.
- `threadId` (string, required): Id of the comment thread to reply to.

### `upload_media` (~57 tokens)

Allocate a signed upload URL (valid 5 minutes) for ProductNow-hosted image/video media.

Input parameters:

- `fileName` (string, required): Name of the media file to upload.
- `mimeType` (string, required): MIME type of the media file.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-teamctx/ghcr-io-cloudcorprecords-teamctx#diagnostics

## Score history

- 2026-11-05: 41
- 2026-11-04: 41
- 2026-11-03: 40
- 2026-11-02: 40

## Common questions

### 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.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/teamctx
- Repository: https://github.com/CloudCorpRecords/teamctx
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-teamctx/ghcr-io-cloudcorprecords-teamctx.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-teamctx/ghcr-io-cloudcorprecords-teamctx.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-teamctx/ghcr-io-cloudcorprecords-teamctx