MCP.Market

ultra-e2e-test tasks MCP server

by hynix666·io.github.hynix666/ultra-e2e-test·v0.1.1
No reviews yet

List, create and move tasks through todo, in progress and done.

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed ultra-e2e-test tasks yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

ultra-e2e-test tasks tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How ultra-e2e-test tasks compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 60% of 1,299 Productivity servers

Install ultra-e2e-test tasks in Claude Code, Cursor or VS Code

claude mcp add ultra-e2e-test -- docker run -i --rm ghcr.io/hynix666/ultra-e2e-test-mcp-server:0.1.1
Add to Cursor

What the publisher says

From the ultra-e2e-test tasks repository's README, as published. We do not edit it. Read it on GitHub

ultra-e2e-test

The end-to-end test for TEMPLATE1: a project generated with every feature, then released and updated through each template release, so that init, template-update, releases and MCP publishing are proven on a real repository rather than only in the template's own CI.

Getting started

You need:

  • Node 24 (.node-version), for the scripts and every Node module.
  • Go 1.26 (services/api-go/go.mod), and golangci-lint for the complete local check; without it, verify.mjs reports golangci-lint as skipped, and CI still runs it.
  • Python 3.13 or newer and uv (services/api-py/.python-version), which installs the rest.
  • The GitHub CLI, only to apply repository settings with configure-github.mjs.

Each toolchain version is pinned once, in the file named beside it above, so there is no .tool-versions to keep in step; mise and asdf can read those files directly.

  1. Install the dependencies of every module present:
node scripts/setup.mjs
  1. Run the checks every CI job runs on the code:
node scripts/verify.mjs             # everything
   node scripts/verify.mjs <module>    # the chassis plus the named modules only

It runs each module's own checks and tests, and the API contract against every task service present. A check it cannot run is reported as skipped, never as passed. A few checks run only in CI, because they need a container engine, a network service or a CI-only tool: actionlint and zizmor on the workflows, npm audit signatures, building and starting each container image, and the report-only scans in security.yml.

  1. Start what you are working on. Each module's entry under What's here names the command that starts it.

What's here

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

ultra-e2e-test tasks: common questions

Is ultra-e2e-test tasks MCP server safe?
Mostly: it is graded B (83/100). Read the ultra-e2e-test tasks safety report
How do I install ultra-e2e-test tasks?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does ultra-e2e-test tasks need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is ultra-e2e-test tasks maintained?
The last commit was 35 days ago (2026-09-29). The latest release is v0.1.1.