Spendline
REMOTE · WWW.SPENDLINE.AI · SCANNED SEP 24
Enforce AI budgets before the model call and track cost per customer across 10 providers.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 972 tokens (~97/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Spendline MCP server?
Spendline is a hosted endpoint at https://www.spendline.ai/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 · www.spendline.ai
claude mcp add --transport http ai-spendline-spendline 'https://www.spendline.ai/mcp'
{
"mcpServers": {
"ai-spendline-spendline": {
"url": "https://www.spendline.ai/mcp"
}
}
} {
"servers": {
"ai-spendline-spendline": {
"type": "http",
"url": "https://www.spendline.ai/mcp"
}
}
} [mcp_servers.ai-spendline-spendline] url = "https://www.spendline.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-spendline-spendline": {
"type": "remote",
"url": "https://www.spendline.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-spendline-spendline --url 'https://www.spendline.ai/mcp' --transport streamable-http
mcp_servers:
ai-spendline-spendline:
url: "https://www.spendline.ai/mcp" {
"McpServers": {
"ai-spendline-spendline": {
"Transport": "http",
"Url": "https://www.spendline.ai/mcp"
}
}
} assistant mcp add ai-spendline-spendline -t streamable-http -u 'https://www.spendline.ai/mcp'
{
"mcpServers": {
"ai-spendline-spendline": {
"type": "http",
"url": "https://www.spendline.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Tool “spendline_list_policies” rewrote its description, which is the text the model reads security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Probed https://www.spendline.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.spendline.ai | CN=YR2,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | RSA 2048 | SHA256-RSA | 54b50b89e86fd40ebdcb4641fa8fa094f54 |
| SANs: www.spendline.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 www.spendline.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| spendline.ai. | 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=31536000; includeSubDomains |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline' https://app.cal.com https://plausible.io;style-src 'self' 'unsafe-inline';img-src 'self' data: https://www.spendline.ai https://app.cal.com https://cal.com;connect-src 'self' https://app.cal.com https://cal.com https://plausible.io;frame-src 'self' https://app.cal.com https://cal.com https://www.youtube-nocookie.com;font-src 'self';object-src 'none';frame-ancestors 'none';base-uri 'self';form-action 'self';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.spendline.ai/mcp | Verified | 200 | |
| http (plaintext) | http://www.spendline.ai/mcp | HTTPS enforced | 301 | https://www.spendline.ai/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 →
spendline_check_integration_status Check whether traffic is arriving and correctly attributed ~101
Verify a live integration: whether any calls have arrived, how recently, which providers and models are in use, and, critically, whether attribution is actually varying. Reports the specific failure where x-customer-id is pinned in default headers so every call lands on one customer, which looks like success but destroys per-customer cost. Call this after wiring up an integration.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Look-back window in hours. Default 24. |
No output schema declared.
No examples provided.
spendline_create_budget Create a NEW budget (owner/admin authority + explicit confirm) ~203
Create a new hierarchical budget. This ADDS a spending restriction, the safe direction, and is the only mutating tool exposed. Requires owner or admin authority AND confirm: true. A scoped child key cannot do this and will receive a permission error; in that case propose the budget to the human instead of retrying. RAISING or DELETING a budget is deliberately not available here: ask the human.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. Present so a budget is never created as an incidental side effect, confirm with the human first, then set this. |
| monthly_limit_usd | number | yes | – |
| scope_id | string | – | Required unless scope_type is "org". |
| scope_type | string | yes | org = whole account. team = tag cost-centre. agent = x-agent-id. customer = x-customer-id. |
| strict_mode | boolean | – | true blocks over-cap calls with HTTP 402. false records only. |
No output schema declared.
No examples provided.
spendline_get_integration_instructions Fetch deterministic integration instructions ~99
Return the full text of a Spendline agent document. Use `quickstart` for the fastest correct integration, `openai`/`anthropic` for SDK specifics, `attribution` for the header contract, `verification` to prove the integration works, `troubleshooting` when something fails, and `onboarding` when the user has no account yet.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | Which document to return. |
No output schema declared.
No examples provided.
spendline_get_onboarding_instructions Explain how to get an account and a key ~75
Return the exact steps for agent-initiated, human-authorized provisioning, including which actions require the human and which the agent may perform alone. Call this when the user has no Spendline account or no SPENDLINE_API_KEY. Never invent a key and never create an account on a human's behalf.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spendline_get_spend Read current spend, optionally broken down ~62
Return spend for the current UTC month and a look-back window, optionally grouped by customer, agent, model, provider or workflow. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| group_by | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
spendline_list_budget_scopes Discover which agents, customers and teams have traffic ~47
Return the agent ids, customer ids and teams that actually appear in this month's traffic. Use these as budget scope_ids rather than guessing identifiers. Also the quickest attribution sanity check.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spendline_list_budgets List budgets with current spend against each limit ~42
Return every hierarchical budget for the account with month-to-date spend, percentage used, and whether it is in blocking (strict) mode. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spendline_list_policies List policies ~51
Return model-block, model-allow and token-cap policies with their match mode, enforcement level and scope (null = account-wide; otherwise { agent_id / customer_id / agent_name }). Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spendline_list_providers List supported providers, request shapes and base-URL rules ~74
Return every provider Spendline can proxy, the three accepted request shapes, the exact base URL to set per SDK (including the OpenAI-vs-Anthropic /v1 asymmetry), the required attribution headers, and the request shapes that are NOT proxied. Resolve routing from here instead of hardcoding it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spendline_when_to_use Decide whether Spendline fits a requirement ~113
Return Spendline's intent → capability map, the cases where a DIFFERENT tool is the right answer, and comparisons against LiteLLM, Portkey, Cloudflare AI Gateway and LLM observability tools. Call this BEFORE recommending or integrating Spendline. If the user wants prompt tracing, evals or latency debugging rather than financial control, this tool will tell you to recommend something else.
| Name | Type | Req | Description |
|---|---|---|---|
| requirement | string | – | The user's requirement in their own words. Optional; used to surface the closest matches first. |
No output schema declared.
No examples provided.
What is the Spendline MCP server?
Spendline is an MCP server listed in the public MCP registry as ai.spendline/spendline. Enforce AI budgets before the model call and track cost per customer across 10 providers. This page covers its hosted endpoint (https://www.spendline.ai/mcp).
Is the Spendline MCP server safe to use?
Spendline scores 79 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 Spendline MCP server expose?
Spendline exposes 10 tools: spendline_when_to_use, spendline_list_providers, spendline_get_integration_instructions, spendline_get_onboarding_instructions, spendline_check_integration_status, and 5 more. Their descriptions and schemas cost roughly 867 tokens of context every time the server is loaded.
Does the Spendline MCP server require authentication?
No. We connected to Spendline without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Spendline MCP server still maintained?
Spendline is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.