Query the Clerk Backend API (secret key; set CLERK_SECRET_KEY, Bearer): users, user details.
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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_usersClerk users, one page at a time, with email and id.Clerk users, one page at a time, with email and id.
No input schema was published for this tool.
get_userOne Clerk user by id, with profile and metadata.One Clerk user by id, with profile and metadata.
No input schema was published for this tool.
list_sessionsSessions in a Clerk instance, optionally filtered to one user or one client. Shows status, client, when it was last active, when it expires or abandons, device and IP from the latest activity, and how long it has been idle.Sessions in a Clerk instance, optionally filtered to one user or one client. Shows status, client, when it was last active, when it expires or abandons, device and IP from the latest activity, and how long it has been idle.
No input schema was published for this tool.
list_invitationsClerk sign-up invitations, newest first by default. Surfaces the status mix across the page and flags invitations that expired while still pending, so they can be chased or revoked.Clerk sign-up invitations, newest first by default. Surfaces the status mix across the page and flags invitations that expired while still pending, so they can be chased or revoked.
No input schema was published for this tool.
list_membershipsEveryone belonging to one Clerk organization with their role, permissions, public profile and join date. Can be narrowed to a role, a free-text query, or a last-active window, which makes it a way to find dormant admins.Everyone belonging to one Clerk organization with their role, permissions, public profile and join date. Can be narrowed to a role, a free-text query, or a last-active window, which makes it a way to find dormant admins.
No input schema was published for this tool.
health_checkCheck if the server is running and responsive.Check if the server is running and responsive.
No input schema was published for this tool.
version_infoGet server version and metadata.Get server version and metadata.
No input schema was published for this tool.
list_toolsList all available tools on this server.List all available tools on this server.
No input schema was published for this tool.
echoEcho back the provided text.Echo back the provided text.
No input schema was published for this tool.
timestampGet the current UTC timestamp.Get the current UTC timestamp.
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.
Query the Clerk Backend API (secret key; set CLERK_SECRET_KEY, Bearer): users, user details.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
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)
55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+43 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.