Skip to main content
Glama
BACH-AI-Tools

Ics Ap Apis MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Ics Ap Apis MCP Server

English | 简体中文 | 繁體中文

用于访问 Ics Ap Apis API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: Coda Universal MCP Server

简介

这是一个 MCP 服务器，用于访问 Ics Ap Apis API。

  • PyPI 包名: bach-ics_ap_apis

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-ics_ap_apis

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-ics_ap_apis bach_ics_ap_apis

# 或指定版本
uvx --from bach-ics_ap_apis@latest bach_ics_ap_apis

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

python server.py

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

# 安装
pip install bach-ics_ap_apis

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-ics_ap_apis": {
      "command": "uvx",
      "args": ["--from", "bach-ics_ap_apis", "bach_ics_ap_apis"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

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

{
  "mcpServers": {
    "bach-ics_ap_apis": {
      "command": "uvx",
      "args": ["--from", "bach-ics_ap_apis", "bach_ics_ap_apis"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

api_endpoint

请根据 RapidAPI 页面手动添加端点信息

端点: GET /endpoint

参数:

  • param (string): 参数

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
api_endpointD

请根据 RapidAPI 页面手动添加端点信息

ParametersJSON Schema
NameRequiredDescriptionDefault
paramNo参数

TDQS

D1.8/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 does not mention any side effects, permissions, persistence, reversibility, or return behavior. For a tool that 'adds' information, there is no indication of what changes occur or what the output looks like.

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

Conciseness3/5

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

The description is concise (one sentence) and front-loaded, but it is under-specified. It earns its place only slightly by mentioning RapidAPI as a source, yet the brevity does not compensate for the lack of meaningful content.

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

Completeness1/5

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

For a tool with one optional parameter and no output schema, the description is extremely incomplete. It fails to explain the tool's purpose, how the parameter relates to the endpoint information, what the expected behavior is, or what the user should observe after invocation.

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

Parameters2/5

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

The schema has one optional parameter 'param' with a description '参数' (parameter), which is tautological and provides no real semantics. The tool description adds nothing about how to use the parameter or what values it expects. Although schema coverage is 100%, the content is useless, and the description does not compensate.

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 'Please manually add endpoint information based on the RapidAPI page' uses a specific verb ('add') but the resource ('endpoint information') is vague and the phrase reads more like an instruction to a human than a functional tool description. It does not clearly define what the tool actually does or what constitutes endpoint information, making it barely rise above a tautology.

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 versus alternatives. The phrase 'based on the RapidAPI page' implies a context but does not explicitly state usage scenarios, prerequisites, or exclusions. No alternatives are mentioned.

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.

  1. 1 tool updatev1.0.0
    • First observedapi_endpoint
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'api_endpoint' has a distinct purpose of adding endpoint information from RapidAPI pages.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'api_endpoint' follows a clear noun-based pattern, and there are no other tools to create inconsistency.

Tool Count2/5

A single tool is too few for a server named 'Ics Ap Apis MCP Server', which suggests a broader API management or integration scope. One tool cannot adequately cover operations like listing, updating, or deleting endpoints, making it feel incomplete and thin.

Completeness2/5

The tool set is severely incomplete for an API-related server. It only allows adding endpoints manually, with no tools for retrieving, modifying, deleting, or managing existing endpoints, creating significant gaps that will hinder agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers