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.

io.github.khs0927/qwen38-free-gateway

REMOTE · API-V2.APPDEPLOY.AI · SCANNED SEP 20

Free Qwen3.8-27B gateway with isolated Minis provider, SSE, retry/failover, and MCP.

+1 this week 75 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 Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 257 tokens (~19/item across 13 items; 7 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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 io.github.khs0927/qwen38-free-gateway MCP server?

io.github.khs0927/qwen38-free-gateway is a hosted endpoint at https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/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 · api-v2.appdeploy.ai

# add to Claude Code
claude mcp add --transport http khs0927-qwen38-free-gateway 'https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "khs0927-qwen38-free-gateway": {
      "url": "https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "khs0927-qwen38-free-gateway": {
      "type": "http",
      "url": "https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.khs0927-qwen38-free-gateway]
url = "https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "khs0927-qwen38-free-gateway": {
      "type": "remote",
      "url": "https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add khs0927-qwen38-free-gateway --url 'https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  khs0927-qwen38-free-gateway:
    url: "https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "khs0927-qwen38-free-gateway": {
      "Transport": "http",
      "Url": "https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add khs0927-qwen38-free-gateway -t streamable-http -u 'https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp'
// mcp.json
{
  "mcpServers": {
    "khs0927-qwen38-free-gateway": {
      "type": "http",
      "url": "https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/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.

  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 +1

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

  • 7 Sept 26 +1

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

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

  • 2 Sept 26 +1

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

  • 31 Aug 26 +1

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

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 20 Sept 2026 · Probed https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=v2.appdeploy.ai CN=Amazon RSA 2048 M01,O=Amazon,C=US 27 May 2026 10 Dec 2026 RSA 2048 SHA256-RSA 33b3b471f2352fa74df06ffb7e7e53e
SANs: v2.appdeploy.ai, *.v2.appdeploy.ai, *.appdeploy.ai
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api-v2.appdeploy.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
appdeploy.ai. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp Verified 200
http (plaintext) http://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp HTTPS enforced 301 https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp
MCP tools · 7 exposed · ~179 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
gateway_health ~19

Check both zero-cost Qwen3.8 providers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_models ~17

List Qwen models through the active provider.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

provider_candidates ~19

Show evaluated HAPI and Hugging Face provider candidates.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

provider_list ~14

List configured zero-cost providers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

provider_probe ~24

Run a real routed gateway inference and report the exact-model ZeroGPU fallback state.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

provider_rank ~18

Rank the healthy free providers by priority and latency.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

qwen_chat ~68

Ask Qwen3.8-27B through H200 with verified exact-model ZeroGPU failover.

NameTypeReqDescription
max_tokensinteger
promptstringyes
reasoning_effortstring
systemstring
temperaturenumber

No output schema declared.

No examples provided.

Common questions

What is the io.github.khs0927/qwen38-free-gateway MCP server?

io.github.khs0927/qwen38-free-gateway is an MCP server listed in the public MCP registry as io.github.khs0927/qwen38-free-gateway. Free Qwen3.8-27B gateway with isolated Minis provider, SSE, retry/failover, and MCP. This page covers its hosted endpoint (https://api-v2.appdeploy.ai/app/qwen3-8-free-gateway-n995yy/api/mcp).

Is the io.github.khs0927/qwen38-free-gateway MCP server safe to use?

io.github.khs0927/qwen38-free-gateway scores 75 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 io.github.khs0927/qwen38-free-gateway MCP server expose?

io.github.khs0927/qwen38-free-gateway exposes 7 tools: qwen_chat, gateway_health, provider_list, provider_rank, provider_probe, and 2 more. Their descriptions and schemas cost roughly 179 tokens of context every time the server is loaded.

Does the io.github.khs0927/qwen38-free-gateway MCP server require authentication?

No. We connected to io.github.khs0927/qwen38-free-gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.khs0927/qwen38-free-gateway MCP server still maintained?

io.github.khs0927/qwen38-free-gateway is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.