Agent Cost Log
REMOTE · COSTLOG.CLOUDFORBOTS.COM
Cost per run, tool, model and day for AI agents, from one call or an OpenTelemetry export.
Available components
Last scanned (11 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Monitoring and Observability
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 Security63
- 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 4 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 536 tokens (~134/item across 4 items; 4 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 Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 17 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 64
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 17 Oct 2026 · Probed https://costlog.cloudforbots.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=costlog.cloudforbots.com | CN=YR1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 59bb71fcf9d86c23306f0e268b93ea9d5a0 |
| SANs: costlog.cloudforbots.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of costlog.cloudforbots.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cloudforbots.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://costlog.cloudforbots.com/mcp | Verified | 200 | |
| http (plaintext) | http://costlog.cloudforbots.com/mcp | HTTPS enforced | 308 | https://costlog.cloudforbots.com/mcp |
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 →
cost_report ~75
Cost per run, per tool, per model and per day. Without an API key pass run_id (one run). With a key: everything on that key. Free shows 7 days, Pro 30.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | 1-30 (free max 7). |
| run_id | string | – | – |
No output schema declared.
No examples provided.
log_costs ~268
Log what your agent's model and tool calls cost, then get the running total for the run and for today. Pass events (one per call, up to 500) or an OpenTelemetry OTLP/JSON trace export as otel (gen_ai.usage.input_tokens / output_tokens / gen_ai.request.model are read; trace id becomes run_id). Give cost_usd per call, or tokens plus your own per-million prices; nothing is guessed. Optional caps: run_cap_usd and daily_cap_usd. Free watch-only returns would_alert when a cap is crossed; Pro posts one alert per day to alert_webhook. Never blocks or changes your agent.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_webhook | string | – | https URL Pro posts the cap alert to. |
| daily_cap_usd | number | – | – |
| events | array | – | – |
| otel | object | – | OTLP/JSON export: { resourceSpans: [...] }. |
| price_in_per_m | number | – | Default input USD per 1M tokens for events without cost_usd. |
| price_out_per_m | number | – | Default output USD per 1M tokens. |
| run_cap_usd | number | – | – |
| run_id | string | – | Stable id for this run (default "default"). |
No output schema declared.
No examples provided.
usage_and_upgrade ~37
Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weekly_report ~46
Plain-English summary of the last 7 days of spend: total, top runs, top tools, top models, busiest day. Read-only; sends nothing. Needs a free API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Agent Cost Log MCP server?
Agent Cost Log is a hosted endpoint at https://costlog.cloudforbots.com/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 · costlog.cloudforbots.com
claude mcp add --transport http com-botrecipe-costlog 'https://costlog.cloudforbots.com/mcp'
What is the Agent Cost Log MCP server?
Agent Cost Log is an MCP server listed in the public MCP registry as com.botrecipe/costlog. Cost per run, tool, model and day for AI agents, from one call or an OpenTelemetry export. This page covers its hosted endpoint (https://costlog.cloudforbots.com/mcp).
Is the Agent Cost Log MCP server safe to use?
Agent Cost Log scores 64 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 Cost Log MCP server expose?
Agent Cost Log exposes 4 tools: log_costs, cost_report, weekly_report, usage_and_upgrade. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.
Does the Agent Cost Log MCP server require authentication?
No. We connected to Agent Cost Log without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Cost Log MCP server still maintained?
Agent Cost Log is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.