# Frasma (remote · www.frasma.org)

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

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `www.frasma.org`: 87/100 (this document), [markdown](https://verifymcp.io/servers/francemazzi-frasma/api-mcp.md), [page](https://verifymcp.io/servers/francemazzi-frasma/api-mcp)

## Channel facts

- Endpoint: `https://www.frasma.org/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 769 tokens (~153/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Frasma MCP server?

Frasma is a hosted endpoint at https://www.frasma.org/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http francemazzi-frasma 'https://www.frasma.org/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "francemazzi-frasma": {
      "url": "https://www.frasma.org/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "francemazzi-frasma": {
      "type": "http",
      "url": "https://www.frasma.org/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.francemazzi-frasma]
url = "https://www.frasma.org/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "francemazzi-frasma": {
      "type": "remote",
      "url": "https://www.frasma.org/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add francemazzi-frasma --url 'https://www.frasma.org/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  francemazzi-frasma:
    url: "https://www.frasma.org/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "francemazzi-frasma": {
      "Transport": "http",
      "Url": "https://www.frasma.org/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add francemazzi-frasma -t streamable-http -u 'https://www.frasma.org/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "francemazzi-frasma": {
      "type": "http",
      "url": "https://www.frasma.org/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 87, +1)

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

### 2026-09-18 (score 86, +1)

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

### 2026-09-16 (score 85, +1)

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

### 2026-09-14 (score 84, +1)

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

### 2026-09-11 (score 83, +1)

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

### 2026-09-09 (score 82, +1)

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

### 2026-09-07 (score 81, +1)

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

### 2026-09-05 (score 80, +1)

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

## MCP tools (5)

### `get_frasma_profile` (~49 tokens)

Get Frasma profile

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

Input parameters:

- `locale` (string): Response language: it or en. Defaults to it.

Output parameters:

- `commercialLimits` (array)
- `description` (string)
- `discovery` (object)
- `focus` (array)
- `founder` (string)
- `kind` (string)
- `languages` (array)
- `location` (string)
- `name` (string)
- `sectors` (array)

### `search_frasma_knowledge` (~106 tokens)

Search Frasma knowledge

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

Input parameters:

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

Output parameters:

- `results` (array): Ranked knowledge matches for the query.

### `get_diagnostic_framework` (~43 tokens)

Get diagnostic framework

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

Input parameters:

- `locale` (string): Response language: it or en. Defaults to it.

Output parameters:

- `commercialLimits` (array)
- `fitCriteria` (array)
- `introduction` (string)
- `poorFitCriteria` (array)
- `steps` (array)
- `title` (string)

### `prepare_diagnostic_summary` (~409 tokens)

Prepare diagnostic summary handoff

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.

Input parameters:

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

Output parameters:

- `completeness` (object)
- `handoff` (object)
- `ok` (boolean)
- `summary` (object)

### `prepare_project_brief` (~162 tokens)

Prepare process brief handoff

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.

Input parameters:

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

Output parameters:

- `brief` (object)
- `handoff` (object)
- `ok` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/francemazzi-frasma/api-mcp#diagnostics

## Score history

- 2026-09-21: 87
- 2026-09-20: 87
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 83
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 80
- 2026-09-05: 80
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 78
- 2026-09-01: 78
- 2026-08-31: 77
- 2026-08-30: 77
- 2026-08-29: 76
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 75
- 2026-08-25: 73

## Common questions

### What is the Frasma MCP server?

Frasma is an MCP server listed in the public MCP registry as io.github.francemazzi/frasma. Read-only Frasma MCP: profile, knowledge search, diagnostic handoff. No email. This page covers its hosted endpoint (https://www.frasma.org/api/mcp).

### Is the Frasma MCP server safe to use?

Frasma scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Frasma MCP server expose?

Frasma exposes 5 tools: get_frasma_profile, search_frasma_knowledge, get_diagnostic_framework, prepare_diagnostic_summary, prepare_project_brief. Their descriptions and schemas cost roughly 769 tokens of context every time the server is loaded.

### Does the Frasma MCP server require authentication?

No. We connected to Frasma without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Frasma MCP server still maintained?

Frasma is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.frasma.org/api/mcp
- Repository: https://github.com/francemazzi/frasma
- Website: https://www.frasma.org/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/francemazzi-frasma/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/francemazzi-frasma/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/francemazzi-frasma/api-mcp