Negirau

io.github.sincekmoriPublished by GitHub account sincekmoriv0.3.3Updated Nov 7, 2026

Read-only, anonymous access to the Negirau public API: subjects and their reaction counts.

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

Read-only MCP access to the Negirau public API, letting an assistant look up subjects and their appreciation reaction counts.

What you can do
  • Look up subjects and their reaction counts through the Negirau public API
  • Search subjects server-side by query and find nearby subjects with bounded search
  • Retrieve only public, anonymous data, with no accounts or user-generated text involved
When to use it
Useful when you want an assistant to check how much appreciation a given subject (such as a fire station, event crew, online service or open-source project) has received, or to search for such subjects by name or location.
Requirements
Runs as a local stdio process installed from the npm package negirau-mcp, so Node.js is needed. It calls the public API at api.negirau.com by default; the NEGIRAU_BASE_URL environment variable can point it at a different base URL. No account or API key is required.
Before you install
The server is read-only and anonymous, so it does not write, send or delete data. Counts are capped by design: values above 100 are shown as "100+" and there are no ranking or bulk-dump endpoints, so it cannot be used for leaderboards or full exports. Setting NEGIRAU_BASE_URL redirects requests to another host, so only change it to an endpoint you trust.

Installation

In SourceWeft

  1. Open Negirau in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Negirau

[CI] [License] [npm negirau] [npm negirau-mcp] [PyPI negirau] [Negirau]

日頃の担い手に、ねぎらいを。 Negirau (negirau.com) lets anyone send a one-tap, login-free appreciation to the people behind everyday work — fire stations, event crews, online services, open-source maintainers.

  • No accounts, no user-generated text, no visitor data stored.
  • Counts are shown exactly up to 100 and as "100+" beyond — by design, this service cannot become a ranking.
  • Runs entirely on Cloudflare Workers + D1 within the free tier.

Development

Prerequisites: bun (plus pnpm for packages/client-ts and packages/mcp-server, and uv for packages/client-py).

bun installcp .dev.vars.example .dev.varsbun run db:migrate && bun run db:seedbun run dev

See AGENTS.md for the full check list, architecture invariants, and gotchas.

Repository layout

PathWhatLicense
/ (server + web app)React Router 7 app on Cloudflare WorkersAGPL-3.0-only
packages/client-tsTypeScript API client (npm), hand-written + spec contract testsApache-2.0
packages/client-pyPython API client (PyPI), hand-written + spec contract testsApache-2.0
packages/mcp-serverMCP server (npm), registers tools dynamically from the live specApache-2.0
skills/negirauAgent Skill (SKILL.md), generated from the route manifestApache-2.0

Everything under packages/ is held to the OpenAPI spec: both clients run spec-driven contract tests, mcp-server reads the live spec at startup, and SKILL.md is generated with a CI drift gate.

Public API

Read-only, anonymous, CORS-open, based at https://api.negirau.com/v1. The spec is served at /v1/openapi.json and generated from the zod schemas at build time — it cannot drift from the implementation. There are no bulk dumps and no ranking endpoints, on purpose: the lookup path is server-side search (q= on /v1/subjects) and bounded nearby search.

License

Copyright (C) 2026 Shinsuke Mori.

The server and web app are licensed under AGPL-3.0-only. Client packages under packages/ are licensed under Apache-2.0 (see each package's LICENSE). The "Negirau" name and the heart-pin logo are not covered by these licenses.

Attribution

Source: README.md at commit 35fd411

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.3.3LatestNov 7, 2026
  2. v0.3.2Sep 16, 2026

Score

50% 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 days25 pts

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

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts