verbashield-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERBASHIELD_API_KEY | Yes | Your VerbaShield API key (vs_live_...). Obtain from verbashield.ru/docs. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verbashield_humanizeC | Humanize AI-generated text via VerbaShield |
| verbashield_detectB | Detect AI-generated text via VerbaShield |
| verbashield_get_quotaA | Return remaining VerbaShield quota, bonus balance, and rate limit |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool performs a distinct function: humanize transforms text, detect analyzes text, and get_quota retrieves account usage. There is no overlap or ambiguity between the three tools.
All tools share the verbashield_ prefix and use lowercase snake_case. The pattern is consistent and predictable: verbashield_humanize, verbashield_detect, and verbashield_get_quota.
Three tools is well-scoped for a narrow service wrapper around VerbaShield, covering the primary actions and account quota without unnecessary bulk.
The tool set covers the full lifecycle for this service: text transformation, detection, and quota monitoring. No obvious gaps exist for the stated domain.