Claude Code statusline that summarizes MCP server count, remote endpoint count, and credential-surface hints without printing tokens, secrets, local paths, or full endpoint URLs.
This statusline is advisory and should not be used as the only MCP authorization review., It intentionally avoids printing full URLs, local paths, header names, tokens, or environment variable values., Remote endpoints and credential hints should trigger a separate review of protected resource metadata, scopes, and token handling.
Privacy notes
The statusline reads Claude Code session metadata from stdin and prints only counts plus a generic credential hint., Avoid modifying the script to print full server URLs, headers, tokens, local config paths, or account identifiers on shared screens.
Author
JSONbored
Submitted by
JSONbored
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
3 safety and 2 privacy notes across 2 risk areas. Review closely: credentials & tokens, permissions & scopes.
2 areas
SafetyPermissions & scopesThis statusline is advisory and should not be used as the only MCP authorization review.
SafetyCredentials & tokensIt intentionally avoids printing full URLs, local paths, header names, tokens, or environment variable values.
SafetyCredentials & tokensRemote endpoints and credential hints should trigger a separate review of protected resource metadata, scopes, and token handling.
PrivacyCredentials & tokensThe statusline reads Claude Code session metadata from stdin and prints only counts plus a generic credential hint.
PrivacyCredentials & tokensAvoid modifying the script to print full server URLs, headers, tokens, local config paths, or account identifiers on shared screens.
Safety notes
This statusline is advisory and should not be used as the only MCP authorization review.
It intentionally avoids printing full URLs, local paths, header names, tokens, or environment variable values.
Remote endpoints and credential hints should trigger a separate review of protected resource metadata, scopes, and token handling.
Privacy notes
The statusline reads Claude Code session metadata from stdin and prints only counts plus a generic credential hint.
Avoid modifying the script to print full server URLs, headers, tokens, local config paths, or account identifiers on shared screens.
Prerequisites
Claude Code CLI with statusline support.
jq installed locally.
MCP server metadata available in the Claude Code statusline input.
Counts configured MCP servers from Claude Code statusline input.
Counts remote HTTP and HTTPS MCP endpoints.
Shows whether credential-like metadata appears without printing values.
Keeps terminal output compact enough for repeated refreshes.
Uses official Claude Code statusline behavior and MCP authorization guidance as sources.
Why use it
MCP auth mistakes often start as visibility problems. A local session can have a
mix of stdio servers, remote servers, and OAuth-backed endpoints. This
statusline gives a small prompt to review the authorization surface without
turning the terminal into a secret leak.
Show that MCP Auth Surface Statusline is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/statuslines/mcp-auth-surface-statusline)
How it compares
MCP Auth Surface Statusline side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
Claude Code statusline that summarizes MCP server count, remote endpoint count, and credential-surface hints without printing tokens, secrets, local paths, or full endpoint URLs.
Real-time burn rate monitor showing cost per minute, tokens per minute, and projected daily spend to prevent budget overruns during Claude Code sessions.
A Claude Code statusline that reads prompt-cache token metrics from session JSON and renders a color-coded hit-rate bar with an estimated token-savings readout.
Claude Code statusline that estimates context pressure from local session token counts and a configurable context limit, then prints a compact risk tier.
✓This statusline is advisory and should not be used as the only MCP authorization review.
It intentionally avoids printing full URLs, local paths, header names, tokens, or environment variable values.
Remote endpoints and credential hints should trigger a separate review of protected resource metadata, scopes, and token handling.
✓Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.
✓Runs a bash script on every status-line refresh (about every 2 seconds) that pipes session JSON through jq and bc; it is read-only and makes no network calls or file writes, but status-line commands execute with your shell's permissions, so review the script before adding it to settings.json.
✓Context percentage is only as accurate as the configured limit and the usage fields available in the statusline input.
Use the warning as a cue to summarize or checkpoint work before context pressure affects reasoning quality.
Do not treat a low percentage as proof that all relevant files, instructions, or tool results are still in scope.
Privacy notes
✓The statusline reads Claude Code session metadata from stdin and prints only counts plus a generic credential hint.
Avoid modifying the script to print full server URLs, headers, tokens, local config paths, or account identifiers on shared screens.
✓Reads the Claude Code statusline JSON from stdin (model, workspace path, token usage) and renders it in the local terminal; it does not send data off-machine.
✓Reads Claude Code session cost and token metrics from the status-line JSON on stdin and prints them to your terminal; no data leaves the machine, but the displayed figures may be visible to anyone viewing your screen or a terminal recording.
✓The script reads local session counters and does not inspect prompt text, files, or transcript contents.
Token counts and configured limits can still reveal workload size in screenshots or shared terminal logs.
Teams should avoid placing customer names or project identifiers in shell variables that appear in debugging output.
Prerequisites
Claude Code CLI with statusline support.
jq installed locally.
MCP server metadata available in the Claude Code statusline input.
Claude Code CLI installed and configured
Bash shell available (bash 4.0+ recommended for arithmetic operations)
jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
bc calculator (bc 1.07+ required for floating point calculations - script will fail without bc)
Claude Code CLI installed and configured
Bash shell available (bash 4.0+ recommended for arithmetic operations)
jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
bc calculator (bc 1.07+ optional for precise savings calculations, script falls back to integer math)
Claude Code statusline support with local JSON input.
jq available for reading session usage fields.
Optional CLAUDE_CONTEXT_LIMIT set to the model or workflow limit your team wants to track.