Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • The install package comes from a different repo than this listing's
Own this project? Claim it
BrowseAI Dev logo

BrowseAI Dev

Researches the web, extracts claims, verifies evidence, and returns cited answers with confidence data.

Install BrowseAI Dev

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "browseai-dev": {
      "command": "npx",
      "args": [
        "-y",
        "verify-anything"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

BrowseAI Dev MCP server gives AI agents tools for web search, page retrieval, claim extraction, citation, and evidence-backed answers. Its answer pipeline combines search, extraction, verification, and confidence scoring, with fast, thorough, and deep research modes. Session tools preserve verified knowledge across related questions and support sharing, exporting, and forking research. Reach for it when an agent needs traceable web research rather than an unsupported generated answer.

Use cases

  • Research current topics with cited sources
  • Extract verifiable claims from web pages
  • Compare generated answers with evidence-backed results
  • Build persistent research sessions across follow-up questions
  • Check claims for contradictions and citation health

Key features

  • Web search and clean page text retrieval
  • Structured claim extraction and verification
  • Cited answers with confidence and consensus data
  • Fast, thorough, and deep research modes
  • Persistent sessions with sharing and forking
  • Raw-versus-evidence-backed answer comparison

Tools13

What BrowseAI Dev lets your agent do. Expand a tool for its parameters.

Self-reported~202 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

22/24 checks healthy over the last 104d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · verify-anything (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars20Stargazers on the source repository.
npm downloads389Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Tools exposed13Callable tools this server registers over MCP.

How BrowseAI Dev works

What the BrowseAI Dev MCP server does

BrowseAI Dev MCP server exposes web research and verification capabilities to an MCP-compatible AI agent. The repository documentation identifies the underlying research system as LastSearch, which searches the internet, retrieves pages, extracts claims, and produces answers with source URLs and confidence information.

The server is suited to questions where an agent needs to show its evidence. It can return structured claims, source details, consensus signals, contradiction findings, and citation health information. Agents can use those fields to make their own decisions about whether an answer is sufficiently supported.

How it works

The core research flow starts with web search, fetches and parses relevant pages, extracts claims, and verifies those claims against the source text. The answer operation combines these stages and can run at three depths:

  • fast performs a single search, extraction, and verification pass.
  • thorough can run additional evidence retrieval, counter-query checks, and consistency checks for weak claims.
  • deep performs iterative research passes that identify gaps, generate follow-up queries, and re-check the combined result. It requires a LastSearch key and sign-in; without the key or after quota exhaustion, it falls back to thorough mode.

Verification can include keyword and semantic matching, source authority, cross-source agreement, contradiction detection, quote checking, and citation URL health. The documentation says premium keys enable semantic retrieval and reranking, while keyword-only verification remains available without those keys.

Tools and capabilities

BrowseAI Dev MCP server provides separate tools for each stage as well as higher-level research workflows:

  • search finds information on a topic.
  • open retrieves a web page and converts it to clean text.
  • extract identifies structured claims from a page.
  • answer returns a researched answer with extracted evidence and citations.
  • compare contrasts a raw language-model answer with an evidence-backed answer.
  • clarity supports prompt-only, language-model, and verified web-fusion modes.
  • Session tools create, query, recall, share, export, and fork persistent research sessions.
  • feedback submits feedback about a result for accuracy improvement.

Session research retains verified knowledge for later questions, so follow-up queries can use prior findings without performing a new web search. Shared sessions return a public share URL, while exported session knowledge provides the accumulated claims.

Limitations and notes

BrowseAI Dev MCP server depends on external web pages and search, language-model, and page-fetching services. Those calls may encounter transient rate limits or server errors; the documented system retries such failures with exponential backoff, while authentication errors fail immediately.

Deep research uses more quota than the other modes: the documentation states that each deep query costs three times the quota and that deep mode supports 100 queries per day. Deep research targets a confidence threshold of 0.85 and can run up to four total research steps. Session features require a LastSearch API key for identity and ownership.

Confidence is evidence-based rather than a language model's self-assessment, but it remains a signal for agent decision-making, not a substitute for reviewing the cited material. A claim supported by only one source may be marked weak, while conflicting sources can reduce confidence. Citation health distinguishes live, stale, and dead URLs when the relevant checks are available.

Written by AllMCPs with AI assistance from the project’s README and listing data. How we build listings

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about BrowseAI Dev

BrowseAI Dev is an MCP server that connects AI agents to web research infrastructure for searching the internet, opening pages, extracting claims, and producing cited answers. Its main tools include `search`, `open`, `extract`, `answer`, `compare`, `clarity`, and persistent research session operations with confidence and verification data.

It identifies npm and PyPI packages for the underlying LastSearch system, but does not give enough information to state how to install or register this MCP server.

Yes, BrowseAI Dev supports persistent research sessions. Use session creation and session query tools to retain verified knowledge across questions, then recall, share, export, or fork that session. Session features require a LastSearch API key for identity and ownership.

Fast performs one search, extraction, and verification pass. Thorough can repeat retrieval and checking for weak claims, while deep performs iterative research with gap analysis and follow-up queries. Deep mode requires a LastSearch key and sign-in, and falls back to thorough when unavailable or when its quota is exhausted.

Yes, the research pipeline checks extracted claims against source text, detects contradictions, and reports citation health when applicable. Results can include verification scores, consensus counts, source authority, and URL status such as live, stale, or dead.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBrowseAI Dev AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/browseai-dev?style=directory)](https://allmcps.com/mcp/browseai-dev)
HTML Embed
<a href="https://allmcps.com/mcp/browseai-dev"><img src="https://allmcps.com/api/badge/browseai-dev?style=directory" alt="BrowseAI Dev on AllMCPs" /></a>