Web Intel MCP
Agent-ready web intelligence as a pay-per-call MCP server. Licensing and credits are handled by KeyFlint (offline Ed25519 license check + credit ledger), used here only as the billing backend. Failed fetches are refunded automatically; invalid input is rejected before any debit.
| Tool | Credits | Returns |
|---|---|---|
read_url |
1 | Main content as clean Markdown (nav, footer, cookie banners removed) |
page_metadata |
1 | Title, description, canonical, lang, robots, Open Graph, JSON-LD types, H1-H3, image alt stats |
extract_links |
1 | Deduplicated internal / external links with anchor text |
tech_stack |
2 | Frameworks, CMS, analytics, payments, CDN/hosting, security headers |
seo_audit |
3 | 0-100 score, A-F grade, 16 weighted checks, top 5 fixes |
compare_seo |
3 x URLs | Ranks 2-5 pages (you vs competitors); only fetched URLs are billed |
pricing, credits_balance |
free | Price list, remaining credits |
Prices are overridable: WEB_INTEL_PRICES="seo_audit=5,read_url=2".
Install
All you need is your KeyFlint license (LIC-...). The gateway URL, its public key and the checkout link have defaults.
Claude Desktop, one click: download web-intel-mcp-X.Y.Z.mcpb from the latest release, double-click it and paste your license. No terminal, no JSON.
Claude Code:
claude mcp add web-intel -e KEYFLINT_LICENSE=LIC-... -- uvx web-intel-mcp
Cursor, Windsurf, Claude Desktop (JSON):
{
"mcpServers": {
"web-intel": {
"command": "uvx",
"args": ["web-intel-mcp"],
"env": { "KEYFLINT_LICENSE": "LIC-..." }
}
}
}
Optional: KEYFLINT_URL, KEYFLINT_PUBLIC_KEYS (fetched from the gateway and cached in ~/.keyflint/keyring.json when unset), KEYFLINT_CHECKOUT_URL.
Hosted mode (sellers)
Paid logic stays on your server. One process bills many buyers; each request carries the buyer's license.
docker build -t web-intel .
docker run -p 8080:8080 \
web-intel
Buyers connect to https://<host>/mcp (Streamable HTTP, stateless) with
Authorization: Bearer LIC-... (or X-License-Key). Missing or forged licenses get -32060.
Billing flow per call
- URL validated (http/https only). Bad input: error, nothing charged.
- Offline Ed25519 license check (
keyflint-verify), cached 60 s. POST /api/v1/quota/deductwith a fresh idempotency key. Out of credits:-32062with the checkout link.- Fetch + analysis. If anything fails:
POST /api/v1/quota/refund(same key), the client getsisError.
Safety
Requests to private, loopback and link-local addresses are refused (checked on every redirect hop),
responses are capped at 3 MB (WEB_INTEL_MAX_BYTES), 15 s timeout (WEB_INTEL_TIMEOUT), max 5 redirects.
WEB_INTEL_ALLOW_PRIVATE=1 disables the address check (tests only).
Tests
End-to-end with a fake KeyFlint quota gateway, locally signed licenses and a local test site (no network needed):
pip install -e ".[test]"
python -m pytest -q
License
Business Source License 1.1. Source available; production use needs a KeyFlint license (or must be non-commercial). Each version becomes Apache 2.0 four years after release. See LICENSE.
Metadata
Release files for web-intel-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| web_intel_mcp-0.1.0.tar.gz | 20.7 kB | With provenance | Details for web_intel_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| web_intel_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for web_intel_mcp-0.1.0-py3-none-any.whl |
Total release size: 38.0 kB
Release files / web_intel_mcp-0.1.0.tar.gz
| Download URL | web_intel_mcp-0.1.0.tar.gz |
|---|---|
| Size | 20.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
634cf03e10632bcab0eda92b2900513a0e097093afb562333a3689da6a2fd353
|
|
BLAKE2b-256 checksum How to use checksums |
17145ee88016a40b2552e821df7d4c9c367dc0ea192131326aed9a6958e5abea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / web_intel_mcp-0.1.0-py3-none-any.whl
| Download URL | web_intel_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 17.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc78426057e902ec6f606c9d74fcbb126435f71072a9bff08a50a085b87578ca
|
|
BLAKE2b-256 checksum How to use checksums |
7dd1206f57f0e923b739d45db1801c2a1eb6a23cd0afaa311c9a45894f2f41f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logSecurity for web-intel-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for web_intel_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.