Guardian Search MCP

Search infrastructure for AI agents.

Give your agents one search interface that returns clean, typed results. Guardian handles engine fan-out, normalization, and failures so your model can keep working.

Multi-engine web search Typed MCP tools Browser + mirror domains ready
Latest agent prompt search_web
Best SOC 2 note-taking app for teams under $15 / seat
Web Shopping Companies
Typed output JSON
  • 1. title, url, host, summary
  • 2. ranking, source engines, freshness
  • 3. vertical fields like price, ticker, publisher
6 engines queried 812 ms
Used anywhere agents need grounded retrieval
LokiAgent Cursor Claude Codex MCP hosts Custom runtimes
Why teams switch

Results your agents can actually use.

Guardian replaces page scraping with stable response shapes. That cuts prompt bloat, reduces brittle browser flows, and keeps retrieval easy to observe.

One tool instead of many search tabs

Ask for web, shopping, company, finance, or site discovery results through one interface. Your runtime does not need custom logic per search engine.

90% token reduction Highlights and summaries keep prompts small.

Lean payloads

Responses stay concise while preserving the fields an agent needs for ranking, citations, and downstream steps.

{"companies":[{"company_name":"...","ceo_name":"...","founded_year":"..."}]}

Structured outputs by default

Build flows that depend on consistent JSON, not a rendered page that changes layout every other week.

01

Typed search tools

Use MCP tools such as search_web, search_shopping, discover_sites, and finance_quote.

02

Multi-engine resilience

Guardian fans out queries, deduplicates overlapping results, and reports which engines succeeded or failed.

03

Deterministic agent mode

When a browser is still the right tool, Agent Mode keeps search controls and URLs predictable for automation.

04

Operational visibility

Inspect elapsed time, provider information, paging, and diagnostics without scraping hidden UI state.

Delivery model MCP + JSON

Use the same search service from direct HTTP clients, orchestrators, or agent frameworks.

Primary endpoint /v1

The canonical transport stays at https://mcp.guardianbrowser.sh/v1.

Brand flexibility 1:1 mirror

guardiansearch.sh can mirror the full public, API, and MCP surface without splitting the stack.

Best use Grounded agents

Research, buying flows, link discovery, finance lookups, and other tasks that need live sources.

Developers

Connect once. Ship everywhere.

Use the MCP endpoint for tool-based agents or the JSON API for direct application logic. Guardian also publishes OpenAPI, llms.txt, OpenSearch metadata, and an agent manifest.

Fast start

Point your client at the MCP endpoint and start calling search tools right away.

Search + browser together

Use Guardian Search MCP for retrieval, then open the browser only for pages that truly need interaction.

Mirror domain support

The Terraform stack can provision guardiansearch.sh as a full mirror of guardianbrowser.sh, including api and mcp subdomains.

Claude Desktop / agent runtime
{
  "mcpServers": {
    "guardian_search": {
      "transport": "streamable_http",
      "url": "https://mcp.guardianbrowser.sh/v1"
    }
  }
}
Enterprise

Security, routing, and naming flexibility built in.

Run the public site, API, and MCP endpoint behind one stack. Keep guardianbrowser.sh as the primary brand today and keep guardiansearch.sh ready as a 1:1 mirror if you ever need to switch names.

Single infrastructure surface

The same deployment serves the browser site, the JSON API, and the dedicated MCP hostname.

Alternate-domain ready

Provision apex, www, api, and mcp records for the mirror domain and include them in ACM in one plan.

Predictable host routing

mcp.* serves Streamable HTTP at /v1. The legacy /mcp path redirects to /v1.

Private by default

Guardian keeps browser automation for browser work and keeps search retrieval in a compact, inspectable interface.

Guardian Search MCP

Stop teaching agents how to use search pages.

Give them a search interface built for software. Use the browser only when a task truly needs a browser.