Skip to content

projectstate MCP server

online.projectstate/projectstateprojectstate.onlinestreamable-httpv0.3.0Scanned

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

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the projectstate MCP server can do

The projectstate MCP server is published by projectstate.online, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: project_open, remember, plan_check and update), but cannot delete data. 2 tools only read.

1 tool reads private data (recall).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 21, 2026, version 0.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • plan_checkBefore 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 i…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • project_openOpen (or create) a project and get a compact brief: status line, open tasks, latest active decisions and failed attempts.No findings

    Why it is in this group

    • The name "project_open" says "open": a word for a change.
    Description, as the server wrote it
    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 '.').
  • rememberStore one fact about the project.No findings

    Why it is in this group

    • The description's first verb is "store": a word for a change.
    Description, as the server wrote it
    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.
  • updateChange an existing entry by id: set `status` (task open|done|dropped, attempt worked|failed|partial, decision active|superseded|reverted, note active|archived), replace `title`/`bo…No findings

    Why it is in this group

    • The name "update" says "update": a word for a change.
    Description, as the server wrote it
    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.
Only reads 2Show 2 read-only tools
  • project_statusGet the project's one-line status, open tasks and last change.No findings

    Why it is in this group

    • The name "project_status" says "status": a word for reading.
    Description, as the server wrote it
    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.
  • recallSearch the project's memory with keywords and get the few most relevant entries (ranked, active entries first, superseded ones last), trimmed to `max_chars`.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.files), and the tool reads: it reads files.
    Description, as the server wrote it
    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(...).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
530
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 530.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 530
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 530; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 4 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 530
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http projectstate https://projectstate.online/mcp
claude mcp add --transport http projectstate https://projectstate.online/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__projectstate__project_status",
      "mcp__projectstate__recall"
    ],
    "ask": [
      "mcp__projectstate__project_open",
      "mcp__projectstate__remember",
      "mcp__projectstate__plan_check",
      "mcp__projectstate__update"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as projectstate. Review it before you use it.

Capability tags behind 1 rule
  • mcp__projectstate__recall private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/online.projectstate/projectstate/verify?hash=f0cefae9cfe88bf4d9c57cbed0a9b82c3b0d2038f167ac058ebbf13f6682d82d" | jq -e '.changed == false'

Pinned hash f0cefae9cfe8, from Oct 21, 2026, 19:15 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/online.projectstate/projectstate/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for online.projectstate/projectstate
[![Anlyon Radar](https://radar.anlyon.com/badge/online.projectstate/projectstate.svg)](https://radar.anlyon.com/servers/online.projectstate/projectstate)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

projectstate MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the projectstate MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the projectstate MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the projectstate MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the projectstate MCP server have?

6 tools: 4 write, 2 read. project_open, remember, plan_check, update, project_status and recall.

Does the projectstate MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the projectstate MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the projectstate MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.