nitur

io.github.AmarShakedPublished by GitHub account AmarShakedv1.0.0Updated Oct 24, 2026

Create projects and read their web analytics: views, referrers, countries, custom events.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Nitur lets an assistant create projects and read their web analytics — views, referrers, countries and custom events — from a hosted endpoint.

What you can do
  • Create and manage analytics projects.
  • Read traffic metrics such as views, referrers and visitor countries.
  • Inspect custom events recorded for a project.
When to use it
Useful when you want an assistant to set up a Nitur analytics project or pull its traffic and event numbers into a conversation, report or follow-up analysis without opening the dashboard.
Requirements
A remote MCP endpoint at nitur.dev over streamable HTTP. Requires a bearer token sent in the Authorization header: an API key created on your Nitur account page. The same key covers both the REST API and this server.
Before you install
The server needs an account API key in the Authorization header; treat it as a secret and avoid exposing it in shared logs or configs. Creating projects and reading analytics data changes or exposes data in your Nitur account, and the data is held by a third-party service.

Installation

In SourceWeft

  1. Open nitur in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.AmarShaked%2Fnitur/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.

{
  "mcpServers": {
    "nitur": {
      "type": "http",
      "url": "https://nitur.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

39% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

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