Frasma

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Read-only Frasma MCP: profile, knowledge search, diagnostic handoff. No email.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Frasma": {
      "url": "https://www.frasma.org/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• get_frasma_profile read-only

  Returns the verified public profile, focus areas, sectors, commercial boundaries, and discovery URLs for Frasma.

  Parameters:

  • locale — string — Response language: it or en. Defaults to it.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• search_frasma_knowledge read-only

  Searches verified Frasma services, sectors, case studies, methodology, fit criteria, and commercial boundaries. Use before making factual claims.

  Parameters:

  • query (required) — string — Search query for verified Frasma knowledge, e.g. DDT ERP or HACCP procedures.
  • locale — string — Response language: it or en. Defaults to it.
  • pagePath — string — Optional canonical site path to scope results, e.g. /servizi/ddt-erp.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_diagnostic_framework read-only

  Returns the diagnostic method, evidence to collect, fit criteria, and commercial limits.

  Parameters:

  • locale — string — Response language: it or en. Defaults to it.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• prepare_diagnostic_summary read-only

  Validates a complete diagnostic summary and returns a handoff payload. Does not send email. Map the diagnosis to a process brief; the user must confirm before POST /api/request-process-assessment.

  Parameters:

  • clientName (required) — string — Client full name.
  • clientEmail (required) — string — Client work email.
  • sector (required) — string — Business sector, e.g. manufacturing or food quality.
  • process (required) — string — Short name of the process under diagnosis, e.g. delivery notes into ERP.
  • currentWorkflow (required) — string — How the process is done today, including people, tools, and handoffs.
  • bottlenecks (required) — array — Observed bottlenecks, one item per string.
  • currentSystems (required) — array — Systems already in use, e.g. email, PDF, Mago Zucchetti.
  • volumesAndFrequency (required) — string — Volumes and frequency, e.g. about 40 DDT per day.
  • baselineMetrics (required) — array — Baseline metrics before any Frasma work, e.g. minutes per document.
  • dataAvailable (required) — array — Data that can be shared for a prototype, preferably anonymized samples.
  • constraints (required) — array — Hard constraints, e.g. human validation before ERP import.
  • desiredOutcomes (required) — array — Desired outcomes without invented savings or guarantees.
  • needCategories (required) — array — One or more Frasma need categories that fit the diagnosis.
  • opportunities (required) — array — Concrete opportunities that follow from the evidence.
  • recommendations (required) — array — Recommended next steps for a limited prototype or discovery.
  • openQuestions (required) — array — Open questions still to confirm with the client.
  • nextSteps (required) — array — Agreed next steps after reviewing this summary.
  • language (required) — string — Language of the diagnostic summary: it or en.
  • honeypot — string — Anti-spam trap. Must be empty or omitted.
  • clientCompany — string — Client company name, if known.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• prepare_project_brief read-only

  Validates the process brief used for a quote (name, email, process, optional company/role/systems/volume). Does not send email. The user must confirm before POST /api/request-process-assessment.

  Parameters:

  • name (required) — string — Client full name.
  • clientEmail (required) — string — Client work email.
  • process (required) — string — Process to evaluate, at least 20 characters: trigger, work today, and desired outcome.
  • role — string — Client role, if known.
  • volume — string — Volumes or frequency, e.g. 80 documents per week.
  • company — string — Client company name, if known.
  • systems — string — Systems already in use, e.g. Outlook and ERP.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.