Skip to main content
Glama
BACH-AI-Tools

Lorem Ipsum By Api Ninjas

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Lorem Ipsum By Api Ninjas MCP Server

English | 简体中文 | 繁體中文

用于访问 Lorem Ipsum By Api Ninjas API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: Placeholder Image Generator

简介

这是一个 MCP 服务器，用于访问 Lorem Ipsum By Api Ninjas API。

  • PyPI 包名: bach-lorem_ipsum_by_api_ninjas

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-lorem_ipsum_by_api_ninjas

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-lorem_ipsum_by_api_ninjas bach_lorem_ipsum_by_api_ninjas

# 或指定版本
uvx --from bach-lorem_ipsum_by_api_ninjas@latest bach_lorem_ipsum_by_api_ninjas

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

python server.py

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

# 安装
pip install bach-lorem_ipsum_by_api_ninjas

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

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

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

在 Claude Desktop 中使用

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

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

可用工具

此服务器提供以下工具:

v1loremipsum

API Ninjas Lorem Ipsum API endpoint. Returns one or more paragraphs of lorem ipsum placeholder text.

端点: GET /v1/loremipsum

参数:

  • max_length (number): Maximum character length.

  • paragraphs (number): Number of paragraphs to generate. If unset, a default value of 1 will be used.

  • start_with_lorem_ipsum (string): Whether to begin the text with the words "Lorem ipsum". Must be either true or false. If unset, a default value of true will be used.

  • random (string): Whether to randomly generate paragraphs. Must be either true or false. If unset, a default value of true will be used.

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
v1loremipsumC

API Ninjas Lorem Ipsum API endpoint. Returns one or more paragraphs of lorem ipsum placeholder text.

ParametersJSON Schema
NameRequiredDescriptionDefault
max_lengthNoMaximum character length.0
paragraphsNoNumber of paragraphs to generate. If unset, a default value of 1 will be used.0
start_with_lorem_ipsumNoWhether to begin the text with the words \"Lorem ipsum\". Must be either true or false. If unset, a default value of true will be used.
randomNoWhether to randomly generate paragraphs. Must be either true or false. If unset, a default value of true will be used.

TDQS

C2.9/5.0
Behavior2/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 mentions that the tool 'Returns' text, implying a read-only operation, but doesn't cover other important aspects like rate limits, authentication needs, error handling, or response format. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 concise and front-loaded, consisting of two sentences that directly state the tool's function and source. There's no unnecessary information, and it efficiently communicates the core purpose without waste. However, it could be slightly more structured by explicitly mentioning key parameters or output details.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain the return format (e.g., text structure, error responses), rate limits, or other behavioral traits needed for effective use. For a tool with 4 parameters and no structured output information, the description should provide more context to compensate.

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 description adds minimal parameter semantics beyond the input schema, which has 100% coverage. It implies parameters control the output ('one or more paragraphs'), but doesn't explain how parameters like 'max_length' or 'random' affect the result. With high schema coverage, the baseline is 3, as the schema already documents parameters well.

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's purpose: 'Returns one or more paragraphs of lorem ipsum placeholder text.' It specifies the verb ('Returns') and resource ('lorem ipsum placeholder text'), and mentions the API source ('API Ninjas Lorem Ipsum API endpoint'). However, since there are no sibling tools, it doesn't need to differentiate from alternatives, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or specific contexts. It simply states what the tool does without indicating appropriate scenarios or limitations. This lack of usage context reduces its helpfulness for an AI agent.

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

TDQS

B3.2/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined as generating lorem ipsum placeholder text, making it distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'v1loremipsum' follows a single pattern without any deviations or mixing of conventions.

Tool Count2/5

A single tool is too few for most server purposes, as it limits functionality and scope. While it matches the simple domain of generating lorem ipsum text, it feels thin and may not support varied agent workflows effectively.

Completeness3/5

The tool covers the basic function of generating lorem ipsum text, but there are notable gaps. For example, it lacks options for customizing text length, format, or style, which are common in similar APIs, limiting its utility for diverse use cases.

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

  • Faker MCP Server

    kentrino
    A
    license
    Not graded
    quality
    C
    maintenance
    Generates fake data like names, text, internet info, dates, and commerce data using Faker.js, supporting multiple locales and customizable parameters.
    55
    3
    MIT

  • Lorem Ipsum Generator API

    Br0ski777
    A
    license
    Not graded
    quality
    B
    maintenance
    Generates Lorem Ipsum placeholder text with exact count control. Uses x402 micropayments for pay-per-call, no API key required.
    1
    MIT

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/lorem_ipsum_by_api_ninjas'

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