Is the Ligafew Python Package Runtime Test MCP server down?

mcp-registry/io.github.ligafew/python-package-runtime-test · v1.0.0

healthy
Last checked 2026-10-27 05:10 UTC · handshake 275ms

As of 2026-10-27 05:10 UTC, the Ligafew Python Package Runtime Test 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. It had 1 outage in 90 days, with a median recovery of 26.1 hours.

uptime (30d checks)
100%
checks observed
4,964
outages (90d)
1
tools
1

Hosted Python sandbox for package runtime verification: pip install and usable-import evidence.

Point your MCP client at this streamable-http endpoint: https://apcs-public-mcp-gateway.apcs-mcp.workers.dev/mcp/python-package-runtime-test

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 2 warning(s) across 1 tool(s); ~288 tokens of tool definitions.
Scores higher than 33% of 15,782 MCP servers Glimind has audited.
Its tool list costs an agent ~288 tokens per session — lighter than 99% of servers.
79 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

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: test_python_package_runtime

1 of 1 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: test_python_package_runtime

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. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ligafew%2Fpython-package-runtime-test/fixes

test_python_package_runtime 1 change 
{
  "name": "test_python_package_runtime",
  "description": "Test a specific Python package/version on a supported Python/Linux target runtime using empirical execution. Returns scoped install evidence, usable-import evidence when requested, and a scoped result/receipt. Supported boundary: public PyPI on Linux x86_64 / CPython 3.13. This is not generic package advice, security verification, arbitrary Python execution, broad compatibility testing, feature behavior testing, or application integration testing.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "requirement"
    ],
    "properties": {
      "requirement": {
        "type": "string",
        "description": "One public-PyPI distribution requirement, for example packaging==24.2; do not provide a URL, VCS reference, local path, or alternate index."
      },
      "import_targets": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Optional Python import names to check after installation, for example [\"packaging\"]; omit when no explicit import check is needed."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Verify PyPI Package Install and Import"
}

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.ligafew/python-package-runtime-test"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.ligafew/python-package-runtime-test"}) 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.ligafew%2Fpython-package-runtime-test.svg)](https://glimind.com/server/mcp-registry%2Fio.github.ligafew%2Fpython-package-runtime-test?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ligafew%2Fpython-package-runtime-test?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ligafew%2Fpython-package-runtime-test.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ligafew%2Fpython-package-runtime-test.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.ligafew%2Fpython-package-runtime-test?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:d0223d3fde434ec1…, first seen 2026-10-17, included at leaf 6090 of 77,531. Version history · verify what your client received.

Tools (1)

Compare: most reliable code 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 Ligafew Python Package Runtime Test MCP server down right now?

As of 2026-10-27 05:10 UTC, the Ligafew Python Package Runtime Test 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. It had 1 outage in 90 days, with a median recovery of 26.1 hours.

How many tools does Ligafew Python Package Runtime Test MCP server provide?

Ligafew Python Package Runtime Test MCP server advertises 1 tool, including test_python_package_runtime.

How do I install Ligafew Python Package Runtime Test MCP server?

Point your MCP client at this streamable-http endpoint: https://apcs-public-mcp-gateway.apcs-mcp.workers.dev/mcp/python-package-runtime-test

Is the Ligafew Python Package Runtime Test MCP server safe to connect to an AI agent?

Glimind scanned all 1 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 Ligafew Python Package Runtime Test 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