Compass Daas

Created By
compass-food21 days ago
Compass DaaS is a Model Context Protocol server for AI agents that need structured restaurant dietary intelligence. It exposes three tools over stdio: compass_search for natural-language restaurant search, compass_enrich_restaurant for matching and enrichment, and compass_decide_fit for evidence-backed dietary suitability decisions.
Overview

Compass DaaS is an MCP server for AI agents that need restaurant dietary intelligence.

It exposes three tools:

  • compass_search: natural-language restaurant search with VeganScore, evidence, and confidence.
  • compass_enrich_restaurant: match and enrich a restaurant by Compass ID, name/address, or Google Place ID.
  • compass_decide_fit: conservative fit, not_fit, or unknown decision for a restaurant against a dietary profile.

The server runs over stdio with npx -y @compass-food/mcp and calls the Compass REST API. Live tool calls require a Compass API key. Free Sandbox keys are available at https://compassfoodtechnologies.com/signup.

Docs: https://compassfoodtechnologies.com/docs/mcp OpenAPI: https://compassfoodtechnologies.com/openapi.json GitHub: https://github.com/compass-food/compass-mcp npm: https://www.npmjs.com/package/@compass-food/mcp

Server Config

{
  "mcpServers": {
    "compass": {
      "command": "npx",
      "args": [
        "-y",
        "@compass-food/mcp"
      ],
      "env": {
        "COMPASS_API_KEY": "your_key_here"
      }
    }
  }
}
Project Info
Created At
21 days ago
Updated At
21 days ago
Author Name
compass-food
Star
-
Language
-
License
-
Category
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago