io.github.egoughnour/cowork-history
PYPI · COWORK-HISTORY · 2 COMPONENTS
Hybrid search for Cowork history: FTS, Spotlight, and semantic vectors
Available components
Last scanned (17 hours ago)
Scores higher than 76% of PyPI servers
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency96
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to egoughnour/cowork-history). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 278 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 615 tokens (~61/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/cowork-history@4.0.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | egoughnour/cowork-history |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/egoughnour/cowork-history/.github/workflows/release.yml@refs/tags/v4.0.3 |
| Rekor log index | 871578376 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:551d346e209fe88f905a7a27b70d2d66e8fb5d8d382721bb94f32bf24d6150e2 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cowork_history_get Get Conversation Details ~27
Get full content of a specific conversation by session ID.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cowork_history_list List Recent Conversations ~29
List recent Claude conversations from the index, sorted by modification time.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cowork_history_projects List Projects ~27
List all projects with conversation history, showing reconstructed paths.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cowork_history_reindex Rebuild Index ~27
Rebuild the conversation index and optionally generate embeddings.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cowork_history_search Search Conversations ~102
Search Claude conversation history using hybrid search. Combines FTS5 full-text search, macOS Spotlight content indexing, and optional vector similarity (requires Ollama). Supports natural language, keywords, and "exact phrases". Examples: - "authentication bug" - finds conversations mentioning both words - "how to deploy" - semantic search finds related discussions - project:"my-app" query:"database" - filter by project
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cowork_history_stats Get Statistics ~25
Get statistics about conversation history and search capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
history_ollama_status History Ollama Status ~61
Check Ollama server status and available models. Returns whether Ollama is running and if the embedding model is available. Use to check if semantic/vector search is available.
| Name | Type | Req | Description |
|---|---|---|---|
| force_refresh | boolean | – | Force refresh the cached status (default: false) |
Structured output declared, but exposes no named fields.
No examples provided.
history_setup_ollama History Setup Ollama ~136
Install Ollama via Homebrew (macOS). Requires Homebrew pre-installed. Uses 'brew install' and 'brew services'. PROS: Auto-updates, pre-built binaries, managed service. CONS: Requires Homebrew, may prompt for sudo on first install.
| Name | Type | Req | Description |
|---|---|---|---|
| install | boolean | – | Install Ollama via Homebrew (requires Homebrew) |
| model | string | – | Model to pull (default: nomic-embed-text) |
| pull_model | boolean | – | Pull the embedding model (nomic-embed-text) |
| start_service | boolean | – | Start Ollama as a background service via brew services |
Structured output declared, but exposes no named fields.
No examples provided.
history_setup_ollama_direct History Setup Ollama Direct ~132
Install Ollama via direct download (macOS). Downloads from ollama.com to ~/Applications. PROS: No Homebrew needed, no sudo required, fully headless. CONS: Manual PATH setup, no auto-updates.
| Name | Type | Req | Description |
|---|---|---|---|
| install | boolean | – | Download and install Ollama to ~/Applications (no sudo needed) |
| model | string | – | Model to pull (default: nomic-embed-text) |
| pull_model | boolean | – | Pull the embedding model (nomic-embed-text) |
| start_service | boolean | – | Start Ollama server (ollama serve) in background |
Structured output declared, but exposes no named fields.
No examples provided.
history_system_check History System Check ~49
Check if system meets requirements for Ollama embeddings. Verifies: macOS, Apple Silicon (M1/M2/M3/M4), RAM, Homebrew. Use before attempting Ollama setup.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.egoughnour/cowork-history MCP server?
io.github.egoughnour/cowork-history runs locally as a PyPI package, launched with uvx cowork-history. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cowork-history
claude mcp add egoughnour-cowork-history -- uvx cowork-history
What is the io.github.egoughnour/cowork-history MCP server?
io.github.egoughnour/cowork-history is an MCP server listed in the public MCP registry as io.github.egoughnour/cowork-history. Hybrid search for Cowork history: FTS, Spotlight, and semantic vectors. This page covers its PyPI package (cowork-history).
Is the io.github.egoughnour/cowork-history MCP server safe to use?
io.github.egoughnour/cowork-history scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.egoughnour/cowork-history MCP server expose?
io.github.egoughnour/cowork-history exposes 10 tools: history_system_check, history_setup_ollama, history_setup_ollama_direct, history_ollama_status, cowork_history_search, and 5 more. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.
Is the io.github.egoughnour/cowork-history MCP server still maintained?
io.github.egoughnour/cowork-history is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.egoughnour/cowork-history MCP server under?
io.github.egoughnour/cowork-history declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.