Is the Principal-drift ledger for standing instructions MCP server down?

mcp-registry/com.textforagents/principal-drift-ledger-standing-instructions · v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 16:31 UTC · handshake 85ms

As of 2026-11-22 16:31 UTC, the Principal-drift ledger for standing instructions MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
815
outages (90d)
0
tools
6

Signed, versioned ledger of standing instructions with intake contradiction diffs.

Point your MCP client at this streamable-http endpoint: https://textforagents.com/products/principal-drift-ledger-standing-instructions/mcp

Agent-readiness: D (64/100)

D (64/100): 0 error(s), 4 warning(s) across 6 tool(s); ~468 tokens of tool definitions.
Scores higher than 1% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~468 tokens per session — lighter than 90% of servers.
64 → 64 since 2026-11-15
no tool-poisoning patterns
Descriptions30
Safety hints0
Schemas100
Protocol40
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (5)

12 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: ledger_compile, ledger_create, ledger_diff, ledger_execute, ledger_verify 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: ledger_compile, ledger_create, ledger_diff, ledger_execute, ledger_verify and 1 more

2 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: ledger_create, ledger_execute

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 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%2Fcom.textforagents%2Fprincipal-drift-ledger-standing-instructions/fixes

ledger_create 1 change
{
  "name": "ledger_create",
  "description": "Create a standing-instruction ledger under your account.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
ledger_execute 1 change
{
  "name": "ledger_execute",
  "description": "Execute an order: the server independently re-diffs (409 semantics as an error result on contradiction) and returns an attestation naming the ledger version in force.",
  "inputSchema": {
    "type": "object",
    "required": [
      "ledger_id",
      "order"
    ],
    "properties": {
      "order": {
        "type": "object"
      },
      "ledger_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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/com.textforagents/principal-drift-ledger-standing-instructions"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.textforagents/principal-drift-ledger-standing-instructions"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fcom.textforagents%2Fprincipal-drift-ledger-standing-instructions.svg)](https://glimind.com/server/mcp-registry%2Fcom.textforagents%2Fprincipal-drift-ledger-standing-instructions?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.textforagents%2Fprincipal-drift-ledger-standing-instructions?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.textforagents%2Fprincipal-drift-ledger-standing-instructions.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:94d45566ad372011…, first seen 2026-11-15, included at leaf 285220 of 384,619. Version history · verify what your client received.

Tools (6)

Compare: most reliable database servers · most reliable data servers · most reliable security 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Principal-drift ledger for standing instructions MCP server down right now?

As of 2026-11-22 16:31 UTC, the Principal-drift ledger for standing instructions MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Principal-drift ledger for standing instructions MCP server provide?

Principal-drift ledger for standing instructions MCP server advertises 6 tools, including ledger_compile, ledger_create, ledger_diff, ledger_execute, ledger_verify.

How do I install Principal-drift ledger for standing instructions MCP server?

Point your MCP client at this streamable-http endpoint: https://textforagents.com/products/principal-drift-ledger-standing-instructions/mcp

Is the Principal-drift ledger for standing instructions 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 Principal-drift ledger for standing instructions 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