logr is an MCP server with 6 tools an agent can call, among them find_profiles, get_context, get_event. It answers at https://logr.it/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Query any public logr profile — timelines, events, full context — plus owner-authorized writes.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
find_profiles | Search public logr profiles by name, handle, bio, or location. Returns handles to use with the other tools. Inputs: query, limit |
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. Inputs: username |
get_event | One timeline event in full, including its media (image/video/link URLs). Inputs: username, id |
get_profile | A profile's identity card: who they are, what they're doing now, socials, and timeline stats. Inputs: username |
get_timeline | A profile's timeline events, newest first, optionally filtered by tag, year, featured, or pinned. Inputs: username, tag, year, featured, pinned, limit |
search_events | Keyword search over a profile's timeline (title, body, tags). All terms must match. Plain text matching — no semantic search. Inputs: username, query, limit |
Every block below points at https://logr.it/mcp. Pick your client and copy.
claude mcp add --transport http logr https://logr.it/mcp
{
"mcpServers": {
"logr": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://logr.it/mcp"]
}
}
}{
"mcpServers": {
"logr": {
"url": "https://logr.it/mcp"
}
}
}{
"servers": {
"logr": {
"type": "http",
"url": "https://logr.it/mcp"
}
}
}{
"context_servers": {
"logr": {
"url": "https://logr.it/mcp"
}
}
}{
"mcpServers": {
"logr": {
"serverUrl": "https://logr.it/mcp"
}
}
}{
"mcpServers": {
"logr": {
"url": "https://logr.it/mcp"
}
}
}name: logr
version: 0.0.1
schema: v1
mcpServers:
- name: logr
type: streamable-http
url: https://logr.it/mcp{
"mcpServers": {
"logr": {
"httpUrl": "https://logr.it/mcp"
}
}
}{
"mcpServers": {
"logr": {
"type": "http",
"url": "https://logr.it/mcp"
}
}
}{
"mcpServers": {
"logr": {
"url": "https://logr.it/mcp"
}
}
}goose://extension?url=https%3A%2F%2Flogr.it%2Fmcp&type=streamable_http&id=logr&name=logr
It answered our last check on 24 October 2026 in 238 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by logr.it and served from logr.it, the vendor's own domain: https://logr.it/mcp.
6, as returned by the server's own tools/list on 22 September 2026: find_profiles, get_context, get_event, get_profile, get_timeline, search_events.
It answered our last check on 24 October 2026 in 238 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://logr.it/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: it.logr. Endpoint host: logr.it. ARD identifier: urn:air:it.logr:mcp:mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.