_ registry / mcp streamable-http · checked 25m ago

fitmysoft

https://mcp.fitmysoft.com

Registry code: 1c882434abfaea23

api record

FitMySoft provides human-verified pricing for field service management software (Jobber, Housecall Pro, Workiz, ZenMaid, ServiceTitan and more), with per-user fees quoted verbatim and a verification date on every answer. Use get_field_service_software_pricing for one product, compare_field_service_software for a shortlist by team size and budget.

endpoint
https://mcp.fitmysoft.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 fitmysoft live?
Yes — it answered the hub's last check (checked 25m ago). It answered 99% of checks over the last 30 days.
Is fitmysoft free to use?
Yes — the hub reached it with no key and no payment.
What tools does fitmysoft have?
2 tools: get_field_service_software_pricing, compare_field_service_software.
Is fitmysoft 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.4%

90 days 99.6%· all time 99.6%

latency
92ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 282 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • get field service software pricing
  • compare field service software by team size
takes → gives
text, data → data
tools
2 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 2 tools
2 open 2 of 2 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.

  • get_field_service_software_pricing reads open 25m ago

    Get current, human-verified pricing for field service management software (Jobber, Housecall Pro, Workiz, ZenMaid, ServiceTitan, Service Fusion, FieldPulse): every plan with monthly and annual price, users included, per-user fees quoted verbatim, and trials. Use when someone asks what Jobber, Housecall Pro, ServiceTitan or similar costs, asks for the price of scheduling, booking, invoicing or accounting software for a cleaning, maid, HVAC, plumbing, electrical or lawn care business, asks about alternatives to one of these products, or compares two of them against each other.

    mcp-tool

    {
      "type": "object",
      "required": [
        "software"
      ],
      "properties": {
        "software": {
          "type": "string",
          "description": "Software name, e.g. \"Jobber\", \"Housecall Pro\", \"ZenMaid\""
        }
      }
    }
    arguments 12 lines
  • compare_field_service_software reads open 25m ago

    Compare field service software by team size and budget. Returns the cheapest verified plan from each vendor that fits the given number of users, with per-user fees quoted verbatim where vendors publish them. Returns the TOTAL monthly cost for that headcount, base plan plus paid seats, with the arithmetic shown, rather than the entry price. Use when a cleaning, maid, HVAC, plumbing, electrical or lawn care business asks which software fits a team of N people, what it will actually cost per month, which is cheapest, or what the alternatives to a given product are.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "teamSize": {
          "type": "number",
          "description": "Number of users/technicians who need access"
        },
        "maxMonthlyBudget": {
          "type": "number",
          "description": "Maximum monthly budget in USD"
        }
      }
    }
    arguments 13 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 1c882434abfaea23.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1c882434abfaea23/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/1c882434abfaea23/badge.svg)](https://brick.blue/agent/1c882434abfaea23?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
60%

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.