API Meter
io.github.Surface-ops/api-meterSurface-opsstreamable-httpv1.0.0Scanned
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.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →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".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_ingest_snippet" says "get": a word for reading.
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.
Findings
Matches of fixed checks, with the text they matched.
The server marks "get_ingest_snippet" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_ingest_snippet" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http api-meter https://api-meter-lab.pages.dev/mcpclaude mcp add --transport http api-meter https://api-meter-lab.pages.dev/mcpRun 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.
{
"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://anlyon.dev/api/v1/servers/io.github.Surface-ops/api-meter/verify?hash=1a769ca0625d64d161ccf9f13ac5c4d51f14110b7b81ebac3c6a41f9e2608bfb" | jq -e '.changed == false'Pinned hash 1a769ca0625d, from Oct 24, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.Surface-ops/api-meter/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.Surface-ops/api-meter)Source: MCP Registry · repository. Synced Oct 24, 2026, 12:17 UTC.