Klisten MeterMCP

kr.co.klisten.apiPublished by api.klisten.co.krOfficial publisherv0.1.0Updated Oct 24, 2026

Read your organization usage records. No payments or transfers. Customer API key required.

The publisher's own server: Klisten ToolGuard

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant read your organization's Klisten usage records using a customer API key.

What you can do
  • Read your organization's usage records from Klisten through the hosted endpoint.
  • No tool list is published, so the exact operations are not documented; the stated scope is reading usage data only.
  • No payments or transfers are offered.
When to use it
Useful when you want an assistant to look up and summarize your organization's Klisten usage records without leaving the chat, for example for quick reporting or checking consumption.
Requirements
A remote streamable HTTP endpoint at api.klisten.co.kr; no local package or runtime. Authentication is required via OAuth, with an Authorization header carrying a Bearer customer API key scoped to your product. Network access to the provider's API is needed.
Before you install
You must supply a customer API key in the Authorization header; treat it as a secret and keep it scoped to the product it was issued for. The server is stated to be read-only for usage records with no payments or transfers, but the tool list is not published, so confirm what it can access before connecting.

Installation

In SourceWeft

  1. Open Klisten MeterMCP 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/kr.co.klisten.api%2Fmetermcp/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": {
    "klisten-metermcp": {
      "type": "http",
      "url": "https://api.klisten.co.kr/mcp/metermcp"
    }
  }
}

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. v0.1.0LatestOct 12, 2026

Score

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

    Publish an icon in the registry entry.

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

Other Klisten integrations