# io.github.CloudCorpRecords/matixworks (npm · @reneturcios/matixworks)

Read a software studio's public site data: open positions, case studies and company profile.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/matixworks`
- 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-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 519 tokens (~103/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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/matixworks MCP server?

io.github.CloudCorpRecords/matixworks runs locally as an npm package, launched with npx -y @reneturcios/matixworks mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-matixworks -- npx -y @reneturcios/matixworks mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-matixworks": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/matixworks",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-matixworks": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/matixworks",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-matixworks -- npx -y @reneturcios/matixworks mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-matixworks": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/matixworks",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-matixworks --command npx --arg -y --arg @reneturcios/matixworks --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-matixworks:
    command: "npx"
    args: ["-y", "@reneturcios/matixworks", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-matixworks": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/matixworks",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-matixworks -t stdio -c npx -a -y @reneturcios/matixworks mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-matixworks": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/matixworks",
        "mcp"
      ]
    }
  }
}
```

## 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-18 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 56)

First indexed and scored.

## MCP tools (5)

### `dynomatix_list_open_positions` (~95 tokens)

List open positions

List every role Dynomatix is currently hiring for. Returns one entry per position with its slug, title, one-line summary, employment type, canonical URL and posting dates. Start here before dynomatix_get_position or dynomatix_submit_application: the slug this returns is the value both of them expect. An empty list means there are no openings right now, not that the lookup failed. Takes no arguments.

### `dynomatix_get_position` (~121 tokens)

Read a job posting

Read one job posting in full: responsibilities, requirements and how the role is set up. Returns the posting's own markdown, frontmatter included — the title and canonical URL it opens with are the citation to quote when you tell someone about the role. Call dynomatix_list_open_positions first to get a valid slug; a slug that is not currently open is refused rather than guessed at.

Input parameters:

- `slug` (string, required): The position's slug, exactly as dynomatix_list_open_positions returned it. Lowercase letters, digits and hyphens.

### `dynomatix_list_work` (~109 tokens)

List past and current work

List the products and client work Dynomatix has shipped. Returns one entry per item with its name, the year it started, its status, a short description and its links. Retired items are included — the site shows them and `status` says which is which — because a track record with the failures removed is not a track record. Where `caseStudyUrl` is not null, dynomatix_get_work will return the full write-up for that slug. Takes no arguments.

### `dynomatix_get_work` (~116 tokens)

Read a case study

Read one case study in full: what the problem was, what was built and what it changed. Returns the study's own markdown, frontmatter included — the title and canonical URL it opens with are the citation to quote. Call dynomatix_list_work first for a valid slug; only entries whose `caseStudyUrl` is not null have a write-up to return.

Input parameters:

- `slug` (string, required): The item's slug, exactly as dynomatix_list_work returned it. Lowercase letters, digits and hyphens.

### `dynomatix_about` (~78 tokens)

About Dynomatix

Who Dynomatix is, what it sells and how to reach it. Returns the company's identity and tagline, its engagement types, both contact addresses, its key pages and its track record. Read this first if you are deciding whether this company fits a need; use dynomatix_submit_enquiry to start a conversation. Takes no arguments.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-matixworks/reneturcios-matixworks#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 56

## Common questions

### What is the io.github.CloudCorpRecords/matixworks MCP server?

io.github.CloudCorpRecords/matixworks is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/matixworks. Read a software studio's public site data: open positions, case studies and company profile. This page covers its npm package (@reneturcios/matixworks).

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

io.github.CloudCorpRecords/matixworks scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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/matixworks MCP server expose?

io.github.CloudCorpRecords/matixworks exposes 5 tools: dynomatix_list_open_positions, dynomatix_get_position, dynomatix_list_work, dynomatix_get_work, dynomatix_about. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/matixworks is still listed as active in the MCP registry. We last reached this channel on 21 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/matixworks MCP server under?

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

### What did VerifyMCP test on the io.github.CloudCorpRecords/matixworks MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/matixworks, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/matixworks: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/matixworks
- Socket report: https://socket.dev/npm/package/@reneturcios/matixworks
- Repository: https://github.com/CloudCorpRecords/matixworks
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-matixworks/reneturcios-matixworks.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-matixworks/reneturcios-matixworks/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-matixworks/reneturcios-matixworks.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-matixworks/reneturcios-matixworks
