logr
REMOTE · LOGR.IT
Query any public logr profile — timelines, events, full context — plus owner-authorized writes.
Available components
Last scanned (17 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Memory and Knowledge
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 598 tokens (~99/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
- Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 7 Aug 26 0
First indexed and scored.
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 16 Oct 2026 · Probed https://logr.it/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=logr.it | CN=YR1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 2048 | SHA256-RSA | 6dafa3675d79e7f7e31047685d9dd313d90 |
| SANs: logr.it | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of logr.it. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| it. | present | 51765 | 13 | Verified |
| logr.it. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://logr.it/mcp | Verified | 200 | |
| http (plaintext) | http://logr.it/mcp | HTTPS enforced | 308 | https://logr.it/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 →
find_profiles Find profiles ~53
Search public logr profiles by name, handle, bio, or location. Returns handles to use with the other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Name, handle, or free-text match |
| Name | Type | Req | Description |
|---|---|---|---|
| profiles | array | yes | – |
No examples provided.
get_context Get full context ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | The profile's @handle (its URL slug), e.g. "koshik" |
No output schema declared.
No examples provided.
get_event Get event ~54
One timeline event in full, including its media (image/video/link URLs).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| username | string | yes | The profile's @handle (its URL slug), e.g. "koshik" |
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| date | string | yes | ISO date (YYYY-MM-DD) |
| displayDate | string | yes | – |
| featured | boolean | yes | – |
| id | string | yes | – |
| link | – | yes | – |
| media | array | yes | – |
| mediaCount | number | yes | – |
| pinned | boolean | yes | – |
| sourceUrl | – | yes | Citation URL for seeded events |
| tags | array | yes | – |
| title | string | yes | – |
| year | number | yes | – |
No examples provided.
get_profile Get profile ~53
A profile's identity card: who they are, what they're doing now, socials, and timeline stats.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | The profile's @handle (its URL slug), e.g. "koshik" |
| Name | Type | Req | Description |
|---|---|---|---|
| about | – | yes | – |
| avatarUrl | – | yes | – |
| bio | string | yes | – |
| currently | string | yes | – |
| disclosure | – | yes | – |
| eventCount | number | yes | – |
| location | string | yes | – |
| name | string | yes | – |
| socials | array | yes | – |
| unverified | boolean | yes | true when auto-generated and not claimed by its subject |
| updatedAt | string | yes | – |
| urls | object | yes | – |
| username | string | yes | – |
| years | – | yes | – |
No examples provided.
get_timeline Get timeline ~120
A profile's timeline events, newest first, optionally filtered by tag, year, featured, or pinned.
| Name | Type | Req | Description |
|---|---|---|---|
| featured | boolean | – | Only events marked as highlights |
| limit | integer | – | – |
| offset | integer | – | – |
| pinned | boolean | – | Only events the owner pinned |
| tag | string | – | Event tag: work | milestone | talk | side_quest | writing |
| username | string | yes | The profile's @handle (its URL slug), e.g. "koshik" |
| year | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
| total | number | yes | Matches before limit/offset |
| username | string | yes | – |
No examples provided.
search_events Search events ~73
Keyword search over a profile's timeline (title, body, tags). All terms must match. Plain text matching — no semantic search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| username | string | yes | The profile's @handle (its URL slug), e.g. "koshik" |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
| total | number | yes | – |
| username | string | yes | – |
No examples provided.
How do I install the logr MCP server?
logr is a hosted endpoint at https://logr.it/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 · logr.it
claude mcp add --transport http it-logr-mcp 'https://logr.it/mcp'
What is the logr MCP server?
logr is an MCP server listed in the public MCP registry as it.logr/mcp. Query any public logr profile, timelines, events, full context, plus owner-authorized writes. This page covers its hosted endpoint (https://logr.it/mcp).
Is the logr MCP server safe to use?
logr scores 86 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 logr MCP server expose?
logr exposes 6 tools: find_profiles, get_profile, get_timeline, get_event, search_events, get_context. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.
Does the logr MCP server require authentication?
No. We connected to logr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the logr MCP server still maintained?
logr is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.