Nocticas

com.nocticasPublished by nocticas.comOfficial publisherv0.69.0Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Nocticas is a remote browser QA agent that runs pinned end-to-end flows against a URL and returns a verified PASS/FAIL verdict instead of a false green.

What you can do
  • Start a browser QA run against a target URL and poll it for a verdict of passed, failed, error or timeout.
  • Run pinned, deterministic step scripts (gate files) so the same flow is replayed on each check.
  • Probe access control and report verified PASS/FAIL results rather than treating harness errors as passes.
  • Expose the run id and verdict so a CI job or assistant can map the outcome to a build result.
When to use it
Useful when you want an assistant or CI pipeline to gate a preview or staging deployment on real browser checks and block merges on a red verdict. Also fits teams that already author flows in Nocticas and want them replayed deterministically.
Requirements
A remote endpoint at app.nocticas.com over streamable HTTP with OAuth, plus a Nocticas API key sent in the x-nocticas-key header. A pinned gate file (JSON step array) and a target URL are needed for each run. Network access to the Nocticas API.
Before you install
The API key is a secret and should be stored as a credential, not committed. Runs are billed in Nocticas credits, though pinned deterministic runs are said to be free within a monthly allowance. Point gates at staging or preview targets with a dedicated test account and avoid embedding real credentials in gate files. The browser runs on Nocticas servers, so the target URL and flow steps are sent to a third party.

Installation

In SourceWeft

  1. Open Nocticas in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.nocticas%2Fnocticas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nocticas": {
      "type": "http",
      "url": "https://app.nocticas.com/api/mcp"
    }
  }
}

README

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:
yaml
# .github/workflows/nocticas.ymlname: Nocticas E2E gateon: [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".

Source: README.md at commit e47e5aa

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.69.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts