Skip to main content
Glama
dataeyesai

dataeyes-mcp-server

Official
by dataeyesai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

DataEyes MCP Server

PyPI version License

中文版说明

An MCP server that provides web search and page reading capabilities through the DataEyes API.

Tools

  • search — Search the web and get structured results.

  • read — Fetch a web page and extract its content.

Related MCP server: MCP Search & Fetch

Getting Your API Key

Register at shuyanai.com (中国站) or dataeyes.ai (Global) to obtain your API key.

Usage

stdio

For local MCP clients (Cursor, Claude Desktop, etc.) using uvx:

Global

{
  "mcpServers": {
    "dataeyes": {
      "command": "uvx",
      "args": ["dataeyes-mcp-server"],
      "env": {
        "DATAEYES_API_KEY": "your-api-key"
      }
    }
  }
}

中国站

{
  "mcpServers": {
    "dataeyes": {
      "command": "uvx",
      "args": ["dataeyes-mcp-server"],
      "env": {
        "DATAEYES_API_KEY": "your-api-key",
        "DATAEYES_API_BASE_URL": "https://api.shuyanai.com"
      }
    }
  }
}

Environment Variable

Default

Description

DATAEYES_API_KEY

—

API key (required)

DATAEYES_API_BASE_URL

https://api.dataeyes.ai

API base URL

Streamable HTTP

No installation required. Connect directly to the hosted MCP endpoint:

Global

{
  "mcpServers": {
    "dataeyes": {
      "url": "https://mcp.dataeyes.ai/mcp",
      "headers": {
        "Authorization": "Bearer your-api-key"
      }
    }
  }
}

中国站

{
  "mcpServers": {
    "dataeyes": {
      "url": "https://mcp.shuyanai.com/mcp",
      "headers": {
        "Authorization": "Bearer your-api-key"
      }
    }
  }
}

License

This project is licensed under the MIT License.

Available Tools

2 tools
readA
Read-onlyIdempotent

Read and extract content from a web page URL.

Fetches the page, extracts the main content, and returns it in the requested format (markdown by default). Includes metadata such as title, description, and status code.

ParametersJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
metadataNoPage metadata
htmlNoHTML content
markdownNoMarkdown content

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark it as read-only and idempotent. The description adds that it extracts main content and returns metadata, enhancing transparency without contradiction.

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

Conciseness5/5

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

Description is concise (4 lines), front-loaded with the main action, and free of fluff. Every sentence adds value.

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

Completeness5/5

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

Given the rich input schema and output schema (present), the description fully covers the tool's purpose and behavior. No missing elements for agent understanding.

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

Parameters3/5

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

The input schema already provides detailed descriptions for each parameter (url, timeout, format, etc.). The description adds only the default format, providing minimal extra semantic value.

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

Purpose5/5

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

The description clearly states it reads and extracts content from a web page URL, specifies default format (markdown) and metadata returned, distinguishing it from the sibling 'search' tool.

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 on when to use vs the sibling 'search' tool or any prerequisites/limitations. The description does not indicate appropriate contexts or alternatives.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
Disambiguation5/5

The two tools have completely different purposes: one extracts content from a given URL, the other searches for URLs. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools use single-word imperative verbs ('read' and 'search') in lowercase, following a consistent and predictable pattern.

Tool Count3/5

With only two tools, the server is minimal but covers the basic web interaction workflow (search then read). It is on the lower end of the typical range but not inappropriate for a focused purpose.

Completeness4/5

The server provides a complete workflow for finding and reading web content. A minor gap is the lack of tools for batch processing or advanced content extraction, but core needs are met.

Maintenance

ActivityInactive
ResponsivenessSyncing

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/dataeyesai/dataeyes-mcp-server'

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