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

kitfinch

https://kitfinch.com

Registry code: abbc2c7ebe23d7de

api record

Business software by trade for US small service businesses, with prices verified at the source.

from a public catalogue that lists it, not from the operator

endpoint
https://kitfinch.com/mcp
protocol
http-sse ·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 kitfinch live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is kitfinch free to use?
Yes — the hub reached it with no key and no payment.
What tools does kitfinch have?
3 tools: compare, recommend_kit, get_pricing.
Is kitfinch 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
100%

90 days 100%· all time 100%

latency
206ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • compare unknown 1h ago

    Use this when the user wants to compare two business software tools side by side. Returns both tools with verified entry prices, the tasks they both cover and a link to Kitfinch's comparison page.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "a",
        "b"
      ],
      "properties": {
        "a": {
          "type": "string",
          "minLength": 1,
          "description": "First tool name or slug"
        },
        "b": {
          "type": "string",
          "minLength": 1,
          "description": "Second tool name or slug"
        }
      }
    }
    arguments 20 lines
  • recommend_kit unknown 1h ago

    Use this when a small US trade or service business (plumber, electrician, HVAC, landscaper…) asks which software to use. Returns Kitfinch's recommended tool for each task (scheduling, invoicing, CRM…), verified entry prices with their source, and an estimated monthly total for the team size.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "job"
      ],
      "properties": {
        "job": {
          "type": "string",
          "minLength": 1,
          "description": "The trade, for example \"plumber\" or \"HVAC companies\""
        },
        "teamSize": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "Number of users; defaults to 1"
        }
      }
    }
    arguments 20 lines
  • get_pricing unknown 1h ago

    Use this when the user asks how much a specific business software tool costs. Returns every plan Kitfinch tracks; an amount is included only when it has a source page and a recent verification date, otherwise the plan says to check the vendor site.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "tool"
      ],
      "properties": {
        "tool": {
          "type": "string",
          "minLength": 1,
          "description": "Tool name or slug, for example \"Jobber\""
        }
      }
    }
    arguments 14 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 abbc2c7ebe23d7de.

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

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.