ai.withhuman/withhuman

MCPcommunitylive
v1.0.0ai.withhumanUnknownUpdated 2d agoGitHub

Set up human approval for your AI agents' tool calls.

Endpoint healthlive
checked 14h ago · 350ms · auth required
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). 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 →
11GitHub stars
2Forks
2d agoLast update
Package
Authorai.withhuman
LicenseUnknown
Version1.0.0
Sourcemcp-registry
Trust Status
B
60/100Good
Hosted endpoint only: this assessment covers who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface10 tools · none privileged
Security scan✓ CleanvHEAD · todayHow well does this scan work?
EvalsNone
IndexedOct 16, 2026

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

Tools

10 tools · none privileged
Statically extracted from the published packagevHEAD · 8h 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.

create_issueCreate an issue in a team

Create an issue in a team

No input schema was published for this tool.

update_issueChange an issue's fields

Change an issue's fields

No input schema was published for this tool.

list_issuesList issues matching a filter

List issues matching a filter

No input schema was published for this tool.

add_commentComment on an issue

Comment on an issue

No input schema was published for this tool.

list_teamsList the workspace's teams

List the workspace's teams

No input schema was published for this tool.

list_projectsList projects

List projects

No input schema was published for this tool.

create_projectCreate a project

Create a project

No input schema was published for this tool.

archive_issueArchive an issue

Archive an issue

No input schema was published for this tool.

assign_issueAssign an issue to a person

Assign an issue to a person

No input schema was published for this tool.

list_cyclesList a team's cycles

List a team's cycles

No input schema was published for this tool.

10 of 10 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

Set up human approval for your AI agents' tool calls.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.