English Français العربية

Nocticas

Registre officiel Recherche et web

Browser QA agent that won't return a false green: verified PASS/FAIL + access-control probing.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http nocticas 'https://app.nocticas.com/api/mcp' --header 'x-nocticas-key: <Your Nocticas API key. Get a free 150-credit key (no card) at https://app.nocticas.com>'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "nocticas": {
            "type": "http",
            "url": "https://app.nocticas.com/api/mcp",
            "headers": {
                "x-nocticas-key": "<Your Nocticas API key. Get a free 150-credit key (no card) at https://app.nocticas.com>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Nocticas E2E Gate — GitHub Action
  2. Quickstart
  3. Inputs
  4. Outputs
  5. The gate file
  6. Cost
  7. Other CI systems (the recipe)

Nocticas E2E Gate — GitHub Action

Run a pinned Nocticas gate against a target URL on every push/PR, and fail the build on a red verdict. The browser runs on Nocticas's servers — this Action is a thin client that starts the run, polls for the verdict, and maps it to an exit code. No false greens: a harness error is never treated as a pass.

Quickstart

  1. Author + pin a flow in Nocticas (agentic run → pin → export the deterministic step script as JSON).
  2. Commit the gate to your repo, e.g. .nocticas/checkout-flow.json.
  3. Add your key as a repo secret: NOCTICAS_API_KEY.
  4. Add the workflow:
# .github/workflows/nocticas.yml
name: Nocticas E2E gate
on: [pull_request, workflow_dispatch]
jobs:
  verify:
    runs-on: ubuntu-latest          # standard runner = free on public repos
    steps:
      - uses: actions/checkout@v4   # so the gate file is available
      - uses: Low-Latency-Labs/nocticas-action@v1
        with:
          api-key: ${{ secrets.NOCTICAS_API_KEY }}
          gate: .nocticas/checkout-flow.json
          target: ${{ vars.PREVIEW_URL }}   # your deployed preview/staging URL

A red verdict fails the job → blocks the PR/merge.

Inputs

InputRequiredDefaultDescription
api-keyyes—Your Nocticas API key (store as a secret).
gateyes—Path to the pinned gate JSON (array of deterministic steps) in your repo.
targetyes—URL to test (e.g. the PR's preview deploy).
api-basenohttps://app.nocticas.com/apiNocticas API base.
timeout-secondsno300Max wait for a verdict.
poll-secondsno3Poll interval.
fail-on-errornotrueTreat a harness error (not a test fail) as a build failure. An unverified run is never a pass.

Outputs

OutputDescription
run-idThe Nocticas run id (link it in your logs).
verdictpassed \failed \error \timeout.

The gate file

A JSON array of deterministic steps — exactly what Nocticas produces when you pin a passing run. Example in examples/gate.example.json. Keeping it in your repo means your E2E test is version-controlled alongside the code it guards.

Don't commit real credentials. Point the gate at a staging/preview target and use a dedicated test account; Nocticas's built-in test inbox handles OTP/magic-link logins so you don't need to embed secrets in the gate.

Cost

  • Publishing this Action: free (public repo, no paid plan).
  • Running it (your customers): free on public repos with standard runners; within the monthly free-minutes allowance on private repos. It's a single thin job — seconds of runner time.
  • The browser run: billed in Nocticas credits — and deterministic/pinned runs are free within your monthly allowance, so gating every push typically costs nothing in credits.

Other CI systems (the recipe)

Not on GitHub? The same start → poll → exit logic is a portable script — see recipe.sh and examples/gitlab-ci.example.yml. The contract is just JSON over HTTP:

POST {api-base}/runs   { "mode":"deterministic", "target": "...", "script": [ ...gate... ] }   → { "id": "..." }
GET  {api-base}/runs/{id}                                                                       → { "status": "passed|failed|error|..." }

Header: x-nocticas-key: <key>. Exit non-zero unless status == "passed".

Questions fréquentes

Qu'est-ce que Nocticas ?

Browser QA agent that won't return a false green: verified PASS/FAIL + access-control probing.

Comment installer Nocticas ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http nocticas 'https://app.nocticas.com/api/mcp' --header 'x-nocticas-key: <Your Nocticas API key. Get a free 150-credit key (no card) at https://app.nocticas.com>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Nocticas ?

Oui. Il attend x-nocticas-key, à renseigner dans sa configuration.

Nocticas est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Nocticas ?

Il est publié par Low-Latency-Labs. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.