Is the Lazymac2x Interactive Api Playground MCP server down?

mcp-registry/io.github.lazymac2x/interactive-api-playground · v2.0.0

healthy
Last checked 2026-10-26 17:08 UTC · handshake 115ms

As of 2026-10-26 17:08 UTC, the Lazymac2x Interactive Api Playground 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,867
outages (90d)
0
tools
5

Cloudflare Workers MCP server: interactive-api-playground

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

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 4 warning(s) across 5 tool(s); ~580 tokens of tool definitions.
Scores higher than 5% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~580 tokens per session — lighter than 90% of servers.
71 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions62
Safety hints4
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (5)

5 of 5 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: api_executor, code_generator, history_tracker, playground_renderer, schema_parser

9 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: api_executor, code_generator

1 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: api_executor

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: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Finteractive-api-playground/fixes

api_executor 1 change 
{
  "name": "api_executor",
  "description": "Execute a live HTTP request to an external URL. Returns real status, headers, and response body. Private IPs are blocked.",
  "inputSchema": {
    "type": "object",
    "required": [
      "method",
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "Full URL (https required)"
      },
      "body": {
        "type": "object"
      },
      "method": {
        "enum": [
          "GET",
          "POST",
          "PUT",
          "PATCH",
          "DELETE",
          "HEAD"
        ],
        "type": "string"
      },
      "headers": {
        "type": "object"
      },
      "timeout_ms": {
        "type": "integer",
        "default": 8000
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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/interactive-api-playground"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/interactive-api-playground"}) 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%2Finteractive-api-playground.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Finteractive-api-playground?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Finteractive-api-playground?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Finteractive-api-playground.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Finteractive-api-playground.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Finteractive-api-playground?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:88477431869f8df8…, first seen 2026-10-17, included at leaf 9348 of 74,323. Version history · verify what your client received.

Tools (5)

Compare: most reliable web servers · most reliable code 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 Interactive Api Playground MCP server down right now?

As of 2026-10-26 17:08 UTC, the Lazymac2x Interactive Api Playground 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 Interactive Api Playground MCP server provide?

Lazymac2x Interactive Api Playground MCP server advertises 5 tools, including api_executor, code_generator, history_tracker, playground_renderer, schema_parser.

How do I install Lazymac2x Interactive Api Playground MCP server?

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

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

Glimind scanned all 5 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 Interactive Api Playground 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