Kenda

io.github.kenda-coPublished by GitHub account kenda-cov0.2.0Updated Oct 24, 2026

Read-only MCP server for querying Kenda token spend and waste

VerifiedSTDIODesktop onlyData & Analytics

Server details

Identifier: io.github.kenda-co/ingestion-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account kenda-co for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.kenda-co%2Fingestion-mcp.svg)](https://sourceweft.com/mcp/io.github.kenda-co%2Fingestion-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Read-only local MCP server that lets an assistant query Kenda for token spend and waste data.

What you can do: Query Kenda token spend and waste figures through a read-only connection.
No individual tools are documented in the manifest, so the exact queries available are not specified.
Configuration is read from a local Kenda config file, with optional environment overrides.
When to use it: Useful when you already use Kenda to track AI token usage and want an assistant to look up spend and waste figures while working in a desktop client.
Requirements: Runs as a local process on the user's machine, installed from the PyPI package ingestion-mcp over stdio; desktop only, not web-executable. Needs a Kenda ingest token (KENDA_TOKEN) and an API base URL (KENDA_ENDPOINT), normally written to ~/.kenda/config.json by kenda-collect init; both can be overridden by environment variable. Network access to the Kenda API is required.

Before you install

The KENDA_TOKEN is a per-customer ingest token and is a secret; keep it out of shared configs and logs. The server is described as read-only, but it sends queries and the token to the Kenda API endpoint, so confirm the endpoint is the one you intend.

Installation

In SourceWeft

Open Kenda in the dashboard and add it to a workspace.
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

This repository has no README.

Tools

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

Version history

v0.2.0LatestSep 16, 2026

Score

25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.