Skip to main content
statuslinesSource-backed

MCP Auth Surface Statusline

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.

by JSONbored·added 2026-06-05·
Language:bash
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://code.claude.com/docs/en/statusline, https://github.com/JSONbored/awesome-claude/blob/main/content/statuslines/mcp-auth-surface-statusline.mdx
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.
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.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Install & runtime1Network & hosting1General1

Safety & privacy surface

Safety & privacy surface

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.

Schema details

Install type
cli
Troubleshooting
No
Runtime and command metadata
Script language
bash
Script body
#!/usr/bin/env bash
set -u

input=$(cat)
if ! command -v jq >/dev/null 2>&1; then
  printf 'MCP auth: jq unavailable\n'
  exit 0
fi

servers=$(printf '%s' "$input" | jq -c '.mcp.servers // []' 2>/dev/null || printf '[]')
server_count=$(printf '%s' "$servers" | jq 'length' 2>/dev/null || printf '0')
remote_count=$(printf '%s' "$servers" | jq '[.[] | select((.url // .endpoint // "") | test("^https?://"))] | length' 2>/dev/null || printf '0')
credential_hint=$(printf '%s' "$servers" | jq '[.[] | select((.auth // .authorization // .headers // .env // null) != null)] | length' 2>/dev/null || printf '0')

if [ "$credential_hint" -gt 0 ]; then
  state="credentials: review"
else
  state="credentials: none shown"
fi

printf 'MCP auth: %s servers | %s remote | %s\n' "$server_count" "$remote_count" "$state"
Full copyable content
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-auth-surface.sh"
  }
}

About this resource

Features

  • 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.

References

Source citations

Add this badge to your README

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.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/statuslines/mcp-auth-surface-statusline.svg)](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.

Field

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.

Open dossier

Real-time burn rate monitor showing cost per minute, tokens per minute, and projected daily spend to prevent budget overruns during Claude Code sessions.

Open dossier

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.

Open dossier

Claude Code statusline that estimates context pressure from local session token counts and a configurable context limit, then prints a compact risk tier.

Open dossier
Next stepsDiffers
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersJSONboredMkDev11
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categorystatuslinesstatuslinesstatuslinesstatuslines
SourceSource-backedSource-backedSource-backedSource-backed
AuthorJSONboredJSONboredJSONboredMkDev11
Added2026-06-052025-10-252025-10-252026-06-04
Platforms
Harness
Source repo
Safety notesThis 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 notesThe 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.
Install
mkdir -p .claude/statuslines
tmp="$(mktemp .claude/statuslines/mcp-auth-surface.sh.XXXXXX)"
cat > "$tmp" <<'EOF'
#!/usr/bin/env bash
set -u

input=$(cat)
if ! command -v jq >/dev/null 2>&1; then
  printf 'MCP auth: jq unavailable\n'
  exit 0
fi

servers=$(printf '%s' "$input" | jq -c '.mcp.servers // []' 2>/dev/null || printf '[]')
server_count=$(printf '%s' "$servers" | jq 'length' 2>/dev/null || printf '0')
remote_count=$(printf '%s' "$servers" | jq '[.[] | select((.url // .endpoint // "") | test("^https?://"))] | length' 2>/dev/null || printf '0')
credential_hint=$(printf '%s' "$servers" | jq '[.[] | select((.auth // .authorization // .headers // .env // null) != null)] | length' 2>/dev/null || printf '0')

if [ "$credential_hint" -gt 0 ]; then
  state="credentials: review"
else
  state="credentials: none shown"
fi

printf 'MCP auth: %s servers | %s remote | %s\n' "$server_count" "$remote_count" "$state"
EOF
chmod 700 "$tmp"
mv -f "$tmp" .claude/statuslines/mcp-auth-surface.sh
Config
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-auth-surface.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/burn-rate-monitor.sh",
    "refreshInterval": 500
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/cache-efficiency-monitor.sh",
    "refreshInterval": 2000
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/context-pressure-statusline.sh"
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.