mcp-registry/com.writerslogic.agents/writerslogic-agent-infra · registry v1.0.0 · server reports v2.0.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 17:00 UTC, the WritersLogic agent-infra MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Micro agents for parsing, validation, encoding, scoring, and structured I/O pipelines.
Point your MCP client at this streamable-http endpoint: https://agents.writerslogic.com/mcp/agent-infra
65 of 65 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 →
65 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
61 parameter(s) across 32 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 →
6 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
3 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 →
Loading this server's tool list costs an agent ~30,166 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. 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 →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 32 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.writerslogic.agents%2Fwriterslogic-agent-infra/fixes
{
"name": "acceptance-receipt",
"description": "Signed acceptance receipt: which deterministic tests a delivered output passed — Runs your deterministic acceptance tests (equals, exists, absent, type, contains, length and number ranges, one-of, sha256, a JSON Schema subset) against a sub-agent's or vendor's JSON output at JSON Pointer paths, and returns per-test results plus a hub-signed receipt over the output hash, the tests hash and the results. Use it before paying for delegated work or releasing the next step. It certi",
"inputSchema": {
"type": "object",
"required": [
"output",
"tests"
],
"properties": {
"label": {
"type": "string",
"maxLength": 200,
"description": "Free text bound into the receipt, e.g. the task id."
},
"tests": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"kind"
],
"properties": {
"id": {
"type": "string",
"pattern": "^[A-Za-z0-9_.:-]{1,64}$"
},
"max": {
"type": "number"
},
"min": {
"type": "number"
},
"kind": {
"enum": [
"equals",
"not-equals",
"exists",
"absent",
"type",
"contains",
"length-between",
"number-between",
"one-of",
"sha256",
"schema"
],
"type": "string"
},
"path": {
"type": "string",
"maxLength": 500,
"description": "RFC 6901 JSON Pointer into output; empty or omitted = the whole output."
},
"value": {
"description": "equals/not-equals/contains: the JSON value; type: a JSON type name; one-of: an array; sha256: lowercase hex; schema: a hub-subset JSON Schema."
}
},
"additionalProperties": false
},
"maxItems": 100,
"minItems": 1
},
"output": {
"description": "The delivered JSON (at most 262144 bytes as JCS).",
"type": "string"
}
},
"additionalProperties": false
}
}{
"name": "approval-invalidation",
"description": "Does a change to the approved thing invalidate the approval under a materiality policy? — Compares what a human or system approved with what is about to be executed (a quote, order, plan, diff summary: any JSON) under a caller-supplied materiality policy: per-path rules exact / ignore / numeric tolerance (absolute or percent) / no-increase / no-decrease, with the longest matching path winning and a default for unlisted paths. Also covers quote revisions (approved revision number must e",
"inputSchema": {
"type": "object",
"required": [
"approved",
"current"
],
"properties": {
"asOf": {
"type": "string",
"maxLength": 40,
"description": "RFC 3339 instant for the expiry check; no clock is read."
},
"policy": {
"type": "object",
"properties": {
"fields": {
"type": "array",
"items": {
"type": "object",
"required": [
"path",
"rule"
],
"properties": {
"abs": {
"type": "number",
"maximum": 1000000000000000,
"minimum": 0,
"description": "numeric-tolerance: allowed absolute difference."
},
"pct": {
"type": "number",
"maximum": 1000,
"minimum": 0,
"description": "numeric-tolerance: allowed difference as percent of the approved value. Either bound being met is enough."
},
"path": {
"type": "string",
"maxLength": 300,
"description": "JSON Pointer prefix; \"*\" matches one token."
},
"rule": {
"enum": [
"exact",
"ignore",
"numeric-tolerance",
"no-increase",
"no-decrease"
],
"type": "string"
}
},
"additionalProperties": false
},
"maxItems": 100
},
"default": {
"enum": [
"material",
"ignore"
],
"type": "string",
"description": "Rule for paths no field rule covers. Default material (any change invalidates)."
}
},
"additionalProperties": false
},
"current": {
"description": "The version about to be executed (JSON).",
"type": "string"
},
"approved": {
"description": "The approved snapshot (JSON).",
"type": "string"
},
"approvedAt": {
"type": "string",
"maxLength": 40,
"description": "RFC 3339 instant."
},
"currentRevision": {
"type": "integer",
"maximum": 1000000000,
"minimum": 0
},
"validForSeconds": {
"type": "integer",
"maximum": 315360000,
"minimum": 0
},
"approvedRevision": {
"type": "integer",
"maximum": 1000000000,
"minimum": 0
},
"requireSameRevision": {
"type": "boolean",
"description": "Default true when either revision is given (a missing partner gives unknown): an approval for another revision does not cover this one. Send false to ignore the revisions."
}
},
"additionalProperties": false
}
}{
"name": "cache-key-check",
"description": "Check that a result-cache key contains every input that changes the result, and nothing volatile — Given the inputs of a cached computation (each declared as influencing the output or not, optionally volatile) and the list of inputs the cache key is built from, finds influential inputs missing from the key (stale or wrong hits), volatile inputs inside it (the cache never hits), unknown-influence inputs left out, and, for private results, a missing tenant dimension (cross-tenant leak). When valu",
"inputSchema": {
"type": "object",
"required": [
"inputs",
"keyParts"
],
"properties": {
"scope": {
"type": "string",
"maxLength": 200,
"description": "Namespace mixed into the digest."
},
"inputs": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"influencesOutput"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200,
"minLength": 1
},
"value": {
"description": "Optional value, used only to compute the key digest."
},
"volatile": {
"type": "boolean",
"description": "Changes on every call (timestamp, request id, nonce)."
},
"influencesOutput": {
"enum": [
"yes",
"no",
"unknown"
],
"type": "string"
}
},
"additionalProperties": false
},
"maxItems": 100,
"minItems": 1
},
"private": {
"type": "boolean",
"description": "The result is per-tenant or per-user."
},
"keyParts": {
"type": "array",
"items": {
"type": "string",
"maxLength": 200,
"minLength": 1
},
"maxItems": 100,
"description": "Names of the inputs the key is built from."
},
"tenantInput": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Name of the input that identifies the tenant or user; required in the key when private."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}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.writerslogic.agents/writerslogic-agent-infra"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.writerslogic.agents/writerslogic-agent-infra"}) over MCP.
evidence-scope-mismatch ~895 tokenswarm-memory ~776 tokensretry-admissibility ~772 tokensfleet-memory ~738 tokensdedup-window ~721 tokensStatic 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fcom.writerslogic.agents%2Fwriterslogic-agent-infra?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.writerslogic.agents%2Fwriterslogic-agent-infra?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.writerslogic.agents%2Fwriterslogic-agent-infra.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e45d174f1faa3876…, first seen 2026-11-19, included at leaf 353118 of 384,671. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other servers · most reliable communication servers · most reliable code servers · most reliable ml servers
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.
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"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 17:00 UTC, the WritersLogic agent-infra MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
WritersLogic agent-infra MCP server advertises 65 tools, including acceptance-receipt, approval-invalidation, artifact-invalidator, assumption-conflict, attachment-references.
Point your MCP client at this streamable-http endpoint: https://agents.writerslogic.com/mcp/agent-infra
Glimind scanned all 65 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.
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.