batchwatch-mcp

MCPcommunity

v0.1.1io.github.batchwatchMITUpdated 1mo agonpm GitHub

Ask batchwatch whether to batch a job and get the real measured queue evidence, not a guess.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1mo agoLast update

Package

Authorio.github.batchwatch

LicenseMIT

Version0.1.1

Sourcenpm+mcp-registry

npmbatchwatch-mcp

GitHubbatchwatch/client

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface6 tools · none privileged

Security scan✓ Cleanv0.1.1 · todayHow well does this scan work?

EvalsNone

IndexedAug 31, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged

Statically extracted from the published packagev0.1.1 · 9h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

should_i_batchThe verdict: given a model and your own max_wait, does the batch queue currently honour it?

The verdict: given a model and your own max_wait, does the batch queue currently honour it?

No input schema was published for this tool.

estimate_batchtimeHow long is MY job likely to wait? Returns the batch-wait distribution (p50/p90) for the model,

How long is MY job likely to wait? Returns the batch-wait distribution (p50/p90) for the model,

No input schema was published for this tool.

conditionsCurrent queue conditions for a model right now vs its recent norm — "is it me or them?".

Current queue conditions for a model right now vs its recent norm — "is it me or them?".

No input schema was published for this tool.

distributionThe full measured wait distribution for a model + mode over a window. The raw evidence behind

The full measured wait distribution for a model + mode over a window. The raw evidence behind

No input schema was published for this tool.

coverageWhich provider+model combinations batchwatch currently has data for, and how answerable each is

Which provider+model combinations batchwatch currently has data for, and how answerable each is

No input schema was published for this tool.

waitThe public "is the queue moving now?" reading for a model (delayed without a key). Lighter than

The public "is the queue moving now?" reading for a model (delayed without a key). Lighter than

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Ask batchwatch whether to batch a job and get the real measured queue evidence, not a guess.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

6 tools · none privileged · observed 2026-09-30 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

should_i_batch
estimate_batchtime
conditions
distribution
coverage
wait

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-30 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

@modelcontextprotocol/sdk1.31.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.8
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.5
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.12
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.3
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.