# FactoGraph (remote · api.factograph.app)

Memory for AI agents: facts a person approved, each with a link, and answers that cite them.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

> **Recent critical change**: Authorization (2026-10-22). See the changelog below before you install this server.

## Components

- remote · `api.factograph.app`: 0/100, [markdown](https://verifymcp.io/servers/app-factograph-factograph/api-k-store-id-mcp.md), [page](https://verifymcp.io/servers/app-factograph-factograph/api-k-store-id-mcp)
- remote · `api.factograph.app`: 68/100 (this document), [markdown](https://verifymcp.io/servers/app-factograph-factograph/api-mcp.md), [page](https://verifymcp.io/servers/app-factograph-factograph/api-mcp)

## Channel facts

- Endpoint: `https://api.factograph.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-11-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (startStep).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1797 tokens (~256/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 FactoGraph MCP server?

FactoGraph is a hosted endpoint at https://api.factograph.app/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 app-factograph-factograph 'https://api.factograph.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-factograph-factograph": {
      "url": "https://api.factograph.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-factograph-factograph": {
      "type": "http",
      "url": "https://api.factograph.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-factograph-factograph]
url = "https://api.factograph.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-factograph-factograph": {
      "type": "remote",
      "url": "https://api.factograph.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-factograph-factograph --url 'https://api.factograph.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-factograph-factograph:
    url: "https://api.factograph.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-factograph-factograph": {
      "Transport": "http",
      "Url": "https://api.factograph.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-factograph-factograph -t streamable-http -u 'https://api.factograph.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-factograph-factograph": {
      "type": "http",
      "url": "https://api.factograph.app/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-11-04 (score 68, +1)

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

### 2026-11-01 (score 67, +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.

### 2026-10-30 (score 66, +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.

### 2026-10-28 (score 65, +1)

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

### 2026-10-26 (score 64, +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.

### 2026-10-24 (score 63, +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.

### 2026-10-22 (score 62, −7)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “startStep”, which the server declares destructive
- [security] Tool “createStore” rewrote its description, which is the text the model reads
- [security] Tool “getManual” rewrote its description, which is the text the model reads
- [security] Tool “listFacts” rewrote its description, which is the text the model reads
- [security] Tool “replyToPrompt” is now declared destructive
- [functional regression] Tool coverage: 100% → 93%
- [functional regression] Schema quality: 219 → 256
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “ask” reworded the description of “store”
- [cosmetic] “getManual” reworded the description of “store”
- [cosmetic] “getStep” reworded the description of “store”
- [cosmetic] “listFacts” reworded the description of “store”
- [cosmetic] “replyToPrompt” reworded the description of “store”
- [cosmetic] Tool “ask” changed its title: Ask a public store → Ask a store
- [cosmetic] Tool “getManual” changed its title: Read a public store's manual → Read a store's manual

### 2026-10-21 (score 69)

First indexed and scored.

## MCP tools (7)

### `getManual` (~139 tokens)

Read a store's manual

The store's manual - how to run its steps and cite its facts - and what it holds: how many facts, from which sources. Read it before the store's other tools, and follow it.

Input parameters:

- `store` (string): The store's link, as the person gave it: a public link (https://.../api/p/<id> or https://.../#/public/<id>, or its public id) or the person's private link (https://.../api/k/<id> or https://.../#/st…

### `listFacts` (~132 tokens)

List every fact

Every fact in the store, numbered, each number a link to the fact. Cite a fact as its number with its link, [F3](<link>).

Input parameters:

- `store` (string): The store's link, as the person gave it: a public link (https://.../api/p/<id> or https://.../#/public/<id>, or its public id) or the person's private link (https://.../api/k/<id> or https://.../#/st…

### `ask` (~180 tokens)

Ask a store

Ask a question; the store answers only from its facts, each claim linked to its fact, and checks the answer against them. Stores nothing. Returns the step's state: `waiting` (a prompt to do and answer with replyToPrompt), `running` (call getStep), `done` (do what `next` says) or `failed`.

Input parameters:

- `question` (string, required): The person's question.
- `store` (string): The store's link, as the person gave it: a public link (https://.../api/p/<id> or https://.../#/public/<id>, or its public id) or the person's private link (https://.../api/k/<id> or https://.../#/st…

### `startStep` (~176 tokens)

Start a step in the person's store

Start a step - propose, add, documents, ask or remove - in a private store, with its JSON body, as the manual says. propose stores nothing; add stores only facts the person approved, with propose's proposal_id and their reply as confirmation; remove deletes only with confirm true, after the person confirmed. Returns the step's state: `waiting` (a prompt to do and answer with replyToPrompt), `running` (call getStep), `done` (do what `next` says) or `failed`.

Input parameters:

- `body` (object, required)
- `step` (string, required): The step to run.
- `store` (string, required): The person's private store link, as they gave it: https://.../api/k/<id> or https://.../#/store/<id>. Public links are read-only.

### `getStep` (~126 tokens)

Follow a step

Where a running step is now: its next prompt, or its result.

Input parameters:

- `run_id` (string, required): The step's run_id.
- `store` (string): The store's link, as the person gave it: a public link (https://.../api/p/<id> or https://.../#/public/<id>, or its public id) or the person's private link (https://.../api/k/<id> or https://.../#/st…

### `replyToPrompt` (~191 tokens)

Answer a step's prompt

Answer the prompt a step is waiting on - do the model work in its `system` and `messages` first. Keep answering until the step is done or failed.

Input parameters:

- `call_id` (string, required): The prompt's call_id.
- `reply` (string, required): Your answer: the JSON object the reply_schema asks for, written as JSON text - or plain text when there is no schema.
- `run_id` (string, required): The step's run_id.
- `store` (string): The store's link, as the person gave it: a public link (https://.../api/p/<id> or https://.../#/public/<id>, or its public id) or the person's private link (https://.../api/k/<id> or https://.../#/st…

### `createStore` (~99 tokens)

Make a store for the person

A new, empty FactoGraph store of the person's own: its private link, which these tools take as `store`. Only after the person said yes to having one. Nothing is stored until the link is first opened. The link is the store's key: give it to them once, and never put it anywhere public.

Input parameters:

- `person_agreed` (boolean, required): true: the person asked for a store, or said yes when you offered one.

## Diagnostics

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

## Score history

- 2026-11-04: 68
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 65
- 2026-10-28: 65
- 2026-10-27: 64
- 2026-10-26: 64
- 2026-10-25: 63
- 2026-10-24: 63
- 2026-10-23: 62
- 2026-10-22: 62
- 2026-10-21: 69

## Common questions

### What is the FactoGraph MCP server?

FactoGraph is an MCP server listed in the public MCP registry as app.factograph/factograph. Memory for AI agents: facts a person approved, each with a link, and answers that cite them. This page covers its hosted endpoint (https://api.factograph.app/api/mcp).

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

FactoGraph scores 68 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 FactoGraph MCP server expose?

FactoGraph exposes 7 tools: getManual, listFacts, ask, startStep, getStep, and 2 more. Their descriptions and schemas cost roughly 1,043 tokens of context every time the server is loaded.

### Does the FactoGraph MCP server require authentication?

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

### Is the FactoGraph MCP server still maintained?

FactoGraph is still listed as active in the MCP registry. We last reached this channel on 4 November 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://api.factograph.app/api/mcp
- Website: https://www.factograph.app/for-ai-agents.html
- Changelog RSS feed: https://verifymcp.io/servers/app-factograph-factograph/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-factograph-factograph/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-factograph-factograph/api-mcp