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.

Ryter Pro

PYPI · RYTERPRO-MCP · SCANNED SEP 21

MCP server for humanizing and rewriting text with the Ryter Pro API.

Available components

pypi · ryterpro-mcp 64
0 this week 64 Trust /100
Trust breakdown (7 categories)

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

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 84 tokens (~42/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 Ryter Pro MCP server?

Ryter Pro runs locally as a PyPI package, launched with uvx ryterpro-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · ryterpro-mcp

# add to Claude Code
claude mcp add apiihub33-cyber-ryterpro-mcp -- uvx ryterpro-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "apiihub33-cyber-ryterpro-mcp": {
      "command": "uvx",
      "args": [
        "ryterpro-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "apiihub33-cyber-ryterpro-mcp": {
      "command": "uvx",
      "args": [
        "ryterpro-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add apiihub33-cyber-ryterpro-mcp -- uvx ryterpro-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "apiihub33-cyber-ryterpro-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "ryterpro-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add apiihub33-cyber-ryterpro-mcp --command uvx --arg ryterpro-mcp
# ~/.hermes/config.yaml
mcp_servers:
  apiihub33-cyber-ryterpro-mcp:
    command: "uvx"
    args: ["ryterpro-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "apiihub33-cyber-ryterpro-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "ryterpro-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add apiihub33-cyber-ryterpro-mcp -t stdio -c uvx -a ryterpro-mcp
// mcp.json
{
  "mcpServers": {
    "apiihub33-cyber-ryterpro-mcp": {
      "command": "uvx",
      "args": [
        "ryterpro-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 19 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 18 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +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.

  • 15 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 14 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 13 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.

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 21 Sept 2026 · Analysed pypi/ryterpro-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 32 packages
Packages resolved 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~53 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
humanize_text ~31

Humanize text using the Ryter Pro API.

NameTypeReqDescription
mode–––
textstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

ryterpro_api_info ~22

Return Ryter Pro MCP server configuration and documentation links.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes–

No examples provided.

Common questions

What is the Ryter Pro MCP server?

Ryter Pro is an MCP server listed in the public MCP registry as io.github.apiihub33-cyber/ryterpro-mcp. MCP server for humanizing and rewriting text with the Ryter Pro API. This page covers its PyPI package (ryterpro-mcp).

Is the Ryter Pro MCP server safe to use?

Ryter Pro scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 Ryter Pro MCP server expose?

Ryter Pro exposes 2 tools: humanize_text, ryterpro_api_info. Their descriptions and schemas cost roughly 53 tokens of context every time the server is loaded.

Is the Ryter Pro MCP server still maintained?

Ryter Pro is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Ryter Pro MCP server under?

Ryter Pro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.