Skip to content
mcp/skillhub

Context Oversharing Auditor MCP Server

by guardbeeio.github.GuardBee/context-oversharing-auditorv0.2.2

OWASP MCP10 context oversharing: session dumps, unscoped memory, shared context, prompt leaks

1Node.jsstdioofficial registry

context tax

pending

security

97/100

cold start

pending

freshness

Active3d ago

Our reading of Context Oversharing Auditor, from the data

Context Oversharing Auditor is a memory MCP server from guardbee, listed in the official MCP Registry.

We haven't measured its tool list yet, so its token cost is unknown.

Maintenance is active: the last public signal was 3 days ago (2026-10-16). For comparison, 68% of memory servers are active or maintained.

With 1 GitHub stars it ranks #700 of 1,597 memory servers we index.

It runs locally on your machine over stdio.

Install Context Oversharing Auditor MCP server

Install in Claude Code

claude mcp add context-oversharing-auditor -- npx -y @guardbee/mcp-context-oversharing-auditor

Security signals

97/100 — no known issues found as of 2026-10-19, from the checks below. This is not a guarantee of safety; review what a server can do before connecting it.

Deductions

  • No security policy (SECURITY.md)-3

Checks

  • ✓Repository hygiene (archived, activity, license, security policy)
  • ○Package metadata (install scripts, provenance) — pending
  • ○Tool descriptions (prompt-injection and hidden-text heuristics) — pending
  • ○Source scan (secrets, CVEs, risky code) by vectra-guard — pending

Scan it yourself before installing with vectra-guard, the open-source agent security CLI. Scoring rules

Freshness

Active — last maintenance signal 3d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-10-16 · 3d ago · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-10-13 · 5d ago · official registry · v0.2.2

How it compares in Memory

Against the most-starred memory servers we index. Token cost is per model turn, measured from each server's live tool list.

ServerStarsToolsTokens / turnFreshnessRuns
Context Oversharing Auditor (this)1—not measuredActivelocal
Memory91,356—not measuredActivelocal
Hindsight51,304—not measuredActive—
Codebase Memory46,873—not measuredActivelocal
Cognee32,506—not measuredActive—
Honcho7,681—not measuredActivehosted
All memory MCP servers

FAQ

›How do I install the Context Oversharing Auditor MCP server in Claude Code?

Run: claude mcp add context-oversharing-auditor -- npx -y @guardbee/mcp-context-oversharing-auditor. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Context Oversharing Auditor require an API key?

No required environment variables are declared in its published metadata.

›Can I use Context Oversharing Auditor as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Context Oversharing Auditor in the official MCP registry?

Yes, as io.github.GuardBee/context-oversharing-auditor.

Sources and method

Official MCP Registry entry
updated 2026-10-13
GitHub repository
fetched 2026-10-19
Package registry (npm / PyPI)
listed
Last checked against all sources
2026-10-19

The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Spot an error? Request a correction or claim the listing.

Alternatives to Context Oversharing Auditor

Other memory MCP servers.

View all