Loading ToolBench

Reading the current corpus…

passwd MCP server · D · ToolBench

← Browse

passwd

github.com/pepuscz/passwd

MCP server for passwd.team password manager

2026-07-28+STDIO5 tools

57/100

Definition Quality76

Protocol Readiness40

Supportability38

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

passwd-mcp defines 5 tools with clear naming conventions (all start with action verbs: passwd_login, list_secrets, get_secret, get_totp_code, get_current_user). All tools have descriptions and input schemas are visible with type definitions. However, several critical gaps reduce the score: (1) parameter descriptions lack depth and validation guidance; (2) output schemas are not explicitly documented; (3) error handling and recovery guidance are absent; (4) no tool annotations (readOnlyHint, idempotentHint) despite all being read-only; (5) passwd_login description relies on example values and could be clearer. The server follows basic tool definition patterns but falls short of production-grade LLM optimization.

Tools (5)

get_current_userread onlyauthsource verified75/100

Get the currently authenticated user's profile information.

get_secretread onlyauthsource verified78/100

Get secret details. Sensitive fields (password, keys, etc.) are redacted — use passwd CLI exec --inject to use credentials without exposing them.

get_totp_coderead onlyauthsource verified75/100

Get the current TOTP (Time-based One-Time Password) code for a secret that has TOTP configured.

list_secretsread onlyauthsource verified82/100

List password records from passwd.team. Supports filtering by query text and secret type.

passwd_loginread onlysource verified70/100

Authenticate with passwd.team using Google OAuth. Call without redirectUrl to get the login URL, then call again with the redirect URL containing the auth code.

Issues (6)

HIGHtool ↗

Output schemas are not documented. LLMs cannot predict the structure of responses and cannot chain tools effectively.

passwd_loginlist_secretsget_secretget_totp_codeget_current_user

MEDIUMtool-description ↗

passwd_login description contains example behavior ('Call without redirectUrl to get the login URL, then call again with the redirect URL') that may cause LLMs to hallucinate these specific sequences rather than adapting to the auth flow.

passwd_login

HIGHconstrained-input ↗

Parameter descriptions lack validation guidance. 'query' in list_secrets has no length limits, format constraints, or examples. 'offset' and 'limit' lack numeric bounds (defaults and maximums).

list_secrets

HIGHrecovery-guide ↗

No error recovery guidance. Descriptions do not explain what to do if authentication fails, a secret ID is invalid, or TOTP is not configured. LLMs have no guidance for recovery.

Recommendations

Add explicit output schemas for all tools. Example for list_secrets: 'Returns: {secrets: [{id: string, name: string, type: enum, username?: string, url?: string}], total: number, hasMore: boolean}'. This enables LLM planning and chaining.
For list_secrets, add numeric constraints: 'offset (default: 0, min: 0)', 'limit (default: 50, max: 100)'. Document that offset + limit > total_count returns empty results.
Rephrase passwd_login description to avoid example sequences: 'Authenticate with Google OAuth. The tool returns a login URL on first call; after user completes OAuth flow, call again with the redirect URL to complete authentication.' This guides LLM behavior without prescribing exact steps.
Add error recovery hints to each tool: 'If invalid secret ID, call list_secrets to discover available secrets.' 'If TOTP code returns an error, the secret may not have TOTP configured, call get_secret to verify.'
Annotate all tools with readOnlyHint in the schema (modern MCP spec). Example: {readOnlyHint: true} in tool definition.
Document what get_secret returns: 'Returns secret metadata (id, name, type, username, url, tags) with sensitive values redacted. Use passwd CLI exec --inject to access credentials without exposing them.'
For passwd_login redirectUrl parameter, clarify format: 'The full redirect URL from Google OAuth callback, including the code parameter. Example format: https://your-redirect-uri?code=<auth_code>&state=<state>'. Avoid naming the example value, describe the structure instead.

Score history

Overall score trend

↑ 1 points across a rubric change (v1 → v2)

57/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-22	D	57	2026-07-28+	v2
2026-03-09	D	56	-	v1