OmniSerp v0.7.0 Release Notes¶

Release Date: December 29, 2025

Highlights¶

Secure credential management with VaultGuard integration
MCP server renamed to follow mcp- prefix convention

New Features¶

Secure Credential Management¶

The mcp-omniserp MCP server now includes optional secure credential management using VaultGuard. This provides enterprise-grade security for API key handling while maintaining full backward compatibility.

Key Features:

OS Keychain Integration: API keys can be stored in the OS keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service) instead of environment variables
Security Posture Checking: Validates system security before granting credential access
Policy-Based Access Control: Configure security requirements via ~/.vaultguard/policy.json
Graceful Fallback: Automatically uses environment variables when no policy is configured

How It Works:

Without a policy file: Works exactly as before - reads API keys from environment variables
With a policy file: Retrieves API keys from the OS keychain with security posture validation

Standard Mode (environment variables):

export SERPER_API_KEY="your-key"
export SEARCH_ENGINE="serper"  # optional, defaults to serper
./mcp-omniserp

Secure Mode (OS keychain + policy):

Store your API key in the keychain:

security add-generic-password -s "omnivault" -a "SERPER_API_KEY" -w "your-key"

Create a security policy (~/.vaultguard/policy.json):

{
  "version": 1,
  "local": {
    "require_encryption": true,
    "min_security_score": 50
  }
}

Run the server:

./mcp-omniserp

Security Logging:

When running in secure mode, the server logs security check results including:

Security score and level
Platform information
Disk encryption status
Biometrics configuration status

New Client SDK Functions¶

client.NewWithRegistry() - Create a client with a pre-configured registry
serpapi.NewWithAPIKey() - Create a SerpAPI engine with a specific API key

Changes¶

MCP Server Rename¶

The MCP server has been renamed from mcpserver to mcp-omniserp to follow the mcp- prefix naming convention.

Before:

{
  "mcpServers": {
    "omniserp": {
      "command": "mcpserver"
    }
  }
}

After:

{
  "mcpServers": {
    "omniserp": {
      "command": "mcp-omniserp",
      "env": {
        "SERPER_API_KEY": "your_serper_api_key"
      }
    }
  }
}

Documentation¶

Added icons to README Overview feature list
Updated README formatting
Added Marp presentation (PRESENTATION.md)

Migration Guide¶

MCP Server Rename¶

If you're using the MCP server, update your configuration:

Before:

{
  "mcpServers": {
    "omniserp": {
      "command": "mcpserver"
    }
  }
}

After:

{
  "mcpServers": {
    "omniserp": {
      "command": "mcp-omniserp",
      "env": {
        "SERPER_API_KEY": "your_serper_api_key"
      }
    }
  }
}

Upgrading to Secure Credentials (Optional)¶

To upgrade from environment variables to secure keychain storage:

Add your API key to the OS keychain
Create a policy file at ~/.vaultguard/policy.json
Remove the env section from your MCP config (credentials now come from keychain)

{
  "mcpServers": {
    "omniserp": {
      "command": "mcp-omniserp"
    }
  }
}

Dependencies¶

github.com/plexusone/omnivault-keyring v0.2.0 - OS keychain integration
github.com/plexusone/vaultguard v0.3.0 - Security posture checking and policy management