Fraise
OCI · GHCR.IO/FRAISEHQ/FRAISE
Memory database for AI agents: remember and recall over a running Fraise daemon, in FQL.
Available components
Last scanned (4 hours ago)
Scores higher than 97% of OCI servers
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to FraiseHQ/fraise). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 497 tokens (~248/item across 2 items; 2 tools + 0 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 Management60
- Stability observed for 18 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 0
- Package version: 0.3.5 → 0.3.6 functional
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.3.4 → 0.3.5 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed oci/ghcr.io/fraisehq/fraise@0.3.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | FraiseHQ/fraise |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/FraiseHQ/fraise/.github/workflows/docker.yaml@refs/tags/v0.3.6 |
| Rekor log index | 3616453117 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:1894013dcd09ca67d0b74bac965c8e5619b369fe856ac37ba998133b1b038f24 |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
recall ~358
Search the agent's long-term memory: run an FQL recall against the fraise daemon and return the matching facts ranked by relevance and recency. Anchors alone — topic:/entity: with no search terms and no vector — seed the search with every fact filed under them, scored one unit per named anchor and decayed by age, newest first under a single anchor: the way to see what is stored under a topic before you know what to search for.
| Name | Type | Req | Description |
|---|---|---|---|
| parameters | object | – | Out-of-band vector bindings: one array of numbers per vec:$name placeholder the query references. |
| query | string | yes | A full FQL recall: search terms, then optional topic:/entity: anchors (beside terms they lift the facts filed under them through the graph and filter nothing, so the recall runs at depth:1 at least),… |
| Name | Type | Req | Description |
|---|---|---|---|
| results | object | yes | Ranked recall results, best first; with anchors alone, each hit scores one unit per named anchor it is filed under, decayed by age — newest first under a single anchor. |
| warnings | array | – | Parse warnings the server attached; the query still ran and the results stand. |
No examples provided.
remember ~139
Store a self-contained fact in the agent's long-term memory: run an FQL remember against the fraise daemon.
| Name | Type | Req | Description |
|---|---|---|---|
| parameters | object | – | Out-of-band vector bindings: one array of numbers per vec:$name placeholder the query references. |
| query | string | yes | A full FQL remember: the fact in single quotes, anchors as repeatable topic:/entity: pairs, @N selecting the graph, vec:$name binding an optional vector. An anchor value that is not letters and digit… |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | The write acknowledgement, the fixed token "ok". A write has no result set to return; this key's presence is what distinguishes an accepted write from a recall that matched nothing. |
| warnings | array | – | Parse warnings the server attached; the query still ran and the results stand. |
No examples provided.
How do I install the Fraise MCP server?
Fraise runs locally as a container image, launched with docker run --rm -i ghcr.io/fraisehq/fraise:0.3.6. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/fraisehq/fraise
claude mcp add fraisehq-fraise -- docker run --rm -i ghcr.io/fraisehq/fraise:0.3.6
What is the Fraise MCP server?
Fraise is an MCP server listed in the public MCP registry as io.github.FraiseHQ/fraise. Memory database for AI agents: remember and recall over a running Fraise daemon, in FQL. This page covers its container image (ghcr.io/fraisehq/fraise).
Is the Fraise MCP server safe to use?
Fraise scores 58 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 Fraise MCP server expose?
Fraise exposes 2 tools: recall, remember. Their descriptions and schemas cost roughly 497 tokens of context every time the server is loaded.
Is the Fraise MCP server still maintained?
Fraise is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Fraise MCP server under?
Fraise declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.