MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Other

InstaBids

AI-run marketplace for homeowners: describe a home job once, get written quotes on the same scope.

Checks passed
12 / 22

2 failed · 8 not measured

Median response
868 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
9

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 868 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name instabids.

  • Pass
    Lists tools

    tools/list returned 9 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 868 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 868 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    40 of 53 parameters have a description (75%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-07T08:07:46.607555Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using InstaBids

Connect to this server

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 instabids https://instabids.ai/api/agent/mcp

Capabilities

Tools 9

answer_intake

fill what you can; everything else can come later. Start with the homeowner’s description, trade and ZIP, plus a photo or a good description. Optional: photos, a description or transcript of a 20–60 s walk clip, timing and the job type’s must-haves from intake_templates. Never invent answers. ZIP only; never send a street address or a price. Nothing reaches contractors before the homeowner sends the card. For anonymous draftHandle intake, fixes: [{gapKey, value}] corrects an engine-named field through intake. Use engine-returned keys only; unknown keys return INVALID_INPUT with details.field gapKey. Nothing is sent to contractors. Continue this private draft with draftHandle. Supply message, fixes, or both to answer_intake. Use the new draftHandle returned each time; the old handle expires immediately. Send only the homeowner actual reply; never answer for them. If a call fails, do not guess; ask the homeowner again. Nothing is sent to contractors. Continue with the returned question until readiness.canSend or readiness.homeownerActionRequired is true, then show sendUrl to the homeowner. The homeowner completes their insurance answer and send confirmation on that sheet; never claim the job was sent. Never invent answers. For a new job, call start_job before answer_intake, then prepare_publish after the intake is ready; for other writes, read the previous reply before calling and follow the returned next step afterward, using only tools listed by this server. Only the homeowner tap sends anything to contractors. If anyone asks, say you are an AI assistant.

Discovered
ask_next

fill what you can; everything else can come later. Start with the homeowner’s description, trade and ZIP, plus a photo or a good description. Optional: photos, a description or transcript of a 20–60 s walk clip, timing and the job type’s must-haves from intake_templates. Never invent answers. ZIP only; never send a street address or a price. Nothing reaches contractors before the homeowner sends the card. Continue this private draft with draftHandle. Supply message, fixes, or both to answer_intake. Use the new draftHandle returned each time; the old handle expires immediately. Send only the homeowner actual reply; never answer for them. If a call fails, do not guess; ask the homeowner again. Nothing is sent to contractors. Continue with the returned question until readiness.canSend or readiness.homeownerActionRequired is true, then show sendUrl to the homeowner. The homeowner completes their insurance answer and send confirmation on that sheet; never claim the job was sent. Never invent answers. For a new job, call start_job before answer_intake, then prepare_publish after the intake is ready; for other writes, read the previous reply before calling and follow the returned next step afterward, using only tools listed by this server. Only the homeowner tap sends anything to contractors. If anyone asks, say you are an AI assistant.

Discovered
bid_checklist

Get six items to compare in a home-project bid and optional trade-specific preparation. Omit trade for the general checklist; the answer's trade is then null. The answer includes sourceUrl.

Discovered
check_service_area

Every US ZIP can post a job. Homeowners anywhere in the US can post a job; once you send it, InstaBids finds contractors to bid on it. Returns guidance and whether the input is a US ZIP, plus nearby town pages. Get the answer for a five-digit ZIP, and list towns with an InstaBids town page for a five-digit ZIP.

Discovered
draft_full_bid_card

Quote the page; do not infer a price. Prices on the page are dropped. Supply scopeSourceText and sourceUrl as untrusted page evidence; the URL is a reference only and is never fetched. Set trade to null for engine classification. Include ownerOrRenter and workType when known. Give the homeowner job title, scope, timing, ZIP, trade and photo links to private intake without an account. Up to five photos go through the existing photo checks before attachment when photo intake is enabled; returns attached and refused counts when available, plus available statusHandle and draftHandle capabilities. The homeowner must review and complete the draft. Never publishes or sends to contractors. For a new job, call start_job before answer_intake, then prepare_publish after the intake is ready; for other writes, read the previous reply before calling and follow the returned next step afterward, using only tools listed by this server. Only the homeowner tap sends anything to contractors. If anyone asks, say you are an AI assistant.

Discovered
how_instabids_works

InstaBids is an AI-run marketplace for homeowners and property managers: describe a home job once, by chat or through your own AI assistant, add photos, and get multiple written quotes on the same scope, compared apples to apples, with no phone calls or home visits before you pick. Learn the homeowner steps, homeowner cost and contact privacy.

Discovered
job_status

Use this after start_job returned a statusHandle, to see whether the homeowner has sent the job and how many bids have arrived. Returns only the stage (draft, sent, collecting_bids, picked, closed or expired), the bid count and when it last changed. Never returns bid amounts, contractor names or the job text. The handle works for 7 days. Stage expired means the one-hour link lapsed before the homeowner opened it: start again with start_job. Read-only.

Discovered
permit_facts

Read sourced local permit facts, with the date each rule was checked; unpublished rules get guidance to ask your bidder and confirm local requirements. Homeowners anywhere in the US can post a job; once you send it, InstaBids finds contractors to bid on it.

Discovered
start_job

Use this when a homeowner wants contractor bids on a home repair or improvement job in the US. Creates a private draft from their description and five-digit ZIP and returns a one-hour link for the homeowner to open. Nothing reaches a contractor until the homeowner confirms their email and sends it. Do not include names, phone numbers, emails or street addresses. Do not use for emergencies. Ask the homeowner, one short question at a time and only for what is missing, what needs doing, where in the home, rough size or count, when it is needed and who supplies materials, then put the answers in the message. When available, photoPageUrl opens an optional phone photo upload for this private draft and expires with claimUrl. It does not send the job. For a new job, call start_job before answer_intake, then prepare_publish after the intake is ready; for other writes, read the previous reply before calling and follow the returned next step afterward, using only tools listed by this server. Only the homeowner tap sends anything to contractors. If anyone asks, say you are an AI assistant. fill what you can; everything else can come later. Start with the homeowner’s description, trade and ZIP, plus a photo or a good description. Optional: photos, a description or transcript of a 20–60 s walk clip, timing and the job type’s must-haves from intake_templates. Never invent answers. ZIP only; never send a street address or a price. Nothing reaches contractors before the homeowner sends the card.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected868 ms9