# mcp-computeflux (mcpb · send_mcp-computeflux.mcpb)

OpenAI-compatible multi-model inference via ComputeFlux (Polkadot testnet, TEE-verifiable). stdio.

- Trust score: 51/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `send_mcp-computeflux.mcpb`: 51/100 (this document), [markdown](https://verifymcp.io/servers/computeflux2026isgod-mcp-computeflux/send-mcp-computeflux.md), [page](https://verifymcp.io/servers/computeflux2026isgod-mcp-computeflux/send-mcp-computeflux)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/computeflux2026isgod/mcp-computeflux/releases/download/v1.0.0.0/send_mcp-computeflux.mcpb`
- Transport: `stdio`
- SHA-256: `49e4b93f1c178ab71b6d770c77f163a2d979481eaf720d8c6caf75c5d993b8d3`

## 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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **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 31 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 (good).
  - Tool/resource definitions use about 166 tokens (~83/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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; "computeflux_chat" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; 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 mcp-computeflux server?

mcp-computeflux ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 49e4b93f1c178ab71b6d770c77f163a2d979481eaf720d8c6caf75c5d993b8d3; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/computeflux2026isgod/mcp-computeflux/releases/download/v1.0.0.0/send_mcp-computeflux.mcpb`
- SHA-256: `49e4b93f1c178ab71b6d770c77f163a2d979481eaf720d8c6caf75c5d993b8d3`

### Verify on macOS / Linux

```bash
echo "49e4b93f1c178ab71b6d770c77f163a2d979481eaf720d8c6caf75c5d993b8d3  send_mcp-computeflux.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\send_mcp-computeflux.mcpb).Hash -eq "49e4b93f1c178ab71b6d770c77f163a2d979481eaf720d8c6caf75c5d993b8d3"
```

## 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 51, 0)

- [security] Stability: 0.97 → pass

### 2026-11-03 (score 51, +1)

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

### 2026-11-01 (score 50, +1)

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

### 2026-10-30 (score 49, +1)

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

### 2026-10-28 (score 48, +1)

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

### 2026-10-25 (score 47, +1)

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

### 2026-10-23 (score 46, +1)

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

### 2026-10-21 (score 45, +1)

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

## MCP tools (2)

### `computeflux_models` (~25 tokens)

List the models available on the ComputeFlux (OpenAI-compatible) endpoint.

### `computeflux_chat` (~111 tokens)

Send a chat completion request to the ComputeFlux (OpenAI-compatible) endpoint. Returns the assistant message text plus usage. Use model like "CAO/deepseek-flash".

Input parameters:

- `max_tokens` (number): Max tokens to generate (optional).
- `messages` (array, required): Chat messages (OpenAI schema).
- `model` (string, required): Model id, e.g. "CAO/deepseek-flash"
- `temperature` (number): Sampling temperature (optional, default 1.0).

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/computeflux2026isgod-mcp-computeflux/send-mcp-computeflux#diagnostics

## Score history

- 2026-11-05: 51
- 2026-11-04: 51
- 2026-11-03: 51
- 2026-11-02: 50
- 2026-11-01: 50
- 2026-10-31: 49
- 2026-10-30: 49
- 2026-10-29: 48
- 2026-10-28: 48
- 2026-10-27: 47
- 2026-10-26: 47
- 2026-10-25: 47
- 2026-10-24: 46
- 2026-10-23: 46
- 2026-10-22: 45
- 2026-10-21: 45
- 2026-10-20: 44
- 2026-10-19: 43
- 2026-10-18: 42
- 2026-10-17: 43
- 2026-10-16: 42
- 2026-10-15: 42
- 2026-10-14: 41
- 2026-10-13: 37
- 2026-10-12: 37
- 2026-10-10: 37
- 2026-10-05: 37
- 2026-10-04: 9

## Common questions

### What is the mcp-computeflux server?

mcp-computeflux is listed in the public MCP registry as io.github.computeflux2026isgod/mcp-computeflux. OpenAI-compatible multi-model inference via ComputeFlux (Polkadot testnet, TEE-verifiable). stdio. This page covers its MCPB bundle (https://github.com/computeflux2026isgod/mcp-computeflux/releases/download/v1.0.0.0/send_mcp-computeflux.mcpb).

### Is the mcp-computeflux server safe to use?

mcp-computeflux scores 51 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 mcp-computeflux server expose?

mcp-computeflux exposes 2 tools: computeflux_models, computeflux_chat. Their descriptions and schemas cost roughly 136 tokens of context every time the server is loaded.

### What licence is the mcp-computeflux server under?

mcp-computeflux 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

- Repository: https://github.com/computeflux2026isgod/mcp-computeflux
- Changelog RSS feed: https://verifymcp.io/servers/computeflux2026isgod-mcp-computeflux/send-mcp-computeflux.xml
- Changelog JSON feed: https://verifymcp.io/servers/computeflux2026isgod-mcp-computeflux/send-mcp-computeflux.json
- HTML version of this page: https://verifymcp.io/servers/computeflux2026isgod-mcp-computeflux/send-mcp-computeflux