LoopingAgent
REMOTE · LOOPINGAGENT.COM · SCANNED SEP 20
English blog + agentic AI architect profile (Paris): search, full text, projects, booking.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 775 tokens (~86/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the LoopingAgent MCP server?
LoopingAgent is a hosted endpoint at https://loopingagent.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · loopingagent.com
claude mcp add --transport http com-loopingagent-loopingagent-mcp 'https://loopingagent.com/api/mcp'
{
"mcpServers": {
"com-loopingagent-loopingagent-mcp": {
"url": "https://loopingagent.com/api/mcp"
}
}
} {
"servers": {
"com-loopingagent-loopingagent-mcp": {
"type": "http",
"url": "https://loopingagent.com/api/mcp"
}
}
} [mcp_servers.com-loopingagent-loopingagent-mcp] url = "https://loopingagent.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-loopingagent-loopingagent-mcp": {
"type": "remote",
"url": "https://loopingagent.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-loopingagent-loopingagent-mcp --url 'https://loopingagent.com/api/mcp' --transport streamable-http
mcp_servers:
com-loopingagent-loopingagent-mcp:
url: "https://loopingagent.com/api/mcp" {
"McpServers": {
"com-loopingagent-loopingagent-mcp": {
"Transport": "http",
"Url": "https://loopingagent.com/api/mcp"
}
}
} assistant mcp add com-loopingagent-loopingagent-mcp -t streamable-http -u 'https://loopingagent.com/api/mcp'
{
"mcpServers": {
"com-loopingagent-loopingagent-mcp": {
"type": "http",
"url": "https://loopingagent.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
- “list_projects” reworded the description of “status” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Tool “get_article” rewrote its description, which is the text the model reads security
- Tool “list_articles” rewrote its description, which is the text the model reads security
- Schema quality: 69 → 85 ▼ functional
- Server version: 0.1.0 → 0.3.0 functional
- New tool “get_project” functional
- New tool “list_categories” functional
- New tool “list_projects” functional
- New tool “search_articles” functional
- “get_article” added an optional parameter “include_content” cosmetic
- “list_articles” added an optional parameter “limit” cosmetic
- 9 Sept 26 +1
- Tool “get_skill” rewrote its description, which is the text the model reads security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://loopingagent.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=loopingagent.com | CN=YE1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5d0e9ec56f790edad134529ce2b62dc1345 |
| SANs: loopingagent.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of loopingagent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| loopingagent.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://loopingagent.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://loopingagent.com/api/mcp | HTTPS enforced | 308 | https://loopingagent.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
book_call ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional topic for the call (e.g. 'agentic AI project'). |
No output schema declared.
No examples provided.
get_article ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_content | boolean | – | Include the full article text (default: true). Set to false for metadata only, which is cheaper. |
| slug | string | yes | Article slug. Ex: browser-automation, agentic-commerce-protocol, langgraph-generative-ui |
No output schema declared.
No examples provided.
get_profile ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_project ~73
Full details of one project shipped by Laurent Knauss: positioning, complete description, tech stack, live URL and status. Use list_projects first for the exact names.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Project name. Ex: AgentRecruteur, BullionRadar, ActionArgent, StreetBodies, VersatileAgent |
No output schema declared.
No examples provided.
get_skill ~63
Laurent Knauss' technical skills, grouped by domain (Agentic AI, RAG & Voice AI, Software engineering & Cloud, Automation & tooling). Each skill has a label and an optional short detail. Use this to assess fit for AI/agentic development roles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_articles ~94
List articles published on loopingagent.com (English technical blog: agentic AI, MCP, LangGraph, TypeScript, blockchain). Returns slug, title, category and description for each. Use search_articles to find articles on a topic, and get_article to read one in full.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter articles by category. |
| limit | number | – | Maximum number of articles to return (default: all of them). |
No output schema declared.
No examples provided.
list_categories ~43
List the loopingagent.com article categories with their article counts and slugs. Use it to browse the blog by theme (Agentic AI, blockchain) before fetching an article.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects ~103
Projects built and shipped by Laurent Knauss (agentic AI products and full-stack web apps), with domain, live status, one-line positioning and tech stack. Use it to assess his delivery track record — get_project returns the full description.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by project family: ai (agentic AI) or web. |
| status | string | – | Filter by status: live (deployed in production) or oss (open source, not deployed). |
No output schema declared.
No examples provided.
search_articles ~142
Full-text search across every article on loopingagent.com (title, description and body text). Returns the most relevant matches with a snippet of the matching passage, ranked by relevance. Use this to find an article to quote or cite on a topic — ex. 'ERC-4337 paymaster', 'Golang pointers', 'evaluating LLM applications', 'MCP server'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict the search to one category. |
| limit | number | – | Maximum number of results (default: 5, max: 20). |
| query | string | yes | Search terms (keywords, topic or technology). Multi-word queries are scored per term. |
No output schema declared.
No examples provided.
What is the LoopingAgent MCP server?
LoopingAgent is an MCP server listed in the public MCP registry as com.loopingagent/loopingagent-mcp. English blog + agentic AI architect profile (Paris): search, full text, projects, booking. This page covers its hosted endpoint (https://loopingagent.com/api/mcp).
Is the LoopingAgent MCP server safe to use?
LoopingAgent scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LoopingAgent MCP server expose?
LoopingAgent exposes 9 tools: get_profile, get_skill, list_articles, get_article, list_projects, and 4 more. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.
Does the LoopingAgent MCP server require authentication?
No. We connected to LoopingAgent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LoopingAgent MCP server still maintained?
LoopingAgent is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.