Eclipse Meter MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 27, 2026

Cross-provider agent spend analytics — one ledger for tokens, tools, and payments.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Local stdio MCP server that gives an assistant a single ledger for cross-provider agent spend: tokens, tools and payments.

What you can do
  • The listing names no tools, so capabilities come only from the short description.
  • It is presented as cross-provider agent spend analytics.
  • It is meant to consolidate token, tool and payment costs into one ledger.
  • No further detail on queries, reports or data sources is provided.
When to use it
Consider it if you run agents across several providers and want their token, tool and payment costs tracked in one place for an assistant to consult. The listing gives no tool list or documentation, so confirm the actual capabilities before relying on it.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, not available as a web executable. No packages, environment variables, headers or authentication are declared, so how it is installed and where it gets spend data is not stated.
Before you install
Spend and payment data is sensitive financial information, and the listing does not say where the server reads it from or whether anything leaves the machine. No credentials are declared, but installation and data handling are undocumented; review the source before pointing it at real billing data.

Installation

In SourceWeft

  1. Open Eclipse Meter MCP 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.

Tools

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

Version history

1
  1. v0.1.0LatestOct 26, 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.