@cqnce/mcp-server

MCPcommunitylive
v0.1.3UnknownMITUpdated 2d agonpmGitHub

MCP server exposing cQnce human-in-the-loop authorization as AI-callable tools

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

Inferred from the transports this listing declares (stdio, 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 →
191Downloads/wk
1GitHub stars
2d agoLast update
Needs 1 credential before it runs
  • CQNCE_API_KEYAPI keyrequired

    Project API key from cQnce

  • CQNCE_ADMIN_TOKENAPI keyoptional

    Optional tenant admin JWT for project, agent, team, and callback management tools

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.1.3
Sourcenpm+mcp-registry
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 surface27 tools · 3 privileged
Security scan✓ Cleanv0.1.3 · todayHow well does this scan work?
EvalsNone
IndexedSep 30, 2026

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

Tools

27 tools · 3 privileged
Statically extracted from the published packagev0.1.3 · 6h 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.

list_agentsList all agents (human approvers) who have joined the current tenant.

List all agents (human approvers) who have joined the current tenant.

No input schema was published for this tool.

get_agentGet details of a specific agent by ID.

Get details of a specific agent by ID.

No input schema was published for this tool.

invite_agentInvite an agent to join the tenant by phone number.

Invite an agent to join the tenant by phone number.

No input schema was published for this tool.

list_agent_invitesList all agent invitations sent by this tenant, including their status (PENDING, ACCEPTED, DECLINED).

List all agent invitations sent by this tenant, including their status (PENDING, ACCEPTED, DECLINED).

No input schema was published for this tool.

list_teamsList all agent teams in the current tenant.

List all agent teams in the current tenant.

No input schema was published for this tool.

create_teamCreate a new agent team.

Create a new agent team.

No input schema was published for this tool.

add_agent_to_teamAdd an agent to a team.

Add an agent to a team.

No input schema was published for this tool.

remove_agent_from_teamprivilegedRemove an agent from a team.

Remove an agent from a team.

No input schema was published for this tool.

list_callbacksList all webhook callbacks configured for a project.

List all webhook callbacks configured for a project.

No input schema was published for this tool.

create_callbackConfigure a webhook endpoint that cQnce will call when a request is resolved.

Configure a webhook endpoint that cQnce will call when a request is resolved.

No input schema was published for this tool.

update_callbackUpdate an existing webhook callback.

Update an existing webhook callback.

No input schema was published for this tool.

delete_callbackprivilegedDelete a webhook callback from a project.

Delete a webhook callback from a project.

No input schema was published for this tool.

rotate_callback_secretRotate the HMAC signing secret for a webhook callback.

Rotate the HMAC signing secret for a webhook callback.

No input schema was published for this tool.

list_projectsList all projects in the current tenant.

List all projects in the current tenant.

No input schema was published for this tool.

get_projectGet full details of a project, including routing rules and webhook callbacks.

Get full details of a project, including routing rules and webhook callbacks.

No input schema was published for this tool.

create_projectCreate a new project in the current tenant.

Create a new project in the current tenant.

No input schema was published for this tool.

update_projectUpdate an existing project's settings.

Update an existing project's settings.

No input schema was published for this tool.

list_routing_rulesList all routing rules for a project, ordered by priority (highest first).

List all routing rules for a project, ordered by priority (highest first).

No input schema was published for this tool.

create_routing_ruleCreate a routing rule for a project. Routing rules determine which agents or teams

Create a routing rule for a project. Routing rules determine which agents or teams

No input schema was published for this tool.

update_routing_ruleUpdate an existing routing rule.

Update an existing routing rule.

No input schema was published for this tool.

delete_routing_ruleprivilegedDelete a routing rule from a project.

Delete a routing rule from a project.

No input schema was published for this tool.

submit_authorization_requestSubmit a human authorization request to cQnce. Use this BEFORE performing any

Submit a human authorization request to cQnce. Use this BEFORE performing any

No input schema was published for this tool.

poll_request_statusCheck the current status of a cQnce authorization request.

Check the current status of a cQnce authorization request.

No input schema was published for this tool.

wait_for_approvalSubmit an authorization request and BLOCK until a human approves or rejects it

Submit an authorization request and BLOCK until a human approves or rejects it

No input schema was published for this tool.

cancel_requestCancel a pending cQnce authorization request.

Cancel a pending cQnce authorization request.

No input schema was published for this tool.

list_requestsList authorization requests for this project.

List authorization requests for this project.

No input schema was published for this tool.

get_requestGet full details of a single authorization request, including payload, metadata,

Get full details of a single authorization request, including payload, metadata,

No input schema was published for this tool.

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

MCP server exposing cQnce human-in-the-loop authorization as AI-callable tools

Keywords
cqncemcpmodel-context-protocolhuman-in-the-loopauthorization
Alternatives
Comparing tool surfaces…

Dependency tree

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

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

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

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

+42 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.