Skip to main content
Glama
BACH-AI-Tools

Moz Da Pa1 MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

Moz Da Pa1 MCP Server

English | 简体中文 | 繁體中文

用于访问 Moz Da Pa1 API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: Google Search Console MCP Server

简介

这是一个 MCP 服务器，用于访问 Moz Da Pa1 API。

  • PyPI 包名: bach-moz_da_pa1

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-moz_da_pa1

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-moz_da_pa1 bach_moz_da_pa1

# 或指定版本
uvx --from bach-moz_da_pa1@latest bach_moz_da_pa1

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

python server.py

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

# 安装
pip install bach-moz_da_pa1

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

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

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

在 Claude Desktop 中使用

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

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

可用工具

此服务器提供以下工具:

getdapa

Our API provides real data from Moz. Domain Authority, Page Authority, External nofollow urls to url, External urls to url and Spam Score.

端点: POST /v1/getDaPa

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
getdapaB

Our API provides real data from Moz. Domain Authority, Page Authority, External nofollow urls to url, External urls to url and Spam Score.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3/5.0
Behavior2/5

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

The description does not disclose behavioral traits beyond stating it provides data. No annotations are present, so the agent must infer behavior. There is no mention of side effects, authentication, or rate limits.

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

Conciseness4/5

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

The description is a single sentence that is concise and to the point. It could benefit from better structuring, but it avoids unnecessary verbosity.

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?

Given no parameters and no output schema, the description should explain what triggers the data retrieval and what the output looks like. It only lists data types without providing operational context, leaving the agent uninformed.

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 input schema has zero parameters, and schema coverage is 100%. The description adds no parameter information because none exist, but the baseline score of 4 is appropriate for a parameterless tool.

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

Purpose4/5

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

The description clearly states the tool provides real data from Moz and lists specific metrics (Domain Authority, Page Authority, etc.), indicating its purpose. However, it lacks explicit verb usage and does not mention any required input, which could be confusing for an agent.

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?

No guidance is provided on when to use this tool or when to avoid it. There are no sibling tools for differentiation, but the description gives no context for appropriate usage scenarios.

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.0
    • First observedgetdapa
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possible ambiguity between tools. The single tool has a clearly distinct purpose.

Naming Consistency5/5

The server has a single tool, so naming consistency is trivially maintained. The name 'getdapa' follows a verb_noun pattern.

Tool Count3/5

The server has only one tool, which feels thin for a service that likely requires operations for different metrics or parameters. It is borderline appropriate.

Completeness1/5

The tool surface is severely incomplete. The domain of Moz data retrieval typically requires multiple endpoints or operations (e.g., getting specific metrics, filtering by URL), but only one tool is provided, limiting flexibility.

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

  • Google Search Console MCP

    bwengr
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables querying Google Search Console data including rankings, clicks, and impressions for websites. Provides tools for analyzing search performance, top queries, page metrics, and ranking changes.
    MIT

  • Haloscan MCP Server

    occirank
    A
    license
    C
    quality
    D
    maintenance
    Enables SEO analysis by interacting with the Haloscan API, providing keyword research, site explorer, and SERP comparison tools.
    33
    73
    3
    MIT

  • MCP DataForSEO Server

    kevinmaqueda
    F
    license
    B
    quality
    C
    maintenance
    Enables SEO analysis and data retrieval through DataForSEO API, including keyword research, backlinks, competitor analysis, and on-page audits.
    24
    -

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/bachai-moz-da-pa1'

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