Is the Projectstate MCP server down?

mcp-registry/online.projectstate/projectstate · v0.3.0

healthy
Last checked 2026-10-26 20:37 UTC · handshake 278ms

As of 2026-10-26 20:37 UTC, the Projectstate MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
4,901
outages (90d)
4
tools
6

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

Point your MCP client at this streamable-http endpoint: https://projectstate.online/mcp

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 3 warning(s) across 6 tool(s); ~1,602 tokens of tool definitions.
Scores higher than 7% of 15,760 MCP servers Glimind has audited.
Its tool list costs an agent ~1,602 tokens per session — lighter than 60% of servers.
71 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints7
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (3)

36 parameter(s) across 6 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: plan_check, project_open, project_status, recall, remember and 1 more

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: plan_check, project_open, project_status, recall, remember and 1 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: update

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fonline.projectstate%2Fprojectstate/fixes

plan_check 1 change
{
  "name": "plan_check",
  "description": "Before you start something non-trivial, say what you are about to do and get back only what would\n        change your mind: attempts that already failed at this, decisions that are still in force and constrain\n        it, and open tasks that overlap. `intent` is one line in plain words, e.g. 'switch the cache to Redis'\n        or 'rewrite the auth middleware to use refresh tokens'. Pass `files` if you know which paths you will\n        touch; entries about those files are included even when the w",
  "inputSchema": {
    "type": "object",
    "title": "plan_checkArguments",
    "required": [
      "project",
      "intent"
    ],
    "properties": {
      "files": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Files",
        "default": null
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 3
      },
      "intent": {
        "type": "string",
        "title": "Intent"
      },
      "project": {
        "type": "string",
        "title": "Project"
      },
      "max_chars": {
        "type": "integer",
        "title": "Max Chars",
        "default": 1200
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Plan check"
}
project_status 1 change
{
  "name": "project_status",
  "description": "Get the project's one-line status, open tasks and last change. Pass `set_status` to overwrite the status\n        line (e.g. 'v0.3 shipped; next: migrate auth to OAuth'). Cheap; use it for handoff notes between sessions.",
  "inputSchema": {
    "type": "object",
    "title": "project_statusArguments",
    "required": [
      "project"
    ],
    "properties": {
      "project": {
        "type": "string",
        "title": "Project"
      },
      "set_status": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Set Status",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Project status"
}
update 1 change
{
  "name": "update",
  "description": "Change an existing entry by id: set `status` (task open|done|dropped, attempt worked|failed|partial,\n        decision active|superseded|reverted, note active|archived), replace `title`/`body`, `append` a line to the\n        body (e.g. an outcome), replace `tags`/`files`, or `delete` it.",
  "inputSchema": {
    "type": "object",
    "title": "updateArguments",
    "required": [
      "project",
      "id"
    ],
    "properties": {
      "id": {
        "type": "integer",
        "title": "Id"
      },
      "body": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Body",
        "default": null
      },
      "tags": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Tags",
        "default": null
      },
      "files": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Files",
        "default": null
      },
      "title": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Title",
        "default": null
      },
      "append": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Append",
        "default": null
      },
      "delete": {
        "type": "boolean",
        "title": "Delete",
        "default": false
      },
      "status": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Status",
        "default": null
      },
      "project": {
        "type": "string",
        "title": "Project"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": true
  },
  "title": "Update entry"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/online.projectstate/projectstate"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/online.projectstate/projectstate"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fonline.projectstate%2Fprojectstate.svg)](https://glimind.com/server/mcp-registry%2Fonline.projectstate%2Fprojectstate?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fonline.projectstate%2Fprojectstate?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fonline.projectstate%2Fprojectstate.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fonline.projectstate%2Fprojectstate.svg
   :target: https://glimind.com/server/mcp-registry%2Fonline.projectstate%2Fprojectstate?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0464f625d3087cca…, first seen 2026-10-17, included at leaf 5210 of 75,326. Version history · verify what your client received.

Tools (6)

Compare: most reliable knowledge servers · most reliable productivity servers · most reliable retrieval servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Projectstate MCP server down right now?

As of 2026-10-26 20:37 UTC, the Projectstate MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Projectstate MCP server provide?

Projectstate MCP server advertises 6 tools, including plan_check, project_open, project_status, recall, remember.

How do I install Projectstate MCP server?

Point your MCP client at this streamable-http endpoint: https://projectstate.online/mcp

Is the Projectstate MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Projectstate MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve