Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Blinka Machine Mouths

REMOTE · BLINKA-MACHINE-MOUTHS.NETLIFY.APP · SCANNED OCT 7

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

65 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 854 tokens (~85/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

remote · blinka-machine-mouths.netlify.app

# add to Claude Code
claude mcp add --transport http tsukiryuu-blinka-machine-mouths 'https://blinka-machine-mouths.netlify.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "tsukiryuu-blinka-machine-mouths": {
      "url": "https://blinka-machine-mouths.netlify.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tsukiryuu-blinka-machine-mouths": {
      "type": "http",
      "url": "https://blinka-machine-mouths.netlify.app/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add tsukiryuu-blinka-machine-mouths --url 'https://blinka-machine-mouths.netlify.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  tsukiryuu-blinka-machine-mouths:
    url: "https://blinka-machine-mouths.netlify.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tsukiryuu-blinka-machine-mouths": {
      "Transport": "http",
      "Url": "https://blinka-machine-mouths.netlify.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add tsukiryuu-blinka-machine-mouths -t streamable-http -u 'https://blinka-machine-mouths.netlify.app/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Oct 26 +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.

  • 4 Oct 26 +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.

  • 3 Oct 26 0
    • Tool “code_signal_python” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 2 Oct 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 9 Oct 2026 · Probed https://blinka-machine-mouths.netlify.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US 16 Feb 2026 19 Mar 2027 ECDSA 256 SHA256-RSA cd5d0afb0611b5bd9d692535c0ca7c4
SANs: *.netlify.app, netlify.app
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 30 Mar 2021 29 Mar 2031 RSA 2048 SHA256-RSA cf5bd062b5602f47ab8502c23ccf066

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of blinka-machine-mouths.netlify.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
netlify.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://blinka-machine-mouths.netlify.app/mcp Verified 200
http (plaintext) http://blinka-machine-mouths.netlify.app/mcp HTTPS enforced 301 https://blinka-machine-mouths.netlify.app/mcp
MCP tools · 10 exposed · ~801 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
acceptance_check_delivery ~75

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.

NameTypeReqDescription
acceptance_criteriastringyes–
deliverystringyes–

No output schema declared.

No examples provided.

code_review_python ~78

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.

NameTypeReqDescription
codestringyes–
intentstringyes–
languagestring––

No output schema declared.

No examples provided.

code_signal_python ~73

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.

NameTypeReqDescription
codestringyes–
intentstringyes–
languagestring––

No output schema declared.

No examples provided.

debug_python_error ~84

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.

NameTypeReqDescription
codestringyes–
errorstringyes–
intentstring––
languagestring––

No output schema declared.

No examples provided.

procurement_catalog ~56

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.

NameTypeReqDescription
problemstring––

No output schema declared.

No examples provided.

recover_workflow ~103

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.

NameTypeReqDescription
available_tools–––
constraintsstring––
goalstringyes–
run_logstringyes–

No output schema declared.

No examples provided.

rescue_signal ~75

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.

NameTypeReqDescription
goalstringyes–
run_logstringyes–

No output schema declared.

No examples provided.

rescue_workflow_pro ~118

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.

NameTypeReqDescription
artifactstring––
artifact_intentstring––
artifact_kindstring––
available_tools–––
constraintsstring––
goalstringyes–
languagestring––
run_logstringyes–

No output schema declared.

No examples provided.

structure_json ~78

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.

NameTypeReqDescription
instructionstring––
schemaobjectyes–
textstringyes–

No output schema declared.

No examples provided.

validate_procurement_request ~61

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.

NameTypeReqDescription
requestobjectyes–

No output schema declared.

No examples provided.

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.