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 Intel

PYPI · WEB-INTEL-MCP · 2 COMPONENTS

Web pages to clean Markdown, metadata, links, tech stack and scored SEO audits. Pay per call.

−8 this week 68 Trust /100

Last scanned (13 hours ago)

Scores higher than 61% of PyPI servers

Category Marketing and SEO

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ArceeDev/web-intel-mcp). View diagnostics → Pass
  • License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 425 tokens (~47/item across 9 items; 8 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 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
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (16)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 +1

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

  • 15 Nov 26 −11
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.30 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
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 21 Nov 2026 · Analysed pypi/web-intel-mcp@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo ArceeDev/web-intel-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ArceeDev/web-intel-mcp/.github/workflows/release.yml@refs/tags/v0.2.1
Rekor log index 3906624213
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:ed031d1d40246dd652298513291143e9e5eb9bbfec91eb72ec25c759b3821935

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 35 packages
Packages resolved 35
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~341 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
compare_seo ~61

Audit 2-5 pages (e.g. you vs competitors) and rank them. Costs seo_audit price x number of URLs. Unreachable URLs are reported, not billed: their share is refunded as one batch.

NameTypeReqDescription
urlsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

credits_balance ~19

Remaining credits on your KeyFlint license. Free.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

extract_links ~40

Internal and external links on a page (deduplicated, absolute URLs, anchor text).

NameTypeReqDescription
limitinteger––
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

page_metadata ~42

Title, description, canonical, lang, robots, Open Graph, JSON-LD types, H1-H3 and image alt stats.

NameTypeReqDescription
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

pricing ~20

Credit price of each tool and where to buy credits. Free.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

read_url ~82

Fetch a web page and return its main content as clean Markdown (nav, ads and cookie banners removed). Args: url: Page URL (https:// is assumed when no scheme is given). max_chars: Cap on returned markdown length (default 20000, max 100000).

NameTypeReqDescription
max_charsinteger––
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

seo_audit ~43

Scored on-page SEO audit (0-100, A-F) with 16 weighted checks and the top fixes to apply first.

NameTypeReqDescription
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

tech_stack ~34

Detect frameworks, CMS, analytics, payments, CDN/hosting and security headers of a site.

NameTypeReqDescription
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Web Intel MCP server?

Web Intel runs locally as a PyPI package, launched with uvx web-intel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · web-intel-mcp

# add to Claude Code
claude mcp add arceedev-web-intel-mcp -- uvx web-intel-mcp
Common questions

What is the Web Intel MCP server?

Web Intel is an MCP server listed in the public MCP registry as io.github.ArceeDev/web-intel-mcp. Web pages to clean Markdown, metadata, links, tech stack and scored SEO audits. Pay per call. This page covers its PyPI package (web-intel-mcp).

Is the Web Intel MCP server safe to use?

Web Intel scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Intel MCP server expose?

Web Intel exposes 8 tools: read_url, page_metadata, extract_links, tech_stack, seo_audit, and 3 more. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.

Is the Web Intel MCP server still maintained?

Web Intel is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Web Intel MCP server under?

Web Intel declares the BUSL-1.1 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.

What did VerifyMCP test on the Web Intel MCP server?

VerifyMCP ran 16 checks on Web Intel, covering Known CVEs, Install scripts, Dependency health, Source repository and 12 more. One item could not be completed, a gap on our side rather than a finding about Web Intel: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.