Sentiment By Api Ninjas MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Sentiment By Api Ninjas MCP Serveranalyze the sentiment of this customer review: 'The product arrived quickly and works perfectly, but the packaging was damaged.'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sentiment By Api Ninjas MCP Server
用于访问 Sentiment By Api Ninjas API 的 MCP 服务器。
🚀 使用 EMCP 平台快速体验
EMCP 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!
快速开始:
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场,浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器(
bach-sentiment_by_api_ninjas)🎉 点击 "安装 MCP" 按钮
✅ 完成!即可在您的应用中使用
EMCP 平台优势:
✨ 零配置:无需手动编辑配置文件
🎨 可视化管理:图形界面轻松管理所有 MCP 服务器
🔐 安全可靠:统一管理 API 密钥和认证信息
🚀 一键安装:MCP 广场提供丰富的服务器选择
📊 使用统计:实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅!
Related MCP server: Nutrition By Api Ninjas MCP Server
简介
这是一个 MCP 服务器,用于访问 Sentiment By Api Ninjas API。
PyPI 包名:
bach-sentiment_by_api_ninjas版本: 1.0.0
传输协议: stdio
安装
从 PyPI 安装:
pip install bach-sentiment_by_api_ninjas从源码安装:
pip install -e .运行
方式 1: 使用 uvx(推荐,无需安装)
# 运行(uvx 会自动安装并运行)
uvx --from bach-sentiment_by_api_ninjas bach_sentiment_by_api_ninjas
# 或指定版本
uvx --from bach-sentiment_by_api_ninjas@latest bach_sentiment_by_api_ninjas方式 2: 直接运行(开发模式)
python server.py方式 3: 安装后作为命令运行
# 安装
pip install bach-sentiment_by_api_ninjas
# 运行(命令名使用下划线)
bach_sentiment_by_api_ninjas配置
API 认证
此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"环境变量
变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
在 Cursor 中使用
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-sentiment_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-sentiment_by_api_ninjas", "bach_sentiment_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}在 Claude Desktop 中使用
编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-sentiment_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-sentiment_by_api_ninjas", "bach_sentiment_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}可用工具
此服务器提供以下工具:
v1sentiment
Returns sentiment analysis score and overall sentiment for a given block of text.
端点: GET /v1/sentiment
参数:
text(string) 必需: query text for sentiment analysis. Maximum 2000 characters.
技术栈
传输协议: stdio
HTTP 客户端: httpx
许可证
MIT License - 详见 LICENSE 文件。
开发
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
Available Tools
1 toolv1sentimentB
Returns sentiment analysis score and overall sentiment for a given block of text.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | query text for sentiment analysis. Maximum 2000 characters. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden. It only states that the tool returns a score and overall sentiment, but fails to describe the score range, output format, or any behavioral traits like limits or side effects beyond the input schema's max length.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words. It is front-loaded and to the point, achieving maximum conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one parameter and no output schema. The description covers the basic purpose but lacks details about the output structure (e.g., score range, sentiment categories). It is complete enough for a minimal viable description but has gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter 'text', which includes a clear description. The tool description adds minimal extra context, essentially restating the schema. Baseline 3 is appropriate as the schema already provides adequate info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Returns' and clearly names the resource: sentiment analysis score and overall sentiment for text. It precisely states what the tool does without ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 vs. alternatives or when not to use it. There is no mention of prerequisites, context, or exclusions.
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 tool update
v1.0.0- First observed
v1sentiment
TDQS
Only one tool exists, so there is no risk of confusion with other tools.
With a single tool, naming consistency is inherently perfect.
One tool for a sentiment analysis server is minimal but acceptable if the scope is narrow; however, it feels thin for typical use.
The tool covers the core function of sentiment analysis, but lacks supplementary features like batch processing or multiple models, leaving some gaps.
Maintenance
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
Remote MCP server that returns sentiment analysis results from SentinelScan API.
Sentiment, toxicity, entity extraction, PII, translation, summary, QA, fraud scoring, safety audit.
Toxicity, sentiment, NER, PII detection, and language identification tools
Text Intelligence delivers robust NLP capabilities without the hassle of authentication or
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides access to Sentiment402 market sentiment data for global markets, crypto, TradFi, and specific assets, with built-in support for x402 micropayment protocol when API responses require payment.MIT
- AlicenseCqualityDmaintenanceProvides access to the Nutrition By Api Ninjas API to extract detailed nutritional information from natural language food queries. It enables users to retrieve data such as calories, vitamins, and macros from text descriptions of meals.1MIT
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade sentiment analysis tool for AI agents, enabling sentiment labeling, keyword extraction, and batch analysis via MCP.1MIT
- AlicenseNot gradedqualityCmaintenanceWraps the API Ninjas multi-endpoint data API, enabling AI agents to access a wide range of data sources through natural language queries.16MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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-sentiment-by-api-ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server