mcp-registry/com.loopingagent/loopingagent-mcp · v0.3.1
As of 2026-10-20 15:16 UTC, the Loopingagent MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 8 minutes.
English blog + agentic AI architect profile (Paris): search, full text, projects, booking.
Claude Code
claude mcp add --transport http loopingagent-mcp-server https://loopingagent.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"loopingagent-mcp-server": {
"type": "http",
"url": "https://loopingagent.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
9 of 9 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 →
1 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 →
Handshake + tools/list takes ~1,669 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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%2Fcom.loopingagent%2Floopingagent-mcp/fixes
{
"name": "book_call",
"description": "Get the booking link to schedule a free 30-minute call with Laurent Knauss (Cal.com). The agent should present this link to the user so they can pick a slot. Optional topic hint is allowed but the actual slot selection happens on Cal.com.",
"inputSchema": {
"type": "object",
"properties": {
"topic": {
"type": "string",
"description": "Optional topic for the call (e.g. 'agentic AI project')."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "get_article",
"description": "Get a single article from loopingagent.com: metadata (category, description, cover, canonical URL), the FULL plain-text content (so the agent can quote and cite it accurately) and 3 related articles. Use list_articles or search_articles first to find the slug.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Article slug. Ex: browser-automation, agentic-commerce-protocol, langgraph-generative-ui"
},
"include_content": {
"type": "boolean",
"description": "Include the full article text (default: true). Set to false for metadata only, which is cheaper."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_profile",
"description": "Full professional profile of Laurent Knauss: title, location, availability, contact email, social profiles (GitHub, LinkedIn, X), certifications, and Cal.com booking link. Use this first to understand who he is and how to reach him.",
"inputSchema": {
"type": "object",
"properties": {}
},
"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.loopingagent/loopingagent-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.loopingagent/loopingagent-mcp"}) over MCP.
search_articles ~218 tokensget_article ~180 tokenslist_projects ~165 tokenslist_articles ~157 tokensbook_call ~117 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%2Fcom.loopingagent%2Floopingagent-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.loopingagent%2Floopingagent-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.loopingagent%2Floopingagent-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.loopingagent%2Floopingagent-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.loopingagent%2Floopingagent-mcp?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:6417ada3a4603182…, first seen 2026-10-17, included at leaf 5737 of 33,617. Version history · verify what your client received.
Compare: most reliable communication 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-20 15:16 UTC, the Loopingagent MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 8 minutes.
Loopingagent MCP server advertises 9 tools, including book_call, get_article, get_profile, get_project, get_skill.
Point your MCP client at this streamable-http endpoint: https://loopingagent.com/api/mcp
Glimind scanned all 9 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.