FourA MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to FourA HTTP, proxy and browser web retrieval tools: Do typed errors and automatic retrieval choices remain transparent when a request escalates to a full browser?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Reliable public-web retrieval across direct HTTP, proxy rotation and JS-capable browser rendering.

What we know

Web-access MCP whose auto tool chooses direct/proxy/browser fetch paths, with explicit HTTP/proxy/browser tools for more control.

Maintenance / activity evidence

@fouradata/mcp 0.7.3 published 2026-09-22T21:15:41.656Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read/fetch authority over allowed public URLs; server tools are documented read-only.
FourA API key.
Sensitive access: URLs, Custom headers/body, Cookies/session data, Fetched page contents

Open-web retrieval can leak secrets if users pass sensitive headers/URLs; restrict to authorized public targets.
SSRF protections block private/reserved addresses.
Disable session return when not needed.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do typed errors and automatic retrieval choices remain transparent when a request escalates to a full browser?

The bounded review of the publisher's documented FourA HTTP, proxy and browser web retrieval tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Open-web retrieval can leak secrets if users pass sensitive headers/URLs; restrict to authorized public targets.
SSRF protections block private/reserved addresses.
Disable session return when not needed.
Read/fetch authority over allowed public URLs; server tools are documented read-only.
FourA API key.
Target URLs, headers/body and optional session/cookie data are sent through FourA.
Sensitive access: URLs, Custom headers/body, Cookies/session data, Fetched page contents
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Intended for public/authorized content.
SSRF protections reject private/reserved addresses.
Anti-bot solving is not guaranteed.
Usage is credit/rate/concurrency limited.
Browser/proxy responses can include cookies/session data if requested.

Original activity observations

@fouradata/mcp 0.7.3 published 2026-09-22T21:15:41.656Z

Technical identity

npm/@fouradata/mcp

Exact implementation source: https://www.npmjs.com/package/@fouradata/mcp ↗
Reviewed resource type: Gateway
Repository identity: fouradata/mcp
Package identity: npm:@fouradata/mcp
Service endpoint: https://mcp.foura.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@fouradata/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
foura.ai/docs/mcp/server
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
foura.ai/docs/mcp/recipes
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
foura.ai/docs/mcp/errors
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
foura.ai/docs/getting-started/authentication
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Local stdio uses FOURA_API_KEY in env; hosted https://mcp.foura.ai/mcp uses Authorization Bearer.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add foura -- npx -y @fouradata/mcp
Configure / authenticate
MCP100 setup guide
Publisher `claude mcp add foura -- npx -y @fouradata/mcp` with FOURA_API_KEY configured in host env.
Check connection
Suggested check
Inspect tool discovery and non-billable metadata; do not fetch charged pages to validate startup.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `fouradata-mcp`, run `claude mcp remove fouradata-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove fouradata-mcp

Official Documentation & Sources

What it does

Web-access MCP whose auto tool chooses direct/proxy/browser fetch paths, with explicit HTTP/proxy/browser tools for more control.

Capability: Search & Web
Resource type: Gateway
Best fit: Reliable public-web retrieval across direct HTTP, proxy rotation and JS-capable browser rendering.

Representative uses

Fetch public pages/APIs
Bulk-fetch URLs
Render SPAs
Retry blocked targets through rotating proxies
Return browser session data when explicitly requested

Limitations

Intended for public/authorized content.
SSRF protections reject private/reserved addresses.
Anti-bot solving is not guaranteed.
Usage is credit/rate/concurrency limited.
Browser/proxy responses can include cookies/session data if requested.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: FourA API key.
Permissions: Read/fetch authority over allowed public URLs; server tools are documented read-only.
Data handling: Target URLs, headers/body and optional session/cookie data are sent through FourA.
Cost: usage_based
Risk and cautions: Open-web retrieval can leak secrets if users pass sensitive headers/URLs; restrict to authorized public targets.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: URLs Custom headers/body Cookies/session data Fetched page contents
Risk level: moderate
Security notes: SSRF protections block private/reserved addresses. Disable session return when not needed.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which implementation does this page cover?

Web-access MCP whose auto tool chooses direct/proxy/browser fetch paths, with explicit HTTP/proxy/browser tools for more control.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @fouradata/mcp. Recorded endpoint: https://mcp.foura.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: FOURA_API_KEY. No configuration values are supplied here. Prerequisites: MCP client; Node runtime for local mode. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: FourA API key.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read/fetch authority over allowed public URLs; server tools are documented read-only.

What data-handling boundary should I consider?

Target URLs, headers/body and optional session/cookie data are sent through FourA. Recorded sensitive-access context: URLs; Custom headers/body; Cookies/session data; Fetched page contents.

What limitations and risks should I check before use?

Open-web retrieval can leak secrets if users pass sensitive headers/URLs; restrict to authorized public targets. Intended for public/authorized content. SSRF protections reject private/reserved addresses. Anti-bot solving is not guaranteed. Usage is credit/rate/concurrency limited. Browser/proxy responses can include cookies/session data if requested. SSRF protections block private/reserved addresses. Disable session return when not needed. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Is this an official MCP?

FourA is listed as First-party MCP in MCP100’s current evidence.

Why we’re tracking it

Best fit

What we know

Maintenance / activity evidence

Verification gaps / watch-outs

Original activity observations

Evidence & Sources

Gateway setup

Install / connect

Configure / authenticate

Check connection

Remove / uninstall / revoke

Official Documentation & Sources

What it does

Representative uses

Limitations

Access & risk

Access scope and cautions

FAQ