Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

logr

REMOTE · LOGR.IT · SCANNED AUG 17

Query any public logr profile — timelines, events, full context — plus owner-authorized writes.

Available components

+3 this week 69 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security63
Transport & Reachability100
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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · logr.it

# add to Claude Code
claude mcp add --transport http it-logr-mcp https://logr.it/mcp
# ~/.codex/config.toml
[mcp_servers.it-logr-mcp]
url = "https://logr.it/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "it-logr-mcp": {
      "type": "remote",
      "url": "https://logr.it/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add it-logr-mcp --url https://logr.it/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  it-logr-mcp:
    url: "https://logr.it/mcp"
// mcp.json
{
  "mcpServers": {
    "it-logr-mcp": {
      "type": "http",
      "url": "https://logr.it/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 17 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Aug 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.

  • 13 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 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
  • 10 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Aug 26 +1
    • Stability: unverified → 0.03 functional
  • 7 Aug 26 64

    First indexed and scored.

Diagnostics

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 17 Aug 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 6 Jul 2026 4 Oct 2026 RSA 2048 SHA256-RSA 5ff5d80797f0371d9964aa7470992a33c49
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
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
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
MCP tools · 6 exposed · ~421 tokens

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.

Tool Tokens
find_profiles ~53

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

NameTypeReqDescription
limitinteger
querystringyesName, handle, or free-text match
NameTypeReqDescription
profilesarrayyes

No examples provided.

get_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.

NameTypeReqDescription
usernamestringyesThe profile's @handle (its URL slug), e.g. "koshik"

No output schema declared.

No examples provided.

get_event ~54

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

NameTypeReqDescription
idstringyes
usernamestringyesThe profile's @handle (its URL slug), e.g. "koshik"
NameTypeReqDescription
bodystringyes
datestringyesISO date (YYYY-MM-DD)
displayDatestringyes
featuredbooleanyes
idstringyes
linkyes
mediaarrayyes
mediaCountnumberyes
pinnedbooleanyes
sourceUrlyesCitation URL for seeded events
tagsarrayyes
titlestringyes
yearnumberyes

No examples provided.

get_profile ~53

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

NameTypeReqDescription
usernamestringyesThe profile's @handle (its URL slug), e.g. "koshik"
NameTypeReqDescription
aboutyes
avatarUrlyes
biostringyes
currentlystringyes
disclosureyes
eventCountnumberyes
locationstringyes
namestringyes
socialsarrayyes
unverifiedbooleanyestrue when auto-generated and not claimed by its subject
updatedAtstringyes
urlsobjectyes
usernamestringyes
yearsyes

No examples provided.

get_timeline ~120

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

NameTypeReqDescription
featuredbooleanOnly events marked as highlights
limitinteger
offsetinteger
pinnedbooleanOnly events the owner pinned
tagstringEvent tag: work | milestone | talk | side_quest | writing
usernamestringyesThe profile's @handle (its URL slug), e.g. "koshik"
yearinteger
NameTypeReqDescription
eventsarrayyes
totalnumberyesMatches before limit/offset
usernamestringyes

No examples provided.

search_events ~73

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

NameTypeReqDescription
limitinteger
querystringyes
usernamestringyesThe profile's @handle (its URL slug), e.g. "koshik"
NameTypeReqDescription
eventsarrayyes
totalnumberyes
usernamestringyes

No examples provided.