Fodda MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Fodda curated knowledge-graph queries: Does OAuth replace deprecated query-string authentication without confusing per-user graph access?

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

Best fit

Expert-curated knowledge-graph and synthetic-analyst access for industry intelligence.

What we know

MCP/REST surface over Fodda's expert-curated knowledge graphs, search, synthetic analysts and brand-intelligence services.

Maintenance / activity evidence

fodda-mcp 1.46.97 published 2026-10-04T03:43:29.786Z

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.
Primarily read/search/analysis, with provider-side profile/build operations. Writes: Build brand-intelligence profile where tool/API supports it.
API key or payment authorization.
Sensitive access: Market/brand research queries, API credentials

Mostly data retrieval; cost controls and source provenance matter.

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

All limitations / Review context

Does OAuth replace deprecated query-string authentication without confusing per-user graph access?

The bounded review of the publisher's documented Fodda curated knowledge-graph queries 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.

Mostly data retrieval; cost controls and source provenance matter.
Primarily read/search/analysis, with provider-side profile/build operations.
API key or payment authorization.
Queries and graph results are processed by Fodda.
Reviewed write actions: Build brand-intelligence profile where tool/API supports it
Sensitive access: Market/brand research queries, API credentials
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.
Requires API key or machine-payment flow for paid use.
Calls are billed/limited by plan.
Knowledge quality/coverage depends on curated graph sources.

Original activity observations

fodda-mcp 1.46.97 published 2026-10-04T03:43:29.786Z

Technical identity

npm/fodda-mcp

Exact implementation source: https://www.npmjs.com/package/fodda-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:fodda-mcp
Service endpoint: https://api.fodda.ai/v1

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 metadata ↗
fodda-mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
www.fodda.ai/api
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
www.fodda.ai/agents
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Publisher explicitly deprecates URL query-string authentication (401); use OAuth or Bearer header
The query-string API key URL mode is deprecated (401). Use OAuth or Authorization Bearer; keep secrets out of URLs.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Publisher explicitly deprecates URL query-string authentication (401); use OAuth or Bearer header | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions
claude mcp add --transport http fodda https://mcp.fodda.ai/mcp
Configure / authenticate
MCP100 setup guide
OAuth remote or publisher-issued personal connector URL; legacy query-string authentication is deprecated.
Check connection
Suggested check
Check auth and read-only account/tool listing; avoid launching paid research as test.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `fodda`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove fodda

Official Documentation & Sources

What it does

MCP/REST surface over Fodda's expert-curated knowledge graphs, search, synthetic analysts and brand-intelligence services.

Capability: Data & Databases
Resource type: MCP Server
Industry: Retail & E-commerce, Media & Marketing, Sports & Entertainment
Best fit: Expert-curated knowledge-graph and synthetic-analyst access for industry intelligence.

Representative uses

Search curated graph data
List available graph catalogs
Ask synthetic analysts
Build/query brand-intelligence profiles

Limitations

Requires API key or machine-payment flow for paid use.
Calls are billed/limited by plan.
Knowledge quality/coverage depends on curated graph sources.

Reviewed access

Access & risk

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

Authentication: API key or payment authorization.
Permissions: Primarily read/search/analysis, with provider-side profile/build operations.
Data handling: Queries and graph results are processed by Fodda.
Cost: usage_based
Risk and cautions: Mostly data retrieval; cost controls and source provenance matter.

Access scope and cautions

Write actions: Build brand-intelligence profile where tool/API supports it
Sensitive access: Market/brand research queries API credentials
Risk level: moderate

FAQ

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

Which tasks are documented for this implementation?

The reviewed tasks include: Search curated graph data; List available graph catalogs; Ask synthetic analysts; Build/query brand-intelligence profiles.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y fodda-mcp. Recorded endpoint: https://api.fodda.ai/v1. Recorded transport: stdio. Recorded environment-variable notes: FODDA_API_KEY. No configuration values are supplied here. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: API key or supported machine-payment flow.

Can it modify data or perform write operations?

Documented write actions include: Build brand-intelligence profile where tool/API supports it. Recorded permission boundary: Primarily read/search/analysis, with provider-side profile/build operations.

What data-handling boundary should I consider?

Queries and graph results are processed by Fodda. Recorded sensitive-access context: Market/brand research queries; API credentials.

What limitations and risks should I check before use?

Mostly data retrieval; cost controls and source provenance matter. Requires API key or machine-payment flow for paid use. Calls are billed/limited by plan. Knowledge quality/coverage depends on curated graph sources. 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.