Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agency Capacity

REMOTE · CONNECT.AGILEGROWTHLABS.COM

Capacity benchmarks, capacity math and Portable Delivery Intelligence for marketing agencies.

+3 this week 84 Trust /100

Last scanned (8 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Project Management

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 609 tokens (~121/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 Management68
  • Stability check failed: schema churn in the 29 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
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
Changelog

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

    No change was recorded against any check on this day. Stability & Change Management went from 61 to 65.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 55 to 58.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 48 to 51.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 41 to 45.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 35 to 38.

  • 26 Oct 26 −3
    • Stability: 0.60 → fail ▼ security
    • Tool “add_to_benchmark” was removed ▼ security
    • Tool “approval_checklist” was removed ▼ security
    • Tool coverage: 84% → 100% ▲ functional
    • Schema quality: 842 → 609 ▲ functional
    • Server version: 1.0.0 → 1.0.1 functional
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Probed https://connect.agilegrowthlabs.com/capacity

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agilegrowthlabs.com CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 46d80d0dac3b238f135be25a0e6732ae
SANs: agilegrowthlabs.com, connect.agilegrowthlabs.com, *.connect.agilegrowthlabs.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of connect.agilegrowthlabs.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agilegrowthlabs.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=31536000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://connect.agilegrowthlabs.com/capacity Verified 200
http (plaintext) http://connect.agilegrowthlabs.com/capacity HTTPS enforced 301 https://connect.agilegrowthlabs.com/capacity
MCP tools · 5 exposed · ~557 tokens

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 →

Tool Tokens
capacity_benchmarks ~62

Returns published benchmarks on accounts per account manager, time spent re-briefing AI, and rework of AI output, each with its source link. Use when the user asks what is normal for agencies.

NameTypeReqDescription
topicstring–Which benchmarks to return.

No output schema declared.

No examples provided.

capacity_check ~204

Estimates an agency's accounts per account manager, yearly coordination cost, and how many more accounts the same team could carry at a target ratio. Use when the user shares client and team numbers and asks about capacity, hiring, or account manager load. Returns an estimate, not a guarantee.

NameTypeReqDescription
account_managersintegeryesPeople who own client accounts day to day.
active_clientsintegeryesActive client accounts.
avg_monthly_retainernumber–Average monthly retainer per client in USD. Optional.
gross_margin_pctnumber–Gross margin percent. Optional.
hours_lost_per_am_per_weeknumber–Hours each account manager loses per week to re-briefing AI, chasing approvals, fixing work and reporting. Optional.
loaded_hourly_costnumber–Loaded hourly cost of an account manager in USD. Optional.
target_accounts_per_amnumber–Target accounts per account manager. Default 18.

No output schema declared.

No examples provided.

client_context_template ~101

Returns a fill-in template for a 1-file client context document (goals, voice, claims rules, priorities, approvals, decisions) for a service line. Use when the user wants AI tools or new teammates to stop needing a client re-brief.

NameTypeReqDescription
client_namestring–Optional client name to put in the title.
service_linestring–general, seo, paid_media, content, lifecycle, or automation. Default general.

No output schema declared.

No examples provided.

define_term ~57

Defines an agency AI operations term, such as Portable Delivery Intelligence, accounts per person, re-brief tax, or AI operations sprawl. Leave term empty to list all terms.

NameTypeReqDescription
termstring–The term to define. Optional.

No output schema declared.

No examples provided.

rebrief_tax ~133

Estimates the monthly hours and cost a team spends explaining clients to AI tools before they do useful work. Use when the user asks what re-briefing AI or re-pasting client context costs.

NameTypeReqDescription
accounts_per_personnumberyesAccounts each person works on.
hourly_costnumber–Loaded hourly cost in USD. Optional.
minutes_per_rebriefnumberyesMinutes spent loading client context into a new AI chat.
peopleintegeryesPeople who use AI on client work.
rebriefs_per_account_per_weeknumberyesNew AI chats per account per person each week.

No output schema declared.

No examples provided.

Install

How do I install the Agency Capacity MCP server?

Agency Capacity is a hosted endpoint at https://connect.agilegrowthlabs.com/capacity, 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 · connect.agilegrowthlabs.com

# add to Claude Code
claude mcp add --transport http com-agilegrowthlabs-agency-capacity 'https://connect.agilegrowthlabs.com/capacity'
Common questions

What is the Agency Capacity MCP server?

Agency Capacity is an MCP server listed in the public MCP registry as com.agilegrowthlabs/agency-capacity. Capacity benchmarks, capacity math and Portable Delivery Intelligence for marketing agencies. This page covers its hosted endpoint (https://connect.agilegrowthlabs.com/capacity).

Is the Agency Capacity MCP server safe to use?

Agency Capacity scores 84 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 Agency Capacity MCP server expose?

Agency Capacity exposes 5 tools: capacity_check, rebrief_tax, capacity_benchmarks, client_context_template, define_term. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.

Does the Agency Capacity MCP server require authentication?

No. We connected to Agency Capacity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agency Capacity MCP server still maintained?

Agency Capacity is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.