io.github.jojo-labs/web-task-api

MCPcommunity
v0.10.1io.github.jojo-labsUnknownUpdated 1mo agonpmGitHub

Browser tasks, sessions, and recipes for MCP and HTTP automation.

is a generalized browser-task runtime for projects that want to treat websites like programmable APIs. For MCP discovery and host UI, the human-facing title should be Web Task. The package and registry IDs stay for compatibility because the same package ships both the HTTP API and the MCP server.[^2] It exposes one API for: starting from a URL + goal letting an agent drive a real browser…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.jojo-labs
LicenseUnknown
Version0.10.1
Sourcemcp-registry
npmweb-task-api
GitHubjojo-labs/web-task-api
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
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 surface12 tools · none privileged
Security scan✓ Cleanv0.10.1 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

is a generalized browser-task runtime for projects that want to treat websites like programmable APIs. For MCP discovery and host UI, the human-facing title should be Web Task. The package and registry IDs stay for compatibility because the same package ships both the HTTP API and the MCP server.[^2] It exposes one API for: starting from a URL + goal letting an agent drive a real browser validating structured output against a schema reusing persistent browser profiles and promoted recipes…

Keywords
mcp