Is the Lazymac2x Api Mock MCP server down?

mcp-registry/io.github.lazymac2x/api-mock-server · v1.1.0

healthy
Last checked 2026-10-22 23:37 UTC · handshake 262ms

As of 2026-10-22 23:37 UTC, the Lazymac2x Api Mock MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,289
outages (90d)
0
tools
6

Cloudflare Workers MCP server: api-mock-server

Install Lazymac2x Api Mock MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http lazymac2x-api-mock-mcp-server https://api.lazy-mac.com/api-mock-server/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "lazymac2x-api-mock-mcp-server": {
      "type": "http",
      "url": "https://api.lazy-mac.com/api-mock-server/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (74/100)

C (74/100): 0 error(s), 4 warning(s) across 6 tool(s); ~479 tokens of tool definitions.
Scores higher than 9% of 15,575 MCP servers Glimind has audited.
Its tool list costs an agent ~479 tokens per session — lighter than 95% of servers.
74 → 74 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions82
Safety hints0
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (5)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: create_mock, delete_mock, get_mock_endpoint, get_mock_logs, list_mocks and 1 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_mock, delete_mock, update_mock_response

1 tool(s) have descriptions under 20 characters.

Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →

Tools: delete_mock

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Fapi-mock-server/fixes

create_mock 1 change
{
  "name": "create_mock",
  "description": "OpenAPI/Swagger 스펙(JSON)으로 목업 API 서버를 생성합니다. 즉시 사용 가능한 엔드포인트 URL을 반환합니다.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name",
      "spec"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "목업 서버 이름"
      },
      "spec": {
        "type": "object",
        "description": "OpenAPI 3.0 또는 Swagger 2.0 스펙 JSON 객체"
      },
      "description": {
        "type": "string",
        "description": "목업 서버 설명 (선택)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
delete_mock 1 change
{
  "name": "delete_mock",
  "description": "목업 서버를 삭제합니다.",
  "inputSchema": {
    "type": "object",
    "required": [
      "mock_id"
    ],
    "properties": {
      "mock_id": {
        "type": "string",
        "description": "삭제할 목업 서버 ID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
get_mock_endpoint 1 change
{
  "name": "get_mock_endpoint",
  "description": "특정 목업 서버의 상세 정보와 엔드포인트 목록을 반환합니다.",
  "inputSchema": {
    "type": "object",
    "required": [
      "mock_id"
    ],
    "properties": {
      "mock_id": {
        "type": "string",
        "description": "목업 서버 ID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lazymac2x/api-mock-server"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/api-mock-server"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-mock-server.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-mock-server?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-mock-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-mock-server.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-mock-server.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-mock-server?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a74c2cbd4c6c2ef5…, first seen 2026-10-17, included at leaf 5524 of 48,787. Version history · verify what your client received.

Tools (6)

Compare: most reliable devops servers · most reliable data servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Lazymac2x Api Mock MCP server down right now?

As of 2026-10-22 23:37 UTC, the Lazymac2x Api Mock MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Lazymac2x Api Mock MCP server provide?

Lazymac2x Api Mock MCP server advertises 6 tools, including create_mock, delete_mock, get_mock_endpoint, get_mock_logs, list_mocks.

How do I install Lazymac2x Api Mock MCP server?

Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/api-mock-server/mcp

Is the Lazymac2x Api Mock MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Lazymac2x Api Mock MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve