# projectstate (remote · projectstate.online)

Per-project memory for AI agents: decisions, attempts, tasks, ranked recall. Paid per call via x402.

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

## Components

- remote · `projectstate.online`: 60/100 (this document), [markdown](https://verifymcp.io/servers/online-projectstate-projectstate/projectstate.md), [page](https://verifymcp.io/servers/online-projectstate-projectstate/projectstate)

## Channel facts

- Endpoint: `https://projectstate.online/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.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-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1036 tokens (~172/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

projectstate is a hosted endpoint at https://projectstate.online/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 online-projectstate-projectstate 'https://projectstate.online/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "online-projectstate-projectstate": {
      "url": "https://projectstate.online/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "online-projectstate-projectstate": {
      "type": "http",
      "url": "https://projectstate.online/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.online-projectstate-projectstate]
url = "https://projectstate.online/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add online-projectstate-projectstate --url 'https://projectstate.online/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  online-projectstate-projectstate:
    url: "https://projectstate.online/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "online-projectstate-projectstate": {
      "Transport": "http",
      "Url": "https://projectstate.online/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add online-projectstate-projectstate -t streamable-http -u 'https://projectstate.online/mcp'
```

### Other

```json
{
  "mcpServers": {
    "online-projectstate-projectstate": {
      "type": "http",
      "url": "https://projectstate.online/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-19 (score 60, +1)

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

### 2026-09-17 (score 59, +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.

### 2026-09-15 (score 58, +1)

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

### 2026-09-13 (score 57, +1)

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

### 2026-09-12 (score 56, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 836 → 1036
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: excellent → good
- [functional] Server version: 0.2.1 → 0.3.0
- [functional] New tool “plan_check”

### 2026-09-11 (score 57)

First indexed and scored.

## MCP tools (6)

### `project_open` (~91 tokens)

Open project

Open (or create) a project and get a compact brief: status line, open tasks, latest active decisions and
        failed attempts. Call this first in a session. Omit `project` to list your projects.
        `project` is a slug like 'my-app' (lowercase, digits, '-', '_' or '.').

Input parameters:

- `description`
- `name`
- `project`

Output parameters:

- `result` (string)

### `project_status` (~75 tokens)

Project status

Get the project's one-line status, open tasks and last change. Pass `set_status` to overwrite the status
        line (e.g. 'v0.3 shipped; next: migrate auth to OAuth'). Cheap; use it for handoff notes between sessions.

Input parameters:

- `project` (string, required)
- `set_status`

Output parameters:

- `result` (string)

### `remember` (~193 tokens)

Remember

Store one fact about the project. `kind` is one of: decision (what was chosen and why), attempt (something
        tried; status 'worked'|'failed'|'partial'), task (status 'open'|'done'|'dropped'), note (anything else).
        `title` is one line; put details, reasons and error messages in `body`. `files` lists related paths.
        `supersedes` marks an older decision/task as replaced by this one. Identical content is stored once, so
        retries are safe; `idempotency_key` additionally guarantees a retry is not billed twice.

Input parameters:

- `body` (string)
- `files`
- `idempotency_key`
- `kind` (string, required)
- `project` (string, required)
- `status`
- `supersedes`
- `tags`
- `title` (string, required)

Output parameters:

- `result` (string)

### `recall` (~150 tokens)

Recall

Search the project's memory with keywords and get the few most relevant entries (ranked, active entries
        first, superseded ones last), trimmed to `max_chars`. Use 2-5 specific keywords (e.g. 'auth token expiry').
        Filters: kind (decision|attempt|task|note), status, tags, files. Omit `query` for the most recent entries.
        Follow up with update(project, id, ...) or remember(...).

Input parameters:

- `files`
- `kind`
- `limit` (integer)
- `max_chars` (integer)
- `project` (string, required)
- `query` (string)
- `status`
- `tags`

Output parameters:

- `result` (string)

### `plan_check` (~165 tokens)

Plan check

Before you start something non-trivial, say what you are about to do and get back only what would
        change your mind: attempts that already failed at this, decisions that are still in force and constrain
        it, and open tasks that overlap. `intent` is one line in plain words, e.g. 'switch the cache to Redis'
        or 'rewrite the auth middleware to use refresh tokens'. Pass `files` if you know which paths you will
        touch; entries about those files are included even when the wording differs. Cheaper than repeating
        work that already failed once.

Input parameters:

- `files`
- `intent` (string, required)
- `limit` (integer)
- `max_chars` (integer)
- `project` (string, required)

Output parameters:

- `result` (string)

### `update` (~141 tokens)

Update entry

Change an existing entry by id: set `status` (task open|done|dropped, attempt worked|failed|partial,
        decision active|superseded|reverted, note active|archived), replace `title`/`body`, `append` a line to the
        body (e.g. an outcome), replace `tags`/`files`, or `delete` it.

Input parameters:

- `append`
- `body`
- `delete` (boolean)
- `files`
- `id` (integer, required)
- `project` (string, required)
- `status`
- `tags`
- `title`

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-09-20: 60
- 2026-09-19: 60
- 2026-09-18: 59
- 2026-09-17: 59
- 2026-09-16: 58
- 2026-09-15: 58
- 2026-09-14: 57
- 2026-09-13: 57
- 2026-09-12: 56
- 2026-09-11: 57

## Common questions

### What is the projectstate MCP server?

projectstate is an MCP server listed in the public MCP registry as online.projectstate/projectstate. Per-project memory for AI agents: decisions, attempts, tasks, ranked recall. Paid per call via x402. This page covers its hosted endpoint (https://projectstate.online/mcp).

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

projectstate scores 60 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 projectstate MCP server expose?

projectstate exposes 6 tools: project_open, project_status, remember, recall, plan_check, update. Their descriptions and schemas cost roughly 815 tokens of context every time the server is loaded.

### Does the projectstate MCP server require authentication?

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

### Is the projectstate MCP server still maintained?

projectstate is still listed as active in the MCP registry. We last reached this channel on 20 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://projectstate.online/mcp
- Repository: https://github.com/ErikKerkvliet/projectstate
- Website: https://projectstate.online/
- Changelog RSS feed: https://verifymcp.io/servers/online-projectstate-projectstate/projectstate.xml
- Changelog JSON feed: https://verifymcp.io/servers/online-projectstate-projectstate/projectstate.json
- HTML version of this page: https://verifymcp.io/servers/online-projectstate-projectstate/projectstate