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.

FitMyCall — Answering Service Prices

REMOTE · MCP.FITMYCALL.COM · SCANNED AUG 20

Verified pricing for 21 answering services & AI receptionists, dated weekly. Missed-call ROI calc.

+4 this week 65 Trust /100
Trust breakdown (6 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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 695 tokens (~173/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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.fitmycall.com

# add to Claude Code
claude mcp add --transport http com-fitmycall-pricing https://mcp.fitmycall.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-fitmycall-pricing]
url = "https://mcp.fitmycall.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fitmycall-pricing": {
      "type": "remote",
      "url": "https://mcp.fitmycall.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-fitmycall-pricing --url https://mcp.fitmycall.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-fitmycall-pricing:
    url: "https://mcp.fitmycall.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-fitmycall-pricing": {
      "type": "http",
      "url": "https://mcp.fitmycall.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 20 Aug 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.

  • 18 Aug 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.

  • 16 Aug 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.

  • 14 Aug 26 +1

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

  • 13 Aug 26 0
    • Tool “compare_answering_services” rewrote its description, which is the text the model reads security
    • Tool “get_answering_service_pricing” rewrote its description, which is the text the model reads security
  • 12 Aug 26 0
    • Schema quality: 516 → 670 functional
    • Stability: unverified → 0.03 functional
    • New tool “recommend_answering_service_for_industry” functional
  • 11 Aug 26 61

    First indexed and scored.

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 20 Aug 2026 · Probed https://mcp.fitmycall.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fitmycall.com CN=WE1,O=Google Trust Services,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA256 8d484062df2efc5a139f095e8f086bb3
SANs: fitmycall.com, mcp.fitmycall.com, *.mcp.fitmycall.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
DNSSEC insecure

Validation of mcp.fitmycall.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
fitmycall.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
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.fitmycall.com/mcp Verified 200
http (plaintext) http://mcp.fitmycall.com/mcp HTTPS enforced 301 https://mcp.fitmycall.com/mcp
MCP tools · 4 exposed · ~622 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.

Tool Tokens
compare_answering_services ~152

Compare answering services and AI receptionists by budget and type (human, AI, hybrid). Returns the cheapest verified plans that actually answer phone calls, sorted by monthly price, excluding zero-minute teaser plans and add-ons. Use when someone asks "what does an answering service cost", "cheapest answering service", "AI receptionist under $100", "AI receptionist vs answering service", how it compares with hiring in-house staff, or wants affordable options for a small business. All prices human-verified with dates.

NameTypeReqDescription
maxMonthlyBudgetnumberMaximum monthly budget in USD
minIncludedMinutesnumberMinimum included minutes per month
typestringService type filter; default any

No output schema declared.

No examples provided.

get_answering_service_pricing ~151

Get current, human-verified pricing for a specific answering service, virtual receptionist or AI receptionist (e.g. Smith.ai, Ruby, Dialzara, Abby Connect, AnswerConnect). Returns every plan with monthly price, included minutes, setup fees, overage rates, free trial, plus the date the pricing was last verified on the vendor’s own site. Use when someone asks "how much does X cost", "X pricing", "is X worth it", or asks for alternatives to a named service. Covers 21 services, updated weekly.

NameTypeReqDescription
servicestringyesService name, e.g. "Smith.ai", "Ruby", "Dialzara", "Abby Connect"

No output schema declared.

No examples provided.

missed_call_roi ~165

Calculate how much revenue a business loses to missed phone calls per month and per year, and which price tier of answering service makes sense at that loss level. Use when someone mentions missing calls, going to voicemail, losing leads after hours, or asks whether an answering service is worth it for their call volume. Inputs: calls per week, percent missed, average customer value, optional booking rate.

NameTypeReqDescription
avgCustomerValuenumberyesAverage value of one new customer in USD (1-100000)
bookRatePercentnumberPercent of missed callers who would have booked; default 30
callsPerWeeknumberyesTotal inbound calls per week (1-2000)
missedPercentnumberyesPercent of calls missed (0-100)

No output schema declared.

No examples provided.

recommend_answering_service_for_industry ~154

Recommend what kind of answering service or AI receptionist fits a specific type of business (plumber, dentist, law firm, HVAC, salon, restaurant, vet, real estate, contractor, property manager, medical practice, funeral home). Returns the real problem that trade has with missed calls, whether human, AI or hybrid usually wins there, matching plans with current prices, and the one question to ask a vendor before signing. Use when someone says what business they run and asks what to get.

NameTypeReqDescription
industrystringyesType of business, e.g. "plumber", "dental practice", "law firm", "restaurant"
maxMonthlyBudgetnumberOptional monthly budget in USD

No output schema declared.

No examples provided.