Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Exact staffing math: FTE needed, a monthly hiring plan, and Erlang C queue staffing.
0 failed · 7 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 1 | 0 | 3 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Staffing Math
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http staffing-math https://staffing-math.vercel.app/mcpCapabilities
For call center, contact center, phone or chat staffing questions with a service level target, such as 80% answered within 20 seconds. Works out agents needed on a live queue to answer a target share of contacts within a target time, using Erlang C. Give contacts per hour for the interval being staffed (usually the busiest hour) and handle time in seconds. Returns agents needed, the service level at that number and at one fewer, chance of waiting, occupancy, and people to schedule after shrinkage. Use required_fte for case or ticket work with no answer-time target.
DiscoveredFor hiring plans, headcount plans, and questions about when to open requisitions or how many people to hire as volume grows, shrinks or changes by season. Plans month by month how many requisitions to open so FTE on hand keeps up with FTE needed. A requisition adds capacity only after time to hire and ramp, and attrition removes people every month, so the plan opens reqs ahead of need and flags the months that run short before any new hire can count. Give weekly_volume with monthly_growth (0.05 means 5% a month, compounding), or weekly_volume_by_month. Unknown inputs fall back to stated defaults: current headcount defaults to what month 1 needs, attrition to 0, time to hire to 2 months, ramp to 0. When attrition is assumed, the result also gives the plan at 15% and 30%. Give hires_in_flight for people already hired or in the pipeline. Returns the plan table, totals, the arithmetic, and which inputs were assumed. A hire counts as zero capacity until fully ramped. Hosts that support MCP Apps also draw the plan as a chart with controls that rerun it.
DiscoveredFor questions like "how many people do I need" or "how many FTE does this workload take": cases, tickets, claims, orders or any work measured as volume times handling time. Applies shrinkage and target occupancy together; leaving out occupancy understates the people needed by about 15% at the 85% default. Give weekly volume and minutes per case; shrinkage, target occupancy and hours per week fall back to stated defaults. Returns FTE, people to staff (rounded up), every input marked given or assumed, and the arithmetic with numbers filled in. For volume that changes over time or any question about when to hire, see hiring_plan; for live queues with an answer-time target, see erlang_staffing.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 1176 ms | 3 | |
| Connected | 466 ms | 3 |