Centipid ISP Billing

com.centipidbillingPublished by centipidbilling.comOfficial publisherv1.1.0Updated Oct 24, 2026

Query your ISP's revenue, subscribers, payments and routers. Needs a Centipid account and API key.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant query an ISP's Centipid billing data: revenue, subscribers, payments and routers.

What you can do
Centipid ISP Billing is a remote MCP server that connects an assistant to an ISP's Centipid billing account. According to the registry description, it lets the assistant query revenue, subscribers, payments and routers. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when an ISP operator wants an assistant to look up billing figures, subscriber counts, payment records or router information from Centipid without opening the billing app.
Requirements
A remote endpoint at mcp.centipidbilling.com over streamable HTTP. Requires a Centipid account and an API key created in the Centipid billing app under Settings, Developer, sent as a Bearer token in the Authorization header. OAuth authentication is declared as required.
Before you install
The Authorization header carries a secret API key that identifies the ISP and carries that operator's permissions, so treat it as sensitive and avoid exposing it in logs or shared transcripts. The key's scope determines what the assistant can reach; the manifest does not say whether any tools write or change billing data.

Installation

In SourceWeft

  1. Open Centipid ISP Billing 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/com.centipidbilling%2Fbilling/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": {
    "centipid-isp-billing": {
      "type": "http",
      "url": "https://mcp.centipidbilling.com/mcp"
    }
  }
}

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

2
  1. v1.1.0LatestSep 24, 2026
  2. v1.0.1Sep 16, 2026

Score

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