Skip to main content
Glama
DiscreteTom

Mock MCP Server

by DiscreteTom
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Mock MCP Server

PyPI - Version

A mock MCP server for testing MCP client implementations and development workflows.

Support tools, prompts and resources.

Usage

Full CLI Usage

 Usage: mock-mcp-server [OPTIONS]

 Mock MCP Server for testing.

╭─ Options ───────────────────────────────────────────────────────────────────────────╮
│ --transport  [stdio|http|sse|streamable-http]  Transport type [default: stdio]      │
│ --host       TEXT                              Host to bind to [default: 127.0.0.1] │
│ --port       INTEGER                           Port to bind to [default: 8000]      │
│ --version                                      Show version and exit                │
│ --help                                         Show this message and exit.          │
╰─────────────────────────────────────────────────────────────────────────────────────╯

Stdio

Add to your MCP client configuration:

Install MCP Server Add to Kiro

{
  "mcpServers": {
    "mock-stdio": {
      "command": "uvx",
      "args": ["mock-mcp-server"]
    }
  }
}

Streamable HTTP

Start server first:

uvx mock-mcp-server --transport http --host 127.0.0.1 --port 7788

Then configure your MCP client:

Install MCP Server Add to Kiro

{
  "mcpServers": {
    "mock-streamable-http": {
      "url": "http://127.0.0.1:7788/mcp"
    }
  }
}

SSE

Start server first:

uvx mock-mcp-server --transport sse --host 127.0.0.1 --port 7789

Then configure your MCP client:

Install MCP Server Add to Kiro

{
  "mcpServers": {
    "mock-sse": {
      "url": "http://127.0.0.1:7789/sse"
    }
  }
}

Related MCP server: http-mcp-server

CHANGELOG

Available Tools

1 tool
mock_echoB

Echo back the provided message.

ParametersJSON Schema
NameRequiredDescriptionDefault
messageYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.1/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. It states the tool 'echoes back' the message, which implies a read-only or non-destructive operation, but doesn't disclose details like whether it modifies the input, requires authentication, has rate limits, or what the output format is. The description is minimal and lacks behavioral context beyond the basic action.

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 a single, efficient sentence with no wasted words, clearly front-loaded with the core action. It's appropriately sized for a simple tool, making it easy to scan and understand quickly.

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?

Given the tool's low complexity (1 parameter, no annotations, but has an output schema), the description is complete enough for basic use. The output schema likely handles return values, so the description doesn't need to explain them. However, it could benefit from more behavioral context, but for this simple case, it's adequate.

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 1 parameter with 0% description coverage, so the schema provides no semantic details. The description adds meaning by specifying that the parameter is a 'message' to be echoed back, which clarifies its purpose beyond the schema's type definition. However, it doesn't detail constraints or examples, but with only 1 parameter, this is sufficient for baseline understanding.

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

Purpose3/5

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

The description 'Echo back the provided message' states what the tool does with a clear verb ('echo back') and resource ('message'), but it's somewhat vague as 'echo' could imply various behaviors like returning the exact input or processing it. With no sibling tools, differentiation isn't needed, but the purpose could be more specific about the exact behavior.

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, as there are no sibling tools mentioned, but it also lacks context on prerequisites or typical use cases. It's a basic tool with implied usage for testing or debugging, but no explicit guidelines are given.

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 update
    • First observedmock_echo
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 confusion or overlap between tools. The tool 'mock_echo' has a single, clear purpose of echoing messages, making it perfectly distinct.

Naming Consistency5/5

The tool name 'mock_echo' follows a consistent verb_noun pattern (echo as the verb, implied message as the noun). Since there is only one tool, naming consistency is inherently perfect with no deviations to assess.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and suggests a trivial or incomplete scope. For a server named 'Mock MCP Server', which implies broader mocking capabilities, one tool feels insufficient and under-scoped.

Completeness2/5

The server's purpose is unclear from the name 'Mock MCP Server', but a single echo tool suggests severe incompleteness. It lacks coverage for common mocking operations like simulating data, errors, or varied responses, creating significant gaps that could cause agent failures in typical 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

  • Basic MCP Server

    gurdasnijor
    A
    license
    Not graded
    quality
    D
    maintenance
    A minimal demonstration server showcasing MCP protocol capabilities including tools, resources, and prompts with basic examples like hello world functionality.
    2
    MIT

  • http-mcp-server

    agarcia-seidor
    A
    license
    Not graded
    quality
    B
    maintenance
    Mock HTTP server implementing MCP (Model Context Protocol) with streamable HTTP transport, health endpoint, and example tools like echo and time.
    225
    MIT

  • mcp-toy

    xiangshiyin
    A
    license
    Not graded
    quality
    D
    maintenance
    A toy MCP server for exploring Model Context Protocol capabilities, including resources, tools, and prompts.
    Apache 2.0

  • mcp-mock

    vibeglitch
    A
    license
    Not graded
    quality
    B
    maintenance
    A lightweight mock MCP server for local testing and resilience experiments, providing predictable tool responses with simulated latency and errors.
    1
    MIT

Appeared in Searches

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/DiscreteTom/mock-mcp-server'

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