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.

Web Research Agent

REMOTE · WEB-RESEARCH-AGENT-MCP.MCPIZE.RUN

Company profiles, site audits and page-to-JSON extraction for AI agents.

60 Trust /100

Last scanned (21 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Web Scraping

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security51
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 400 tokens (~66/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 40% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 4 Nov 26 +1

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

  • 3 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Nov 26 59

    First indexed and scored.

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 4 Nov 2026 · Probed https://web-research-agent-mcp.mcpize.run/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcpize.run CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 460e91290e7a30310ed14847bc47d7e2
SANs: mcpize.run, *.mcpize.run
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of web-research-agent-mcp.mcpize.run. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
run. present 37315 8 Verified
mcpize.run. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://web-research-agent-mcp.mcpize.run/mcp Verified 200
http (plaintext) http://web-research-agent-mcp.mcpize.run/mcp Inconclusive 405
MCP tools · 6 exposed · ~400 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
company_profile ~47

Research a company from its website: name, description, socials, emails, key pages, pricing mentions, tech stack.

NameTypeReqDescription
urlstringyesCompany website, e.g. stripe.com

No output schema declared.

No examples provided.

email_check ~78

Validate an email address or domain via live DNS: syntax, MX/null-MX, SPF, DMARC policy, disposable/free/role flags, deliverability verdict and 0-100 score. No SMTP probe.

NameTypeReqDescription
domainstring–Or a domain, e.g. stripe.com
emailstring–Email address to check

No output schema declared.

No examples provided.

page_diff ~84

Monitor a page for changes: returns normalized text + SHA-256 content_hash; pass previous_text (or previous_hash) from an earlier call to get changed flag and added/removed lines.

NameTypeReqDescription
previous_hashstring––
previous_textstring––
selectorstring–Optional #id to limit to one element
urlstringyes–

No output schema declared.

No examples provided.

page_to_json ~51

Fetch a web page and return structured JSON: meta, Open Graph, JSON-LD, headings, links, images, clean text.

NameTypeReqDescription
max_textinteger––
urlstringyes–

No output schema declared.

No examples provided.

site_audit ~50

Audit a web page: SEO, performance hints, security headers, broken internal links; returns score 0-100 and issues.

NameTypeReqDescription
max_linksinteger––
urlstringyes–

No output schema declared.

No examples provided.

sitemap_urls ~90

List a site's URLs from its sitemaps (robots.txt Sitemap: lines, nested indexes, text sitemaps) with lastmod/changefreq/priority; optional since date filter.

NameTypeReqDescription
limitinteger––
max_sitemapsinteger––
sincestring–ISO date; only URLs with lastmod >= since
urlstringyesSite or sitemap URL

No output schema declared.

No examples provided.

Install

How do I install the Web Research Agent MCP server?

Web Research Agent is a hosted endpoint at https://web-research-agent-mcp.mcpize.run/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · web-research-agent-mcp.mcpize.run

# add to Claude Code
claude mcp add --transport http elaysuu-web-research-agent-mcp 'https://web-research-agent-mcp.mcpize.run/mcp'
Common questions

What is the Web Research Agent MCP server?

Web Research Agent is an MCP server listed in the public MCP registry as io.github.elaysuu/web-research-agent-mcp. Company profiles, site audits and page-to-JSON extraction for AI agents. This page covers its hosted endpoint (https://web-research-agent-mcp.mcpize.run/mcp).

Is the Web Research Agent MCP server safe to use?

Web Research Agent scores 60 out of 100 on VerifyMCP. 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 Web Research Agent MCP server expose?

Web Research Agent exposes 6 tools: company_profile, site_audit, page_to_json, email_check, sitemap_urls, page_diff. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.

Does the Web Research Agent MCP server require authentication?

No. We connected to Web Research Agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Web Research Agent MCP server still maintained?

Web Research Agent is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.