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

Open AI models through one API: chat completions, live model catalogue, prices, cost estimates.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/modelrelay`
- 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.
  - 31 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 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 814 tokens (~203/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "synap_chat_completion" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 4 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/modelrelay MCP server?

io.github.CloudCorpRecords/modelrelay runs locally as an npm package, launched with npx -y @reneturcios/modelrelay 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-modelrelay -- npx -y @reneturcios/modelrelay mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-modelrelay": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/modelrelay",
        "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-16 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 53)

First indexed and scored.

## MCP tools (4)

### `synap_chat_completion` (~309 tokens)

Run a chat completion on Synap

Send a conversation to a model on Synap, Linkrra's OpenAI-compatible inference API, and get the model's reply. Use this when you need text generated, code written or a question answered by one of the open models Synap serves. This is the only tool here that costs money: it bills prompt and completion tokens to the Synap API key supplied as the Authorization: Bearer header on the MCP connection. With no key it returns an error and nothing is spent; a key with no balance returns insufficient_credits. Call synap_estimate_cost first if the price matters. Returns the standard OpenAI chat.completion JSON (choices[0].message.content holds the reply, usage holds token counts). The call is not streamed and keeps no memory between calls — send the full message history each time.

Input parameters:

- `max_tokens` (integer): Upper limit on tokens generated in the reply. Omit to use the model default; lower it to cap cost.
- `messages` (array, required): The conversation so far, oldest first. The last message is normally the user turn to answer.
- `model` (string, required): Model id exactly as returned by synap_list_models, e.g. "qwen3-coder-30b". Use "synap-v1" to let Synap pick the cheapest model that can handle the request.
- `temperature` (number): Sampling randomness, 0 to 2. Lower is more deterministic. Omit to use the model default.

### `synap_list_models` (~204 tokens)

List Synap models and prices

List the models Synap serves right now, each with its price per million tokens, context window and what it is good at. Use this to choose a model id before calling synap_chat_completion, or to compare prices. Free, read-only, no API key needed, and safe to call repeatedly; the list is live, so models can appear or go between calls. Returns {"object":"list","count":N,"data":[{id,name,capability,tier,context_tokens,max_output_tokens,pricing,data_policy}]}; pricing is USD per million prompt and completion tokens and is absent for the auto-routing ids ("synap-v1"), which bill at the price of the model they route to. For every field of one model use synap_get_model.

Input parameters:

- `query` (string): Optional case-insensitive filter matched against model id, name and capability, e.g. "coder", "qwen" or "vision". Omit to list everything.

### `synap_get_model` (~104 tokens)

Get one Synap model in full

Return the complete catalogue record for one Synap model: pricing, context and output limits, supported parameters, quantisation, data-retention policy and readiness. Use this after synap_list_models when you need details the summary leaves out. Free, read-only and needs no API key. Returns the raw model object, or an error naming the id if Synap does not serve it.

Input parameters:

- `model` (string, required): Model id exactly as returned by synap_list_models.

### `synap_estimate_cost` (~197 tokens)

Estimate the cost of a Synap call

Work out what a chat completion would cost on Synap from token counts, using the live price list. Use this before synap_chat_completion when budget matters, or to compare models for a job. Free, read-only, needs no API key and runs no model. Returns {model, prompt_tokens, completion_tokens, prompt_usd, completion_usd, total_usd, pricing}. It is an estimate: the real charge uses the token counts the model reports afterwards. Auto-routing ids such as "synap-v1" have no fixed price and return an error saying so.

Input parameters:

- `completion_tokens` (integer): Tokens you expect back. Use your max_tokens for a worst case. Defaults to 0.
- `model` (string, required): Model id exactly as returned by synap_list_models.
- `prompt_tokens` (integer, required): Tokens you will send (system + conversation). Roughly 4 characters of English per token.

## Diagnostics

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

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 53

## Common questions

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

io.github.CloudCorpRecords/modelrelay is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/modelrelay. Open AI models through one API: chat completions, live model catalogue, prices, cost estimates. This page covers its npm package (@reneturcios/modelrelay).

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

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

io.github.CloudCorpRecords/modelrelay exposes 4 tools: synap_chat_completion, synap_list_models, synap_get_model, synap_estimate_cost. Their descriptions and schemas cost roughly 814 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/modelrelay 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/modelrelay MCP server under?

io.github.CloudCorpRecords/modelrelay 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/modelrelay MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/modelrelay, 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/modelrelay: 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/modelrelay
- Socket report: https://socket.dev/npm/package/@reneturcios/modelrelay
- Repository: https://github.com/CloudCorpRecords/modelrelay
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-modelrelay/reneturcios-modelrelay.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-modelrelay/reneturcios-modelrelay/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-modelrelay/reneturcios-modelrelay.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-modelrelay/reneturcios-modelrelay
