@ramex-labs/continuity-mcp-gateway

MCPcommunity
v0.3.0-preview.10io.github.zerohourzuluApache-2.0Updated 6d agonpmGitHub

Local MCP gateway for approved jobs, current agent permissions and durable retry inspection.

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 →
371Downloads/wk
6d agoLast update
Package
Authorio.github.zerohourzulu
LicenseApache-2.0
Version0.3.0-preview.10
Sourcenpm+mcp-registry
npm@ramex-labs/continuity-mcp-gateway
GitHubzerohourzulu/continuity
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✓ 31 resolved · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv0.3.0-preview.6 · 5d agoHow well does this scan work?
EvalsNone
IndexedSep 24, 2026

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

Tools

4 tools · none privileged
Statically extracted from the published packagev0.3.0-preview.6 · 5d 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.

continuity_statusInspect the original approved job without sending it again. Requires current inspection permission.

Inspect the original approved job without sending it again. Requires current inspection permission.

No input schema was published for this tool.

continuity_whyCheck current permission for a job. This explanation is not permission to execute.

Check current permission for a job. This explanation is not permission to execute.

No input schema was published for this tool.

read_documentNo description published

This tool published no description. Forge does not invent one.

create_ticketNo description published

This tool published no description. Forge does not invent one.

2 of 4 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

Local MCP gateway for approved jobs, current agent permissions and durable retry inspection.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

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

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-26 — observed resolution, not a publisher declaration.

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

7 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)

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