Skip to content

API Meter MCP server

io.github.Surface-ops/api-meterSurface-opsstreamable-httpv1.0.1Scanned

Per-customer API usage analytics: sign up, get ingest snippets, read usage by customer and endpoint.

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the API Meter MCP server can do

The API Meter MCP server is published by the GitHub account Surface-ops. It has 4 tools. It can create or change data (3 tools: create_account, get_ingest_snippet and export_usage), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (create_account).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • create_accountSign up an API for API Meter (free to 250K requests/month).Reads text others writeNo findings

    Why it is in this group

    • The name "create_account" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Sign up an API for API Meter (free to 250K requests/month). Returns the slug, ingest key, dashboard key and proxy URL. Keys are shown once: store them. Limited to 5 signups per hour per network.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • export_usageBilling-ready monthly usage rows (same as /api/export): view=detail (customer x plan x method x endpoint) or view=customers.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Billing-ready monthly usage rows (same as /api/export): view=detail (customer x plan x method x endpoint) or view=customers. Returns JSON rows, or CSV text with format=csv.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_ingest_snippetCopy-paste server code that reports each request (method, route, status, latency, customer, plan) to API Meter.1 finding

    Why it is in this group

    • The name "get_ingest_snippet" says "get": a word for reading.
    • The description's first verb is "copy": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_ingest_snippet" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_ingest_snippet" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Copy-paste server code that reports each request (method, route, status, latency, customer, plan) to API Meter. Batched, fail-open, never blocks your API.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • get_usageMonthly (UTC) usage for one API, grouped by customer, endpoint or plan.No findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.
    Description, as the server wrote it
    Monthly (UTC) usage for one API, grouped by customer, endpoint or plan. Includes an agent bucket: requests whose plan label ends in '-agent' (AI agent / bot traffic, counted and billed like any request).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api-meter-lab.pages.dev/mcp: tools/list returned 4 tools to an anonymous client, including create_account (write), get_ingest_snippet (write), export_usage (write)

    What this check looks for

Posture changes

  1. Nov 8, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
  2. Oct 31, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_ingest_snippet" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_ingest_snippet" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
  3. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http api-meter https://api-meter-lab.pages.dev/mcp
claude mcp add --transport http api-meter https://api-meter-lab.pages.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__api-meter__get_usage"
    ],
    "ask": [
      "mcp__api-meter__create_account",
      "mcp__api-meter__get_ingest_snippet",
      "mcp__api-meter__export_usage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as api-meter. Review it before you use it.

Capability tags behind 1 rule
  • mcp__api-meter__create_account untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Surface-ops/api-meter/verify?hash=8238804b84e87230704e0bccb2af8d497f08e8e2916aaa723ad07d5a60d47c96" | jq -e '.changed == false'

Pinned hash 8238804b84e8, from Nov 9, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Surface-ops/api-meter/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Surface-ops/api-meter
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Surface-ops/api-meter.svg)](https://radar.anlyon.com/servers/io.github.Surface-ops/api-meter)

Source: MCP Registry · repository. Synced Oct 26, 2026, 15:17 UTC.

API Meter MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the API Meter MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the API Meter MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the API Meter MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the API Meter MCP server have?

4 tools: 3 write, 1 read. create_account, get_ingest_snippet, export_usage and get_usage.

Does the API Meter MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the API Meter MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the API Meter MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 26, 2026. Every change is on this page and in its Atom feed.