Lomen

io.github.MrBananKaka123Published by GitHub account MrBananKaka123v1.0.0Updated Oct 24, 2026

Ask about your website traffic, sources and AI insights from Lomen analytics

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Lets an assistant query website traffic, traffic sources and AI insights from Lomen analytics.

What you can do
Lomen is a remote analytics service exposed over streamable HTTP. According to its description, it lets an assistant ask about a website's traffic, where visitors come from, and AI-generated insights. No individual tools are listed in the supplied material.
When to use it
Useful when you want to ask questions about your own site's traffic and referral sources in conversation, or pull Lomen's AI insights without opening the analytics dashboard.
Requirements
A remote endpoint at lomenanalytics.com reached over streamable HTTP, plus OAuth authentication, which the manifest marks as required. No environment variables, headers or local packages are declared.
Before you install
Access is granted through OAuth, so the assistant can read whatever analytics data that account can see; review the scopes requested during sign-in. The supplied material does not describe write actions or third-party data sharing.

Installation

In SourceWeft

  1. Open Lomen in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.MrBananKaka123%2Flomen/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lomen": {
      "type": "http",
      "url": "https://lomenanalytics.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.