accueil / serveurs / IA & Mémoire / io.github.jimy-r/agent-workspace-practice
io.github.jimy-r/agent-workspace-practice
serveur MCP (Model Context Protocol) · jamesross-practice 1.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.jimy-r/agent-workspace-practice est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.jimy-r/agent-workspace-practice » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 6 outils
- assess_workspace≈ 343 tokens
Score an agent workspace across six dimensions: canonical knowledge, memory and context economics, verification and oversight, safety and permissions, telemetry and cost, provenance and delegation. Two variants: "practitioner" takes 18 answers (a single operator's workspace), "org" takes 12 (an organisation's agent readiness). Each answer is an integer 0-3 in question order, where 0 is the least mature option offered and 3 the most. Returns per-dimension scores, an overall percentage, a maturity band, and the two weakest dimensions with the gap that matters there. The question text lives at https://jamesross.ai/tools/maturity-check (practitioner) and https://jamesross.ai/tools/agent-readiness (org). Read it before answering on someone's behalf.
Paramètres, retour & exemple (2)
Paramètresanswers· array · requis
Answers in question order: 18 integers for "practitioner", 12 for "org". Each is 0-3.variant· string · requis · practitioner | org
"practitioner" for the 18-question workspace check, "org" for the 12-question organisational readiness check.
Exemple d'appel{"name": "assess_workspace", "arguments": {"answers": [], "variant": "practitioner"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - check_redaction≈ 207 tokens
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.
Paramètres, retour & exemple (1)
Paramètrestext· string · requis
The text to scan. Up to 100KB; anything beyond that is truncated and the result says so.
Exemple d'appel{"name": "check_redaction", "arguments": {"text": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - lookup_pattern≈ 177 tokens
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.
Paramètres, retour & exemple (1)
Paramètresquery· string · requis
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.
Exemple d'appel{"name": "lookup_pattern", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - price_context_read≈ 372 tokens
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.
Paramètres, retour & exemple (6)
Paramètresread_mult· number · optionnel
Cache-read price multiplier against input price. Default 0.1.entry_turn· number · requis
Turn number at which the block enters the context (t).write_mult· number · optionnel
Cache-write price multiplier against input price. Default 1.25.size_tokens· number · requis
Size of the block in tokens (S).total_turns· number · requis
Total turns in the session (T). Must be at least entry_turn.price_in_per_mtok· number · optionnel
Input price in USD per million tokens. Default 5.
Exemple d'appel{"name": "price_context_read", "arguments": {"entry_turn": 1, "size_tokens": 1, "total_turns": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - request_capability≈ 148 tokens
Tell this server what capability you needed but didn't find here. Requests are logged and reviewed by a human; include no secrets or personal data.
Paramètres, retour & exemple (2)
Paramètrescontext· string · optionnel
Optional: what you were trying to do, and why the existing tools did not cover it. Up to 1KB.description· string · requis
What you needed. Up to 2KB.
Exemple d'appel{"name": "request_capability", "arguments": {"description": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_architecture≈ 288 tokens
Full-text search across the published architecture corpus: the 18 patterns and how they compose, the evaluation method, the seven learn-track modules, and the teardowns of other people's published agent systems. Returns ranked sections, each with its title, its source file, a snippet, and a link to the full text on GitHub. Use it when you want the passage itself rather than a pattern summary; lookup_pattern is the narrower tool that answers "which pattern covers this?". Every section is also readable in full as a resource under the architecture:// scheme (resources/list, resources/read).
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
How many sections to return. 1-10, default 5.query· string · requis
Search terms, e.g. "canonical copy", "silent failure", "cache write cost". Terms shorter than 3 characters are ignored.
Exemple d'appel{"name": "search_architecture", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».