Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Fodda Synthetic Expert Consult

REMOTE · MCP.FODDA.AI · SCANNED AUG 3

Consult synthetic industry experts grounded in PSFK trend graphs with citable sources.

Available components

+14 this week 68 Trust /100
Trust breakdown (6 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 →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability50
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (poor).Fail
  • Context-footprint check failed: tool/resource definitions use about 6974 tokens (~435/item across 16 items; 13 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.fodda.ai

# add to Claude Code
claude mcp add --transport http ai-fodda-expert-consult https://mcp.fodda.ai/expert-consult
# ~/.codex/config.toml
[mcp_servers.ai-fodda-expert-consult]
url = "https://mcp.fodda.ai/expert-consult"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-fodda-expert-consult": {
      "type": "remote",
      "url": "https://mcp.fodda.ai/expert-consult",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-fodda-expert-consult --url https://mcp.fodda.ai/expert-consult --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-fodda-expert-consult:
    url: "https://mcp.fodda.ai/expert-consult"
// mcp.json
{
  "mcpServers": {
    "ai-fodda-expert-consult": {
      "type": "http",
      "url": "https://mcp.fodda.ai/expert-consult"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Aug 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: fair → poor functional
  • 1 Aug 26 +1

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

  • 31 Jul 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1

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

  • 29 Jul 26 0
    • Tool “consult_analyst” rewrote its description, which is the text the model reads security
    • Tool “list_analysts” rewrote its description, which is the text the model reads security
    • Schema quality: good → fair functional
    • “consult_analyst” reworded the description of “analyst_id” cosmetic
    • “consult_analyst” reworded the description of “company” cosmetic
  • 28 Jul 26 +11
    • Transport: fail → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 491 → 428 functional
    • Stability: unverified → 0.03 functional
    • New tool “get_capabilities” functional
  • 27 Jul 26 54

    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 3 Aug 2026 · Probed https://mcp.fodda.ai/expert-consult

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.fodda.ai CN=WR3,O=Google Trust Services,C=US 24 Jul 2026 22 Oct 2026 RSA 2048 SHA256-RSA 327a89c0ad6224d8102712bc19dab6f4
SANs: mcp.fodda.ai
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
DNSSEC insecure

Validation of mcp.fodda.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
fodda.ai. 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
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.fodda.ai/expert-consult Verified 200
http (plaintext) http://mcp.fodda.ai/expert-consult HTTPS enforced 302 https://mcp.fodda.ai/expert-consult
MCP tools — 13 exposed · ~3,131 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.

Tool Tokens
check_deliverable_status ~108

Poll a deliverable commissioned with request_deliverable. Pass the job_id from that response. Returns the current status ("working" | "completed" | "failed") and, once completed, the artifact links to present to the user. Polling is free. Deliverables typically take a few minutes — poll every ~15–30s.

NameTypeReqDescription
job_idstringyesThe job_id returned by request_deliverable.
userIdstringOptional user identifier.

No output schema declared.

No examples provided.

consult_analyst ~425

Consult a named Synthetic Analyst who answers in their expert voice using their curated knowledge graph — one-off questions or multi-turn engagements (pass session_id back to continue). Each analyst has a unique methodology, domain expertise, and analytical lens that produces insights distinct from generic search or standard graph queries. For company-specific executives (e.g. "Nike CMO", "Apple CEO", "Target CFO"), you can pass analyst_id: "brand-cmo" with company: "Nike", or pass analyst_id: "Nike CMO" directly (auto-resolves to analyst_id: "brand-cmo" and company: "Nike"). Call list_analysts first to discover available analyst_id values. Responses may include a coverage status (in/adjacent/out), source attribution, and referrals to other expert graphs. Referrals MUST be presented in third-person platform voice (not the expert's voice) with an offer to query the referred graph. The analyst researches on your behalf: they can search Fodda's graphs, earnings intelligence, and supplemental data mid-consultation, and may refer or consult other analysts. Their research reads bill to you at standard rates ($0.50/call) and are itemized in `sources_used`.

NameTypeReqDescription
analyst_idstringyesThe analyst ID (e.g., 'ben-dietz-sic', 'brand-cmo'). Also accepts company-specific alias queries like 'Nike CMO', 'Apple CEO', or 'Starbucks CFO'.
companystringOptional company name or stock ticker (e.g., 'Nike', 'Tesla', or 'TSLA') to bind the analyst to a specific brand context. Automatically extracted if included in analyst_id (e.g. 'Nike CMO').
querystringyesThe question or topic to discuss with the analyst
session_idstringPass the session_id from a previous consult response to continue that engagement — the analyst keeps context and follow-ups cost less. Omit for a one-off question.
userIdstringOptional user identifier.

No output schema declared.

No examples provided.

generate_visual ~247

Create a presentation-ready data visualization from research findings. Available chart types: "cultural_shifts" (From→To transitions), "competitive_compass" (brands on 2 axes), "trend_constellation" (network of related trends), "implication_ladder" (Signal→Trend→So What→Do What), "innovation_pathway" (Now→Near-Term→Future), "opportunity_map" (2×2 white space analysis). Returns a branded SVG that renders directly in the chat.

NameTypeReqDescription
chart_typestringyesThe type of visualization to generate
datastringyesJSON string containing the chart data. Structure depends on chart_type. cultural_shifts: {shifts:[{from,to}]}. competitive_compass: {brands:[{name,x,y}], axes:{left,right,top,bottom}}. trend_constell…

No output schema declared.

No examples provided.

get_capabilities ~58

Returns Fodda's main capabilities / features / offerings / products / services / tools and what they cost. Call this for any question about what Fodda can do or what's available.

NameTypeReqDescription
userIdstringOptional user identifier.

No output schema declared.

No examples provided.

get_evidence ~315

Get the source articles, case studies, and statistics behind a specific trend — with full citations and publisher attribution. Each item includes source URL, location, brand names, publication date, category, and a formatted citation. Use after search_graph when you need the supporting proof behind a trend. This is a direct lookup by trend ID — not a text search tool.

NameTypeReqDescription
for_node_idstringyesThe node_id from a prior search_graph result (e.g. '2507.0'). MUST come from the search result's node_id field. Node IDs are NOT sequential integers — do NOT guess or invent IDs like '1', '2', '3'. D…
graphIdstringyesThe graph ID. Use list_graphs to see all options. Examples: 'retail', 'tech', 'food', 'travel', 'beauty', 'sports', 'sic', 'pew', 'ce-design', 'ezra-eeman-wayfinder', 'dhl-ecommerce-trends-2026', 'au…
top_knumberNumber of evidence items to return (default 5)
userIdstringOptional user identifier for trial usage tracking.

No output schema declared.

No examples provided.

get_label_values ~297

List all brands, locations, technologies, audiences, or trends within a specific knowledge graph. Use to explore what a graph contains — e.g., "what brands are in the retail graph?" or "what locations does the fashion graph cover?". To get a complete list of every trend in a graph, call with label="Trend" — this returns the full deterministic list, useful for industry-report graphs where search may return partial results.

NameTypeReqDescription
graphIdstringyesThe graph ID. Use list_graphs to see all options. Examples: 'retail', 'tech', 'food', 'travel', 'beauty', 'sports', 'sic', 'pew', 'ce-design', 'ezra-eeman-wayfinder', 'dhl-ecommerce-trends-2026', 'au…
labelstringyesThe label to fetch values for (e.g., 'Brand', 'Location', 'Technology', 'Audience', 'RetailerType', 'Trend')
propertystringOptional property to return values for. Defaults vary by label.
userIdstringOptional user identifier for trial usage tracking.

No output schema declared.

No examples provided.

get_my_account ~74

Check the current user's account status: API call balance, plan, enabled/disabled graphs, and profile info. Use when the user asks "how many API calls do I have?", "what plan am I on?", "what graphs can I access?", or similar account questions. Returns live data — not cached from session start.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_neighbors ~406

Discover what's connected to a specific trend — related brands, technologies, locations, and cross-domain links that search alone wouldn't surface. Returns curated editorial connections between trends that web search cannot provide. Use after search_graph to map the territory around a trend, find which brands are connected, or understand cross-domain relationships. Requires node_id from a prior search_graph result.

NameTypeReqDescription
depthnumberTraversal depth (default 1, max 2)
directionstringTraversal direction: 'out' (default) follows outgoing edges, 'in' follows incoming edges
graphIdstringyesThe graph ID. Use list_graphs to see all options. Examples: 'retail', 'tech', 'food', 'travel', 'beauty', 'sports', 'sic', 'pew', 'ce-design', 'ezra-eeman-wayfinder', 'dhl-ecommerce-trends-2026', 'au…
limitnumberMaximum results (default 50)
relationship_typesarrayFilter by relationship types: 'EVIDENCED_BY', 'RELATED_TO', 'SEMANTICALLY_SIMILAR', 'ASSOCIATED_BRAND', 'MENTIONS_BRAND', 'IN_LOCATION'
seed_node_idsarrayyesArray of node IDs to start traversal from. MUST be actual node_id values from a prior search_graph result (e.g. ["2507.0"]). Node IDs are NOT sequential integers — do NOT guess or invent IDs like "1"…
userIdstringOptional user identifier for trial usage tracking.

No output schema declared.

No examples provided.

get_node ~282

Get the full profile of a specific trend — detailed description, lifecycle stage (emerging/building/mature), signal strength, geographic scope, and all properties. Use when you need deeper detail on a single trend after search_graph returned a summary. Requires node_id from a prior search_graph result.

NameTypeReqDescription
graphIdstringyesThe graph ID. Use list_graphs to see all options. Examples: 'retail', 'tech', 'food', 'travel', 'beauty', 'sports', 'sic', 'pew', 'ce-design', 'ezra-eeman-wayfinder', 'dhl-ecommerce-trends-2026', 'au…
nodeIdstringyesThe node_id from a prior search_graph result (e.g. '2507.0'). MUST come from the search result's node_id field. Node IDs are NOT sequential integers — do NOT guess or invent IDs like '1', '2', '3'. D…
userIdstringOptional user identifier for trial usage tracking.

No output schema declared.

No examples provided.

list_analysts ~97

Lists available synthetic analyst personas (e.g. brand-cmo, brand-ceo, brand-cfo). To query a company-specific synthetic expert (e.g., "Nike CMO", "Apple CMO", "Adidas CEO"), consult brand-cmo (or relevant role ID) and supply the target company name in the company parameter (e.g. company: "Nike").

NameTypeReqDescription
userIdstringOptional user identifier.

No output schema declared.

No examples provided.

list_graphs ~108

List all knowledge graphs the user can access — IDs, descriptions, authors, sectors, signal counts. Use FIRST in any session to discover available sources before searching. Returns graph metadata needed for graphId parameters in other tools. Deprecated: waldo, psfk (use retail/tech/food/travel/fashion/beauty/sports instead).

NameTypeReqDescription
userIdstringOptional user identifier. Authenticated users are identified automatically via API key. For trial users, this helps track usage.

No output schema declared.

No examples provided.

request_deliverable ~286

Commission a finished document from an analyst — a skill-based deliverable like a marketing plan, deck review, or trend briefing. Specify offering_key (see the `offerings` list on each analyst from list_analysts), a brief (2–5 sentences: audience, goal, constraints), and optional attachments. The analyst researches on your behalf, then produces the document in the background. Returns a job_id — poll with check_deliverable_status until status is "completed" to get the artifact links. The offering price is charged on acceptance; the analyst's research is included, not billed separately. Example brief: "Marketing plan for a DTC skincare launch targeting Gen-Z, $50k budget, 90-day horizon."

NameTypeReqDescription
analyst_idstringyesThe analyst ID producing the deliverable (e.g., 'ben-dietz-sic'). See list_analysts.
attachmentsarrayOptional supporting text files mounted into the analyst's workspace (max 5).
briefstringyes2–5 sentences: audience, goal, constraints. Agents imitate the example in the tool description — be concrete.
offering_keystringyesThe offering to commission (e.g., 'marketing_plan'). See the `offerings` array on each analyst from list_analysts.
userIdstringOptional user identifier.

No output schema declared.

No examples provided.

search_graph ~428

Find trends, signals, and expert insights across 100+ curated knowledge graphs covering retail, beauty, tech, food, travel, sports, and 30+ specialist domains. Returns trend data with cited evidence, source attribution, and lifecycle stage (emerging/building/mature/fading) — not generic web summaries. If graphId is omitted, searches ALL accessible graphs in parallel (recommended default). Use for market trends, competitor analysis, innovation signals, consumer behavior, cultural shifts, or any topic where curated expert intelligence outperforms web search.

NameTypeReqDescription
graphIdstringOptional graph ID. If omitted, searches ALL accessible graphs. Examples: 'retail', 'tech', 'food', 'travel', 'beauty', 'sports', 'sic', 'pew', 'ce-design', 'ezra-eeman-wayfinder', 'dhl-ecommerce-tren…
include_evidencebooleanIf true, batch-fetch supporting evidence articles inline with results. Default: true.
limitnumberMaximum number of results (default 10, max 50)
modestringExecution mode: "research" for topic research (15 API calls), "compare" for upload & compare intelligence (20 API calls). Defaults to "research".
querystringyesThe search query. Location terms are auto-detected and used to filter results geographically.
skip_skillsbooleanIf true, skip applying any enabled skills (Paralogy, Igloo, etc.) for this query only. Use when the user says "without skills", "skip Paralogy", or "just the raw results". Default: false.
use_semanticbooleanWhether to use semantic search (default true)
userIdstringOptional user identifier for trial usage tracking.

No output schema declared.

No examples provided.