Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.infoinlet-marketplace/mcp-browser-research

NPM · @INFOINLET/MCP-BROWSER-RESEARCH · SCANNED SEP 20

Web browsing & research for AI agents — fetch/read pages, structured extraction, Exa search.

+1 this week 72 Trust /100
Trust breakdown (7 categories)

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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 36 of 132 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 210 tokens (~52/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 13% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.infoinlet-marketplace/mcp-browser-research server?

io.github.infoinlet-marketplace/mcp-browser-research runs locally as an npm package, launched with npx -y @infoinlet/mcp-browser-research. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @infoinlet/mcp-browser-research

# add to Claude Code
claude mcp add infoinlet-marketplace-mcp-browser-research -- npx -y @infoinlet/mcp-browser-research
// .cursor/mcp.json
{
  "mcpServers": {
    "infoinlet-marketplace-mcp-browser-research": {
      "command": "npx",
      "args": [
        "-y",
        "@infoinlet/mcp-browser-research"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "infoinlet-marketplace-mcp-browser-research": {
      "command": "npx",
      "args": [
        "-y",
        "@infoinlet/mcp-browser-research"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add infoinlet-marketplace-mcp-browser-research -- npx -y @infoinlet/mcp-browser-research
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "infoinlet-marketplace-mcp-browser-research": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@infoinlet/mcp-browser-research"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add infoinlet-marketplace-mcp-browser-research --command npx --arg -y --arg @infoinlet/mcp-browser-research
# ~/.hermes/config.yaml
mcp_servers:
  infoinlet-marketplace-mcp-browser-research:
    command: "npx"
    args: ["-y", "@infoinlet/mcp-browser-research"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "infoinlet-marketplace-mcp-browser-research": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@infoinlet/mcp-browser-research"
      ]
    }
  }
}
# add to Vellum
assistant mcp add infoinlet-marketplace-mcp-browser-research -t stdio -c npx -a -y @infoinlet/mcp-browser-research
// mcp.json
{
  "mcpServers": {
    "infoinlet-marketplace-mcp-browser-research": {
      "command": "npx",
      "args": [
        "-y",
        "@infoinlet/mcp-browser-research"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Analysed npm/@infoinlet/mcp-browser-research@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 132 packages
Packages resolved 132
Deprecated 1
Stale 36
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~210 tokens

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 →

Tool Tokens
browse_url ~51

Fetch a web page and return its title + clean readable main-content text. Works for static/SSR pages. Optionally include outbound links.

NameTypeReqDescription
include_linksboolean
urlstringyes

No output schema declared.

No examples provided.

deep_research ~57

Multi-step research: search the web (Exa), read the top results, and synthesize an answer with [n] citations. Requires EXA_API_KEY.

NameTypeReqDescription
num_sourcesnumber
questionstringyes

No output schema declared.

No examples provided.

extract_from_page ~56

Fetch a page and extract structured data from it as JSON, following your instruction (e.g. "extract the product name, price, and rating").

NameTypeReqDescription
instructionstringyeswhat to extract
urlstringyes

No output schema declared.

No examples provided.

web_search ~46

Semantic web search via Exa. Returns ranked results (title, url, snippet). Requires EXA_API_KEY.

NameTypeReqDescription
num_resultsnumber
querystringyes

No output schema declared.

No examples provided.

Common questions

What is the io.github.infoinlet-marketplace/mcp-browser-research server?

io.github.infoinlet-marketplace/mcp-browser-research is listed in the public MCP registry as io.github.infoinlet-marketplace/mcp-browser-research. Web browsing & research for AI agents, fetch/read pages, structured extraction, Exa search. This page covers its npm package (@infoinlet/mcp-browser-research).

Is the io.github.infoinlet-marketplace/mcp-browser-research server safe to use?

io.github.infoinlet-marketplace/mcp-browser-research scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.infoinlet-marketplace/mcp-browser-research server expose?

io.github.infoinlet-marketplace/mcp-browser-research exposes 4 tools: browse_url, extract_from_page, web_search, deep_research. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.

Is the io.github.infoinlet-marketplace/mcp-browser-research server still maintained?

io.github.infoinlet-marketplace/mcp-browser-research is still listed as active in the MCP registry. We last reached this channel on 20 September 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.infoinlet-marketplace/mcp-browser-research server under?

io.github.infoinlet-marketplace/mcp-browser-research declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.