Skip to main content
Glama
BACH-AI-Tools

Sms Verify3 MCP Server

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Sms Verify3 MCP Server

English | 简体中文 | 繁體中文

Sms Verify3 的 MCP 服务器，由 API-to-MCP 工具自动生成。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-sms_verify3）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: VirtualSMS MCP Server

简介

这是一个使用 FastMCP 自动生成的 MCP 服务器，用于访问 Sms Verify3 API。

  • PyPI 包名: bach-sms_verify3

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-sms_verify3

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-sms_verify3 bach_sms_verify3

# 或指定版本
uvx --from bach-sms_verify3@latest bach_sms_verify3

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-sms_verify3

# 运行（命令名使用下划线）
bach_sms_verify3

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "sms_verify3": {
      "command": "python",
      "args": ["E:\path\to\sms_verify3\server.py"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

注意: 请将 E:\path\to\sms_verify3\server.py 替换为实际的服务器文件路径。

可用工具

此服务器提供以下工具:

estimate_cost

Estimate Cost

端点: POST /send-numeric-verify

技术栈

  • FastMCP: 快速、Pythonic 的 MCP 服务器框架

  • 传输协议: stdio

  • HTTP 客户端: httpx

开发

此服务器由 API-to-MCP 工具自动生成。

版本: 1.0.0

Available Tools

1 tool
estimate_costC

Estimate Cost

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

C2.1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about side effects, permissions, return behavior, or required context, leaving the agent completely in the dark about what happens when the tool is invoked.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

'Estimate Cost' is extremely brief, but this is under-specification rather than effective conciseness. The description omits essential information, so it fails to earn its place as a helpful tool description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though there is an output schema (whose contents are unknown), the description is extremely vague and does not clarify what cost is being estimated, what inputs (if any) are expected, or what the output represents. The tool remains opaque.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the input schema is empty with 100% coverage. According to the rubric, a 0-parameter tool earns a baseline of 4 since there are no parameter semantics to explain or compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Estimate Cost' simply restates the tool name, providing no additional specificity about what kind of cost, what inputs are involved, or what distinguishes this tool from others. It is essentially a tautology, not a clear statement of function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, what prerequisites exist, or what alternatives might be considered. The description offers no contextual information to help an agent decide when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.1
    • First observedestimate_cost
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.5/5.0
Disambiguation5/5

With only one tool, there is no risk of confusing it with others. The tool's purpose is distinct as the only available operation.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern ('estimate_cost'), which is consistent and predictable.

Tool Count2/5

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.

Completeness1/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/sms_verify3'

If you have feedback or need assistance with the MCP directory API, please join our Discord server