Skip to content

Agent Billing Primitives (Dirtsmith) MCP server

io.github.throttler300/mcp-usage-meteringthrottler300streamable-httpv1.4.0Scanned

Usage metering, spend cap (reserve before pay), lease lock, semaphore, heartbeat for agents. Free tr

5 tools: 5 change things.

Tools: 0 delete, 0 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 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 Agent Billing Primitives (Dirtsmith) MCP server can do

The Agent Billing Primitives (Dirtsmith) MCP server is published by the GitHub account throttler300. It has 5 tools. It can create or change data (5 tools: mcp_usage_metering, agent_spend_ledger, agent_lease_lock, agent_semaphore and 1 more), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

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

Last scanned Nov 18, 2026, version 1.4.0.

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.

5 tools

Changes things 5Claude Code: ask
  • agent_heartbeat_registryHeartbeat registry / dead-man switch / liveness check for AI agents: agents beat with an interval and grace; list_stale shows which agents went silent or crashed.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.
    Description, as the server wrote it
    Heartbeat registry / dead-man switch / liveness check for AI agents: agents beat with an interval and grace; list_stale shows which agents went silent or crashed. Idempotent, shared by namespace. Every call requires a tiny solved packet (returned in the reply, 2 s, one try); free first call, no API key (GET /try?tool=agent_heartbeat_registry).
  • agent_lease_lockDistributed lock / lease lock (mutex) for AI agents: acquire, renew, release a named lock with TTL and a monotonic fencing token so only one agent runs a job at a time.No findings

    Why it is in this group

    • The name "agent_lease_lock" says "lock": a word for a change.
    Description, as the server wrote it
    Distributed lock / lease lock (mutex) for AI agents: acquire, renew, release a named lock with TTL and a monotonic fencing token so only one agent runs a job at a time. Idempotent, shared by namespace, no Redis needed. Every call requires a tiny solved packet (returned in the reply, 2 s, one try); free first call, no API key (GET /try?tool=agent_lease_lock).
  • agent_semaphoreCounting semaphore / concurrency limit for AI agents: at most N agents hold a slot at once (rate limit parallel workers), TTL permits with fencing tokens, auto-expire on crash.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.
    Description, as the server wrote it
    Counting semaphore / concurrency limit for AI agents: at most N agents hold a slot at once (rate limit parallel workers), TTL permits with fencing tokens, auto-expire on crash. Idempotent, shared by namespace. Every call requires a tiny solved packet (returned in the reply, 2 s, one try); free first call, no API key (GET /try?tool=agent_semaphore).
  • agent_spend_ledgerAgent spend cap / budget ledger: set a budget, reserve before pay (atomic, never overspends even with many agents in parallel), then settle or release.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.
    Description, as the server wrote it
    Agent spend cap / budget ledger: set a budget, reserve before pay (atomic, never overspends even with many agents in parallel), then settle or release. Idempotent, shared by namespace. Spending limit, budget guard, cost control for AI agents. Every call requires a tiny solved packet (returned in the reply, 2 s, one try); free first call, no API key (GET /try?tool=agent_spend_ledger).
  • mcp_usage_meteringUsage metering for MCP tools and AI agents: record a billable usage event per tool call (idempotent, idempotency_key dedupes retries) and get an invoice line preview.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.
    Description, as the server wrote it
    Usage metering for MCP tools and AI agents: record a billable usage event per tool call (idempotent, idempotency_key dedupes retries) and get an invoice line preview. Per-call billing, usage-based pricing, metered billing for MCP servers. Every call requires one solved task: a tiny data packet, OR (this tool only) a public item: one line of public-domain text plus a deterministic format conversion (snake_case, word count, uppercase) with a known answer, returned as item_alternative; answer it within 2 s via item:{item_id, answer}. Verified answers are stored and readable at GET /items. Free first call, no API key (GET /try). Pay-ahead: every response carries next_work_packet; pass work_answer {work_packet_id, labels} on your next call (under 2 s) instead of solving a fresh packet. That work is our own internal classification (Buyer Zero), not customer data.

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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 18, 2026, 16:23 UTC, unchanged since Nov 11, 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
5
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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://gap-functions.bfurrow26.workers.dev/mcp: tools/list returned 5 tools to an anonymous client, including mcp_usage_metering (write), agent_spend_ledger (write), agent_lease_lock (write), agent_semaphore (write), agent_heartbeat_registry (write)

    What this check looks for

Posture changes

  1. Nov 11, 2026
    • Tools that change things, listed without credentials: 3 to 5

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. Tools1 changed.~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 5.View diff
    • Tools that change things, listed without credentials: 3 to 5
  3. Tools1 changed.~1 changedView diff
  4. Tools2 added, 3 changed.+2 added~3 changedView diff

Install

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

claude mcp add --transport http usage-metering https://gap-functions.bfurrow26.workers.dev/mcp
claude mcp add --transport http usage-metering https://gap-functions.bfurrow26.workers.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": [],
    "ask": [
      "mcp__usage-metering__mcp_usage_metering",
      "mcp__usage-metering__agent_spend_ledger",
      "mcp__usage-metering__agent_lease_lock",
      "mcp__usage-metering__agent_semaphore",
      "mcp__usage-metering__agent_heartbeat_registry"
    ],
    "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 usage-metering. Review it before you use it.

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.throttler300/mcp-usage-metering/verify?hash=955c8747b7561433c6d85e9c29b77e7faf9baabd890ed4a38328139fb4a0a846" | jq -e '.changed == false'

Pinned hash 955c8747b756, from Nov 18, 2026, 10: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.throttler300/mcp-usage-metering/changes.xml

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

Badge

Anlyon Radar badge for io.github.throttler300/mcp-usage-metering
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.throttler300/mcp-usage-metering.svg)](https://radar.anlyon.com/servers/io.github.throttler300/mcp-usage-metering)

Source: MCP Registry · repository. Synced Nov 4, 2026, 16:18 UTC.

Agent Billing Primitives (Dirtsmith) MCP server: questions and answers

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

Is the Agent Billing Primitives (Dirtsmith) MCP server safe?

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

Can the Agent Billing Primitives (Dirtsmith) MCP server delete data?

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

Can the Agent Billing Primitives (Dirtsmith) 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 Agent Billing Primitives (Dirtsmith) MCP server have?

5 tools: 5 write. mcp_usage_metering, agent_spend_ledger, agent_lease_lock, agent_semaphore and agent_heartbeat_registry.

Does the Agent Billing Primitives (Dirtsmith) MCP server need sign-in or OAuth?

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

Does the Agent Billing Primitives (Dirtsmith) MCP server send data to outside services?

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

Has the Agent Billing Primitives (Dirtsmith) MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.