Skip to content
logr logo

logr MCP server

Which MCP servers are logr'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 logr

Whose server it is
  • Registry nameit.logr/mcpverified in the MCP registry

The registry name sits under logr.it. 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
  • Tools6
  • Server calls itselflogr
  • Server version1.0.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 4 of 6 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: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Use1 GitHub stars
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer153 ms
  • Space in an agent's context≈ 778 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsB · 89 of 100
  • Typed results5 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 6

What an agent can do with it

  • cannot · log milestones and side projects as dated entries
  • not sure · share a timeline that readers can follow
  • not sure · let AI agents ask questions about a personal log

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 offers6 tools · read 2026-10-26
  • find_profiles

    Search public logr profiles by name, handle, bio, or location. Returns handles to use with the other tools.

  • get_profile

    A profile's identity card: who they are, what they're doing now, socials, and timeline stats.

  • get_timeline

    A profile's timeline events, newest first, optionally filtered by tag, year, featured, or pinned.

  • get_event

    One timeline event in full, including its media (image/video/link URLs).

  • search_events

    Keyword search over a profile's timeline (title, body, tags). All terms must match. Plain text matching — no semantic search.

  • get_context

    The complete Markdown context for a profile — identity, about, and full timeline with sources. Same content as the logr://profiles/{username} resource, for clients that prefer tools.

How to connect

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

{
  "mcpServers": {
    "logr": {
      "type": "http",
      "url": "https://logr.it/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http logr https://logr.it/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://logr.it/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.