Skip to main content
Glama
BACH-AI-Tools

Biztoc MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Biztoc MCP Server

English | 简体中文 | 繁體中文

用于访问 Biztoc API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: Weather and Stock Information MCP Server

简介

这是一个 MCP 服务器，用于访问 Biztoc API。

  • PyPI 包名: bach-biztoc

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-biztoc

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-biztoc bach_biztoc

# 或指定版本
uvx --from bach-biztoc@latest bach_biztoc

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

python server.py

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

# 安装
pip install bach-biztoc

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

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

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

在 Claude Desktop 中使用

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

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

可用工具

此服务器提供以下工具:

news__source

Get the latest news stories for the respective {source_id} in chronological order.

端点: GET /news/source/{source_id}

参数:

  • source_id (string) 必需: Example value: bbc

sources

Lists all currently available {source_id}s. Equivalent of news blocks on biztoc.com. Note that certain proprietary blocks like Twitter or Stock Tickers are not available.

端点: GET /sources

news__topics

Get trending topic clusters and their respective stories, ordered by a proprietary popularity algorithm. Akin to the /topics view on biztoc.com. The topics and stories will change every hour.

端点: GET /news/topics

search

Search across the entire news index from the last 14 days. Note that no search operators are supported via the API so all provided terms are considered required.

端点: GET /search

参数:

  • q (string) 必需: Example value: apple

news__latest

Get the latest news stories in chronological order, across all pages. Akin to the /wire view on biztoc.com.

端点: GET /news/latest

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

5 tools
news_latestA

Get the latest news stories in chronological order, across all pages. Akin to the /wire view on biztoc.com.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It mentions 'across all pages' implying handling of pagination, but it does not disclose rate limits, data volume, or whether results are limited to recent stories.

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?

Two concise sentences with front-loaded purpose. Every word contributes meaning, and the analogy is efficient.

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?

No output schema exists, so the description should explain return format. It does not specify what fields each story contains (e.g., title, date, content), relying on an external analogy that may not be machine-interpretable.

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?

There are no parameters, and schema coverage is 100%. The description adds no param info, but by baseline for 0 params, a score of 4 is appropriate.

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 retrieves the latest news stories in chronological order, with 'across all pages' differentiating it from potentially paginated siblings. The analogy to '/wire view' on biztoc.com adds clarity.

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

Usage Guidelines3/5

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

The description indicates when to use (to get latest news) but lacks explicit guidance on when not to use or alternatives among siblings. The analogy helps but does not fully delineate use cases.

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

news_sourceB

Get the latest news stories for the respective {source_id} in chronological order.

ParametersJSON Schema
NameRequiredDescriptionDefault
source_idYesExample value: bbc

TDQS

B3.1/5.0
Behavior2/5

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

No annotations, so description bears full burden. Only states 'latest' and 'chronological' but omits pagination, error handling, read-only nature, or what happens with invalid source_id.

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?

Single sentence, front-loaded with 'Get', no extraneous words. Highly concise and to the point.

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?

No output schema, no annotations, and missing details on output format, valid source_ids, pagination, or how to obtain source_ids from sibling tool 'sources'. Incomplete for practical use.

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?

Schema only has example 'bbc'; description uses placeholder but doesn't define source_id or list valid sources. Adds minimal meaning beyond the schema.

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?

Description clearly states it gets latest news stories for a given source_id in chronological order, specifying verb, resource, and ordering, distinguishing it from siblings like news_latest (maybe cross-source) or news_topics.

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 this tool vs alternatives like news_latest, news_topics, or search. Does not mention prerequisites or when not to use.

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

news_topicsA

Get trending topic clusters and their respective stories, ordered by a proprietary popularity algorithm. Akin to the /topics view on biztoc.com. The topics and stories will change every hour.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.8/5.0
Behavior3/5

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

Discloses ordering by proprietary algorithm and hourly updates. With no annotations, this provides some behavioral context but no mention of read-only nature or side effects.

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?

Three sentences, all valuable. First states purpose, second gives analogy, third explains update frequency. No fluff.

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?

For a tool with no parameters and no output schema, the description fully explains what it returns, ordering, and update cadence. Complete.

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?

No parameters, so description adds no param info. Baseline score of 4 as per guidelines, and description adds context about algorithm and update frequency.

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?

Clearly states it gets trending topic clusters and stories, ordered by a proprietary algorithm. Mentions analogy to /topics view, distinguishing it from siblings like news_latest or search.

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

Usage Guidelines3/5

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

Implies usage for trending topics via analogy to /topics view, but no explicit when-to-use or when-not-to-use versus siblings like news_latest or search.

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

sourcesA

Lists all currently available {source_id}s. Equivalent of news blocks on biztoc.com. Note that certain proprietary blocks like Twitter or Stock Tickers are not available.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the transparency burden. It discloses that certain sources (proprietary blocks like Twitter/Stock Tickers) are not included. However, it does not detail output format, pagination, or performance characteristics.

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?

The description is two sentences with no extraneous information. It is front-loaded with the core purpose and followed by a notable limitation.

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

Completeness4/5

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

For a parameterless tool with no output schema, the description covers the basic functionality and a key limitation. It could be enhanced by specifying the output type (e.g., list of strings) but overall is sufficient.

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 no parameters, so the description's mention of the output (available {source_id}s) adds semantic value. The baseline is 4 due to 100% schema coverage.

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 the tool's action ('Lists all currently available {source_id}s') and provides a real-world analogy ('Equivalent of news blocks on biztoc.com'). It distinguishes from siblings by focusing on listing all source IDs rather than a specific source or topics.

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

Usage Guidelines3/5

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

The description does not explicitly guide when to use this tool versus its siblings (news_latest, news_source, etc.). It mentions a limitation about proprietary blocks not being available, which is useful, but lacks direct comparison to alternatives.

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. 5 tool updatesv1.0.0
    • First observednews_latest
    • First observednews_source
    • First observednews_topics
    • First observedsearch
    • First observedsources
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect of the news domain: latest stories, stories by source, trending topics, search, and listing sources. There is no functional overlap.

Naming Consistency4/5

Tool names follow a consistent lowercase_underscore pattern, but not all share the same prefix: three use 'news_' while two are standalone nouns ('search', 'sources'). This is a minor inconsistency.

Tool Count5/5

Five tools cover the core functionalities of a news aggregator without being excessive or sparse. Each tool serves a clear purpose.

Completeness4/5

The set covers common news operations: fetching latest, filtering by source, trending topics, search, and source listing. A minor gap is the lack of a tool to retrieve a specific story by ID.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Tavily Search MCP Agent

    arben-adm
    A
    license
    Not graded
    quality
    D
    maintenance
    This MCP server performs multi-topic searches in business, news, finance, and politics using the Tavily API, providing high-quality sources and intelligent summaries.
    1
    MIT

  • NewsBreak Ads MCP Server

    geopopos
    A
    license
    A
    quality
    D
    maintenance
    MCP server for the NewsBreak Business API that enables analytics, reporting, and campaign management through tools and resources.
    6
    1
    MIT

  • whatshot-mcp

    RayLLLU
    F
    license
    A
    quality
    C
    maintenance
    MCP server for WhatsHot API providing read-only access to aggregated hotlists, news flashes, and gold prices, with tools to fetch current data, query history, search, and get trends.
    7
    1
    -