Sms Verify3 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | 不适用 | |
| PORT | No | 不适用 | |
| API_KEY | Yes | API 密钥 |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| estimate_costC | Estimate Cost |
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 1 tool
With only one tool, there is no risk of confusing it with others. The tool's purpose is distinct as the only available operation.
The single tool follows a clear verb_noun pattern ('estimate_cost'), which is consistent and predictable.
A single tool for a server named 'Sms Verify3' is far too few for the apparent scope of SMS verification. The count feels minimal and likely insufficient.
The server appears intended for SMS verification, but only an estimation tool is present. Core operations like sending or verifying codes are entirely missing, leaving major gaps.