# Blinka Machine Mouths (remote · blinka-machine-mouths.netlify.app)

Paid agent tools plus free procurement discovery and validation. No private Mika state exposed.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `blinka-machine-mouths.netlify.app`: 65/100 (this document), [markdown](https://verifymcp.io/servers/tsukiryuu-blinka-machine-mouths/blinka-machine-mouths.md), [page](https://verifymcp.io/servers/tsukiryuu-blinka-machine-mouths/blinka-machine-mouths)

## Channel facts

- Endpoint: `https://blinka-machine-mouths.netlify.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-07.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 854 tokens (~85/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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.

## Install

### How do I install the Blinka Machine Mouths MCP server?

Blinka Machine Mouths is a hosted endpoint at https://blinka-machine-mouths.netlify.app/mcp, so there is nothing to install locally. 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 --transport http tsukiryuu-blinka-machine-mouths 'https://blinka-machine-mouths.netlify.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tsukiryuu-blinka-machine-mouths": {
      "url": "https://blinka-machine-mouths.netlify.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tsukiryuu-blinka-machine-mouths": {
      "type": "http",
      "url": "https://blinka-machine-mouths.netlify.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tsukiryuu-blinka-machine-mouths]
url = "https://blinka-machine-mouths.netlify.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tsukiryuu-blinka-machine-mouths": {
      "type": "remote",
      "url": "https://blinka-machine-mouths.netlify.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tsukiryuu-blinka-machine-mouths --url 'https://blinka-machine-mouths.netlify.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tsukiryuu-blinka-machine-mouths:
    url: "https://blinka-machine-mouths.netlify.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tsukiryuu-blinka-machine-mouths": {
      "Transport": "http",
      "Url": "https://blinka-machine-mouths.netlify.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tsukiryuu-blinka-machine-mouths -t streamable-http -u 'https://blinka-machine-mouths.netlify.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tsukiryuu-blinka-machine-mouths": {
      "type": "http",
      "url": "https://blinka-machine-mouths.netlify.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-07 (score 65, +1)

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

### 2026-10-04 (score 64, +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-10-03 (score 63, 0)

- [security] Tool “code_signal_python” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-02 (score 63)

First indexed and scored.

## MCP tools (10)

### `structure_json` (~78 tokens)

Paid $0.01 Base USDC. Extract JSON from unstructured text, prose, notes, or logs into a caller-supplied JSON Schema using only explicit source evidence. No URL fetch, private Mika state, or retained request body.

Input parameters:

- `instruction` (string)
- `schema` (object, required)
- `text` (string, required)

### `acceptance_check_delivery` (~75 tokens)

Paid $1.00 Base USDC. Independently check a supplied delivery only against supplied acceptance criteria. Returns criterion-level pass/fail/unclear evidence. No browsing, tool execution, private Mika context, hidden-state inference, or retained input.

Input parameters:

- `acceptance_criteria` (string, required)
- `delivery` (string, required)

### `recover_workflow` (~103 tokens)

Paid $0.25 Base USDC. Diagnose a failed workflow, deployment, or agent run into completed state, blockers, retry traps, unknowns, and the smallest safe next action constrained to exact caller-supplied tool names, plus a deterministic continuation contract with explicit authority non-inheritance. The service never executes the continuation.

Input parameters:

- `available_tools`
- `constraints` (string)
- `goal` (string, required)
- `run_log` (string, required)

### `rescue_signal` (~75 tokens)

Paid $0.005 Base USDC. Cheap first-pass failed-run triage: evidence-backed blocker, retry trap, smallest next state change, and an optional smallest-sufficient continuation route when more help is warranted. No followup is purchased or executed automatically.

Input parameters:

- `goal` (string, required)
- `run_log` (string, required)

### `code_signal_python` (~73 tokens)

Paid $0.005 Base USDC. Fast static Python bug/security preflight with an optional cost-transparent /code-review continuation only for high/critical or multiple findings. Code is parsed but never executed or retained.

Input parameters:

- `code` (string, required)
- `intent` (string, required)
- `language` (string)

### `debug_python_error` (~84 tokens)

Paid $0.01 Base USDC. Debug Python code from source plus an observed error/exception/traceback. Returns a bounded diagnosis, evidence, strongest static issue, and suggested fix. Submitted source is never executed or retained.

Input parameters:

- `code` (string, required)
- `error` (string, required)
- `intent` (string)
- `language` (string)

### `code_review_python` (~78 tokens)

Paid $0.25 Base USDC. Review caller-supplied Python source against its intended behavior for high-confidence bugs, security issues, missing edge cases, and repair suggestions. Code is parsed/reviewed but never executed or retained.

Input parameters:

- `code` (string, required)
- `intent` (string, required)
- `language` (string)

### `rescue_workflow_pro` (~118 tokens)

Paid $3.00 Base USDC. Premium failed-run repair packet: evidence-bound workflow recovery plus bounded Python code or text/config review, prioritized fixes, retry traps, and an exact tool-bounded next action. Artifacts are never executed.

Input parameters:

- `artifact` (string)
- `artifact_intent` (string)
- `artifact_kind` (string)
- `available_tools`
- `constraints` (string)
- `goal` (string, required)
- `language` (string)
- `run_log` (string, required)

### `procurement_catalog` (~56 tokens)

Free public discovery. List Blinka/Little Life Moths bounded service offers plus the machine-readable procurement request schema and public submission channels. Does not accept work, take payment, or expose private Mika state.

Input parameters:

- `problem` (string)

### `validate_procurement_request` (~61 tokens)

Free public procurement preflight. Validate a buyer-authored authority-verification request against the public request schema and return a non-binding scope-review handoff with candidate bounded services. No request body is retained and no payment occurs.

Input parameters:

- `request` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tsukiryuu-blinka-machine-mouths/blinka-machine-mouths#diagnostics

## Score history

- 2026-10-07: 65
- 2026-10-04: 64
- 2026-10-03: 63
- 2026-10-02: 63

## Common questions

### What is the Blinka Machine Mouths MCP server?

Blinka Machine Mouths is an MCP server listed in the public MCP registry as io.github.tsukiryuu/blinka-machine-mouths. Paid agent tools plus free procurement discovery and validation. No private Mika state exposed. This page covers its hosted endpoint (https://blinka-machine-mouths.netlify.app/mcp).

### Is the Blinka Machine Mouths MCP server safe to use?

Blinka Machine Mouths scores 65 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 Blinka Machine Mouths MCP server expose?

Blinka Machine Mouths exposes 10 tools: structure_json, acceptance_check_delivery, recover_workflow, rescue_signal, code_signal_python, and 5 more. Their descriptions and schemas cost roughly 801 tokens of context every time the server is loaded.

### Does the Blinka Machine Mouths MCP server require authentication?

No. We connected to Blinka Machine Mouths without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Blinka Machine Mouths MCP server still maintained?

Blinka Machine Mouths is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://blinka-machine-mouths.netlify.app/mcp
- Repository: https://github.com/tsukiryuu/blinka-nest
- Website: https://blinka-machine-mouths.netlify.app/
- Changelog RSS feed: https://verifymcp.io/servers/tsukiryuu-blinka-machine-mouths/blinka-machine-mouths.xml
- Changelog JSON feed: https://verifymcp.io/servers/tsukiryuu-blinka-machine-mouths/blinka-machine-mouths.json
- HTML version of this page: https://verifymcp.io/servers/tsukiryuu-blinka-machine-mouths/blinka-machine-mouths