mcp-registry/io.github.jimy-r/agent-workspace-practice · v1.2.0
As of 2026-10-21 05:36 UTC, the Jimy R Agent Workspace Practice MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Search + patterns, maturity assessment, context pricing, redaction checks - a practice as tools.
Claude Code
claude mcp add --transport http jimy-r-agent-workspace-practice-mcp-serv https://jamesross.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"jimy-r-agent-workspace-practice-mcp-serv": {
"type": "http",
"url": "https://jamesross.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
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 →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jimy-r%2Fagent-workspace-practice/fixes
{
"name": "check_redaction",
"description": "Scan text for the shapes of private content before it goes anywhere public: email addresses, absolute home paths, credential and token prefixes, private and link-local IPs, .local hostnames, and secret filenames. Returns a count per pattern class and a total, nothing else. The text you send and the substrings that matched are never stored, never logged and never echoed back. Only the counts are kept. A line carrying the marker \"redaction-ok\" is skipped. Accepts up to 100KB.",
"inputSchema": {
"type": "object",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"description": "The text to scan. Up to 100KB; anything beyond that is truncated and the result says so."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Pre-flight text for the shapes of private content"
}{
"name": "lookup_pattern",
"description": "Search the 18 architecture patterns behind this practice by keyword or by pattern number. Returns up to 3 matches, each with its number, title, the problem it opens on, and a link to the full text. Use it when you want the reasoning behind an agent-workspace design decision rather than a how-to.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Keywords to match against pattern titles and summaries, e.g. \"credentials\", \"silent failure\", \"context cost\". A bare number 1-18 looks that pattern up directly."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Look up an agent-workspace pattern"
}{
"name": "price_context_read",
"description": "Price a block of context by where it enters a session. The API is stateless, so the whole transcript is re-sent on every inference step, and a token costs its size times the number of turns left after it arrives. Returns the carried token volume, the cost of the block in USD, what the same read would have cost entering 20 turns from the end, and the multiplier between the two. Use it to decide whether a large read should move later in a session or into a subagent.",
"inputSchema": {
"type": "object",
"required": [
"size_tokens",
"entry_turn",
"total_turns"
],
"properties": {
"read_mult": {
"type": "number",
"default": 0.1,
"minimum": 0,
"description": "Cache-read price multiplier against input price. Default 0.1."
},
"entry_turn": {
"type": "number",
"minimum": 0,
"description": "Turn number at which the block enters the context (t)."
},
"write_mult": {
"type": "number",
"default": 1.25,
"minimum": 0,
"description": "Cache-write price multiplier against input price. Default 1.25."
},
"size_tokens": {
"type": "number",
"minimum": 0,
"description": "Size of the block in tokens (S)."
},
"total_turns": {
"type": "number",
"minimum": 0,
"description": "Total turns in the session (T). Must be at least entry_turn."
},
"price_in_per_mtok": {
"type": "number",
"default": 5,
"minimum": 0,
"description": "Input price in USD per million tokens. Default 5."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Price a block of context by its position"
}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/io.github.jimy-r/agent-workspace-practice"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.jimy-r/agent-workspace-practice"}) over MCP.
price_context_read ~382 tokensassess_workspace ~286 tokenssearch_architecture ~270 tokenscheck_redaction ~209 tokenslookup_pattern ~179 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. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.jimy-r%2Fagent-workspace-practice?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jimy-r%2Fagent-workspace-practice?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jimy-r%2Fagent-workspace-practice.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jimy-r%2Fagent-workspace-practice.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.jimy-r%2Fagent-workspace-practice?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a1a85b8980437156…, first seen 2026-10-17, included at leaf 14406 of 37,421. Version history · verify what your client received.
Compare: most reliable other servers · most reliable security servers · most reliable knowledge servers · most reliable search 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
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 05:36 UTC, the Jimy R Agent Workspace Practice MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Jimy R Agent Workspace Practice MCP server advertises 6 tools, including assess_workspace, check_redaction, lookup_pattern, price_context_read, request_capability.
Point your MCP client at this streamable-http endpoint: https://jamesross.ai/mcp
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.
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.