Agent Billing Primitives (Dirtsmith)
REMOTE · GAP-FUNCTIONS.BFURROW26.WORKERS.DEV
Usage metering, spend cap (reserve before pay), lease lock, semaphore, heartbeat for agents. Free tr
Available components
Last scanned (13 hours ago)
Scores higher than 42% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability44
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1024 tokens (~204/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “agent_heartbeat_registry” rewrote its description, which is the text the model reads security
- Tool “agent_lease_lock” rewrote its description, which is the text the model reads security
- Tool “agent_semaphore” rewrote its description, which is the text the model reads security
- Tool “agent_spend_ledger” rewrote its description, which is the text the model reads security
- Tool “mcp_usage_metering” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → poor functional
- New tool “agent_heartbeat_registry” functional
- New tool “agent_semaphore” functional
- New tool “agent_lease_lock” functional
- New tool “agent_spend_ledger” functional
- 3 Nov 26 53
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://gap-functions.bfurrow26.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bfurrow26.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 50319db8e224b31328599f411c0ac4ebd73 |
| SANs: *.bfurrow26.workers.dev, bfurrow26.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gap-functions.bfurrow26.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gap-functions.bfurrow26.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://gap-functions.bfurrow26.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_heartbeat_registry ~159
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).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| agent_id | string | – | – |
| caller_id | string | – | – |
| grace_s | integer | – | – |
| idempotency_key | string | yes | – |
| interval_s | integer | – | – |
| namespace | string | yes | – |
| note | string | – | – |
| source | – | – | – |
No output schema declared.
No examples provided.
agent_lease_lock ~161
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).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| caller_id | string | – | – |
| holder_id | string | – | – |
| idempotency_key | string | yes | – |
| lock_name | string | yes | – |
| namespace | string | yes | – |
| source | – | – | – |
| ttl_s | integer | – | – |
No output schema declared.
No examples provided.
agent_semaphore ~167
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).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| caller_id | string | – | – |
| holder_id | string | – | – |
| idempotency_key | string | yes | – |
| max_slots | integer | – | – |
| namespace | string | yes | – |
| permit_id | string | – | – |
| semaphore | string | yes | – |
| source | – | – | – |
| ttl_s | integer | – | – |
No output schema declared.
No examples provided.
agent_spend_ledger ~190
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).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| amount_micros | integer | – | – |
| budget_id | string | yes | – |
| caller_id | string | – | – |
| idempotency_key | string | yes | – |
| limit_micros | integer | – | – |
| memo | string | – | – |
| namespace | string | yes | – |
| reservation_id | – | – | – |
| source | – | – | – |
| ttl_s | integer | – | – |
No output schema declared.
No examples provided.
mcp_usage_metering ~236
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).
| Name | Type | Req | Description |
|---|---|---|---|
| caller_id | string | – | – |
| end_customer_ref | string | yes | – |
| idempotency_key | string | yes | – |
| metadata | object | – | – |
| source | – | – | – |
| tool_name | string | yes | – |
| tool_version | string | yes | – |
| unit_label | string | – | – |
| unit_price_cents | integer | – | – |
| units | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Agent Billing Primitives (Dirtsmith) MCP server?
Agent Billing Primitives (Dirtsmith) is a hosted endpoint at https://gap-functions.bfurrow26.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gap-functions.bfurrow26.workers.dev
claude mcp add --transport http throttler300-mcp-usage-metering 'https://gap-functions.bfurrow26.workers.dev/mcp'
What is the Agent Billing Primitives (Dirtsmith) MCP server?
Agent Billing Primitives (Dirtsmith) is an MCP server listed in the public MCP registry as io.github.throttler300/mcp-usage-metering. Usage metering, spend cap (reserve before pay), lease lock, semaphore, heartbeat for agents. Free tr. This page covers its hosted endpoint (https://gap-functions.bfurrow26.workers.dev/mcp).
Is the Agent Billing Primitives (Dirtsmith) MCP server safe to use?
Agent Billing Primitives (Dirtsmith) scores 52 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Billing Primitives (Dirtsmith) MCP server expose?
Agent Billing Primitives (Dirtsmith) exposes 5 tools: mcp_usage_metering, agent_spend_ledger, agent_lease_lock, agent_semaphore, agent_heartbeat_registry. Their descriptions and schemas cost roughly 913 tokens of context every time the server is loaded.
Does the Agent Billing Primitives (Dirtsmith) MCP server require authentication?
No. We connected to Agent Billing Primitives (Dirtsmith) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Billing Primitives (Dirtsmith) MCP server still maintained?
Agent Billing Primitives (Dirtsmith) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.