mcp-registry/io.outil/outil · registry v2.1.1 · server reports v2.0.0
Also listed as github/outil-io/outil-mcp
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 16:14 UTC, the Outil.io MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
All-in-one marketing for entrepreneurs: sites, sales funnels, CRM, email, WhatsApp, courses, shop.
Point your MCP client at this streamable-http endpoint: https://outil.io/mcp
Loading this server's tool list costs an agent ~102,825 tokens before any work — more than 99% 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 →
9 tool definition(s) exceed ~1,200 tokens each (largest: apply_video_edits, ~4,806).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~13,546 tokens every session. How to fix →
413 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 →
1075 parameter(s) across 347 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 →
In the last 30 days: 91 tool(s) removed and 22 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 →
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 →
6 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
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.outil/outil"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.outil/outil"}) over MCP.
apply_video_edits ~4,806 tokensbuild_video_from_storyboard ~2,209 tokensapply_site_changes ~2,161 tokensreplace_video_document ~2,154 tokensapply_page_changes ~1,911 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%2Fio.outil%2Foutil?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.outil%2Foutil?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.outil%2Foutil.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:5360df744c5a8e5b…, first seen 2026-11-21, included at leaf 378627 of 384,547. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable productivity servers · most reliable media servers · most reliable other servers · most reliable code 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 16:14 UTC, the Outil.io MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Outil.io MCP server advertises 300+ tools, including add_site_project_message, add_slide_ai, add_team_member, add_video_audio_track, add_video_caption.
Point your MCP client at this streamable-http endpoint: https://outil.io/mcp
Glimind scanned all 413 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.