Skip to content
Inside the Loop logo

Inside the Loop MCP server

Which MCP servers are Inside the Loop's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Inside the Loop

Whose server it is
  • Registry namedev.insidetheloop/blogverified in the MCP registry

The registry name sits under insidetheloop.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools4
  • Server calls itselfinsidetheloop
  • Server version2.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 40 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check latest verified version of agent dev tools; look up fixes for tool error messages; query tool and fix pages through a read-only MCP server.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "check latest verified version of agent dev tools", the likely first call is list_tools.
  • For "look up fixes for tool error messages", the likely first call is search_fixes.
  • For "query tool and fix pages through a read-only MCP server", the likely first call is list_tools.
  • Parameters are untyped or undescribed in 1 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer2085 ms
  • Space in an agent's context≈ 488 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 96 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 4

What an agent can do with it

  • can do · check latest verified version of agent dev tools
  • can do · look up fixes for tool error messages
  • can do · query tool and fix pages through a read-only MCP server

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-26
  • list_tools

    List the CLIs with living tool pages (ASC CLI, Codex CLI, Wrangler, ...): latest version, UTC release date, last verified date and page URLs.

  • get_tool

    Return one tool page as Markdown: latest version and release date, upgrade command, last five releases, commands and flags added or removed (our sandbox --help diff), breaking changes, reproduced errors with fixes, monthly history and…

  • search_fixes

    Find the fix page for a CLI error message. Paste the exact error line, a fragment of it, or the whole terminal output (for example "unexpected argument '--full-auto' found"). Returns matching fix pages with the exact error, tool, affected…

  • get_fix

    Return one fix page as Markdown: the exact error output, tool and affected versions, cause, fix commands, our sandbox reproduction (commands and output), why it happens with a source link, related fixes and sources. Accepts the slug from…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "blog": {
      "type": "http",
      "url": "https://insidetheloop.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http insidetheloop https://insidetheloop.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://insidetheloop.dev/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.