_ registry / mcp streamable-http · checked 1h ago

fitmycall

https://mcp.fitmycall.com

Registry code: d39b2cb49e1c4cea

api record

FitMyCall provides current, human-verified pricing for 21 answering services and AI receptionists, plus a missed-call revenue calculator. Every price carries the date it was verified on the vendor’s site. Use get_answering_service_pricing for one service, compare_answering_services for shortlists by budget, missed_call_roi to quantify lost revenue.

endpoint
https://mcp.fitmycall.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fitmycall live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is fitmycall free to use?
Yes — the hub reached it with no key and no payment.
What tools does fitmycall have?
4 tools: missed_call_roi, compare_answering_services, get_answering_service_pricing, recommend_answering_service_for_industry.
Is fitmycall safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.8%· all time 99.8%

latency
274ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 616 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • compare answering service prices
  • get pricing for an answering service
  • calculate revenue lost to missed calls
  • recommend an answering service for an industry
takes → gives
data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 open 4 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • missed_call_roi reads open 4h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "callsPerWeek",
        "missedPercent",
        "avgCustomerValue"
      ],
      "properties": {
        "callsPerWeek": {
          "type": "number",
          "description": "Total inbound calls per week (1-2000)"
        },
        "missedPercent": {
          "type": "number",
          "description": "Percent of calls missed (0-100)"
        },
        "bookRatePercent": {
          "type": "number",
          "description": "Percent of missed callers who would have booked; default 30"
        },
        "avgCustomerValue": {
          "type": "number",
          "description": "Average value of one new customer in USD (1-100000)"
        }
      }
    }
    arguments 26 lines
  • compare_answering_services reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "type": {
          "enum": [
            "any",
            "ai",
            "human",
            "hybrid"
          ],
          "type": "string",
          "description": "Service type filter; default any"
        },
        "maxMonthlyBudget": {
          "type": "number",
          "description": "Maximum monthly budget in USD"
        },
        "minIncludedMinutes": {
          "type": "number",
          "description": "Minimum included minutes per month"
        }
      }
    }
    arguments 23 lines
  • get_answering_service_pricing reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "service"
      ],
      "properties": {
        "service": {
          "type": "string",
          "description": "Service name, e.g. \"Smith.ai\", \"Ruby\", \"Dialzara\", \"Abby Connect\""
        }
      }
    }
    arguments 12 lines
  • recommend_answering_service_for_industry reads open 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "industry"
      ],
      "properties": {
        "industry": {
          "type": "string",
          "description": "Type of business, e.g. \"plumber\", \"dental practice\", \"law firm\", \"restaurant\""
        },
        "maxMonthlyBudget": {
          "type": "number",
          "description": "Optional monthly budget in USD"
        }
      }
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d39b2cb49e1c4cea.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d39b2cb49e1c4cea/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d39b2cb49e1c4cea/badge.svg)](https://brick.blue/agent/d39b2cb49e1c4cea?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.