MCP.Market

logr MCP server

online · 100% uptime
by logr.it·it.logr/mcp·v1.0.0·1 stars

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

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed logr yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

logr tools (6)

write = sends, deletes, buys or posts
  • find_profilesFree

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

  • get_contextFree

    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.

  • get_eventFree

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

  • get_profileFree

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

  • get_timelineFree

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

  • search_eventsFree

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

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1109ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 36 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year5/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How logr compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
478 ms
faster than 31% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 6 read

Install logr in Claude Code, Cursor or VS Code

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

What the publisher says

From the logr repository's README, as published. We do not edit it. Read it on GitHub

logr

A personal portfolio + AI context layer. Most people have a LinkedIn. Nobody has a structured, machine-readable, queryable version of their story that works with any AI tool. logr fills that gap — an editorial life-log that is beautiful for humans to read and structured for AI to query.

You log your story once. It becomes three things:

  • a timeline at logr.it/you — year-grouped, hover-to-expand, in your choice of 9 palettes × 8 layouts,
  • machine-readable Markdown context any AI agent can ingest — the real moat, and
  • a grounded AI chat widget where visitors ask questions answered strictly from your log.

See ROADMAP.md for what's built and what's next.

Features

  • Multi-user — sign in with Google, claim a handle at /welcome, edit at /dashboard with a live preview.
  • AI import — paste your story, upload a resume (PDF/DOCX), or point at a URL; AI structures it into timeline events you review and confirm before anything is saved.
  • Grounded chat — the visitor chat is prompted with the same complete Markdown context as the public routes, streams via OpenRouter, and is rate-limited. Facts-only: if it's not in your log, it says so.
  • Theming — 9 palettes (incl. dark ink) × 8 layouts (timeline, journal, magazine, terminal, feed, card, centered, polaroid), persisted per profile, previewable live.
  • Pinned events — pin up to 7 events from the dashboard events tab (pins dialog); they replace the "recent" side rail (and the OG image's rail) and are marked in the Markdown context.
  • Media — image upload (S3, or local FS in dev), video/tweet embeds, unfurled link cards, dynamic OG image per profile.

Chat, S3, and Google auth are each feature-gated on their env vars and degrade gracefully when unset.

Routes

Tech stack

Next.js 16 (App Router) · React 19 · TypeScript · Postgres (Supabase) + Prisma 6 · Auth.js (NextAuth v5, Google OAuth) · Vercel AI SDK via OpenRouter · AWS S3 (local FS in dev) · Tailwind v4 + scoped CSS driven by theme tokens · Source Serif 4 + JetBrains Mono · Vercel.

Running locally

npm install
cp .env.example .env     # fill in the values below
npx prisma migrate dev   # applies migrations to your Postgres
npm run db:seed          # loads a demo profile + ~18 events
npm run dev              # http://localhost:3000

.env (see .env.example for details):

  • DATABASEURL / DIRECTURL — Supabase Postgres; transaction pooler (:6543, ?pgbouncer=true) for runtime, session (:5432) for prisma migrate.
  • AUTHSECRET + AUTHGOOGLEID / AUTHGOOGLE_SECRET — Google sign-in for /dashboard and onboarding.
  • OPENROUTERAPIKEY — optional; enables the visitor chat + AI import (OPENROUTER_MODEL to override the default model).
  • AWS_* — optional; S3 image storage (falls back to ./public/uploads).

Project structure

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

logr: common questions

Is logr MCP server safe?
Mostly: it is graded B (83/100). Read the logr safety report
How do I install logr?
It runs remotely at logr.it. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does logr need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is logr maintained?
The last commit was 78 days ago (2026-08-18). The latest release is v1.0.0.
Is logr up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does logr compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.