io.github.ligafew/apcs-public-mcp-gateway
REMOTE · APCS-PUBLIC-MCP-GATEWAY.ITSNOTEVENBUTTER03.WORKERS.DEV
Fresh scoped PyPI install and import verification on Linux x86_64 and CPython 3.13.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 7 Sep 2026.
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Superseded by io.github.ligafew/apcs-pypi-package-verification for task-legible discovery; same APCS verification service.
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (2)
- HTTPS
- Transport
Checks we could not complete (9)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Sept 26 −2
- Stability: 0.07 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “verify_python_package” was removed ▼ security
- The server changed its declared name: apcs-empirical-python-verification → python-package-runtime-test security
- New tool “test_python_package_runtime” functional
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 14 Sept 2026 · Probed https://apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev/mcp | Unreachable | ||
| http (plaintext) | http://apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
test_python_package_runtime Verify PyPI Package Install and Import ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| import_targets | array | – | Optional Python import names to check after installation, for example ["packaging"]; omit when no explicit import check is needed. |
| requirement | string | yes | One public-PyPI distribution requirement, for example packaging==24.2; do not provide a URL, VCS reference, local path, or alternate index. |
No output schema declared.
No examples provided.
How do I install the io.github.ligafew/apcs-public-mcp-gateway server?
io.github.ligafew/apcs-public-mcp-gateway is a hosted endpoint at https://apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev
claude mcp add --transport http ligafew-apcs-public-mcp-gateway 'https://apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev/mcp'
What is the io.github.ligafew/apcs-public-mcp-gateway server?
io.github.ligafew/apcs-public-mcp-gateway is listed in the public MCP registry as io.github.ligafew/apcs-public-mcp-gateway. Fresh scoped PyPI install and import verification on Linux x86_64 and CPython 3.13. This page covers its hosted endpoint (https://apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev/mcp).
Is the io.github.ligafew/apcs-public-mcp-gateway server safe to use?
io.github.ligafew/apcs-public-mcp-gateway scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ligafew/apcs-public-mcp-gateway server expose?
io.github.ligafew/apcs-public-mcp-gateway exposes 1 tool: test_python_package_runtime. Their descriptions and schemas cost roughly 162 tokens of context every time the server is loaded.
Does the io.github.ligafew/apcs-public-mcp-gateway server require authentication?
Its publisher declares no required credentials for io.github.ligafew/apcs-public-mcp-gateway. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.ligafew/apcs-public-mcp-gateway server still maintained?
io.github.ligafew/apcs-public-mcp-gateway is marked deprecated in the MCP registry. We last reached this channel on 7 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.ligafew/apcs-public-mcp-gateway server?
VerifyMCP ran 2 checks on io.github.ligafew/apcs-public-mcp-gateway, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about io.github.ligafew/apcs-public-mcp-gateway: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.