Skip to content

BidBud Estimating MCP server

com.bidbudai/estimatingbidbudai.comstreamable-httpv1.2.0Scanned

Home-improvement cost estimates, tier comparisons, quote checks and permit guidance for US homes.

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BidBud Estimating MCP server can do

The BidBud Estimating MCP server is published by bidbudai.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: estimate_project), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 1Claude Code: ask
  • estimate_projectEstimate the cost of one or more home-improvement services for a US home.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description is 2,408 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ons, and questions to ask the homeowner that would tighten the estimate."

      What this check looks for
    Description, as the server wrote it
    Estimate the cost of one or more home-improvement services for a US home. When to use: the homeowner wants to know what a job should cost, for example before asking contractors for bids. Limits: US residential homes only, one property per call. A planning estimate from national cost data with metro-area or state labor rates, not a bid; actual prices depend on the site, the scope and the local market. Args: home_sqft: Finished square footage of the home (200-20000). num_rooms: Number of rooms (1-50). Used to derive wall area. services: Services to price, e.g. ["painting", "roofing"]. quality_tier: "economy", "medium" (mid-range) or "high" (premium). zip_code: 5-digit US ZIP code of the property. Applies metro-area (or state) labor-rate adjustments; strongly recommended. state: Two-letter state code, used when the ZIP is unknown. stories: Above-grade stories (1, 1.5, 2 or 3; default 1). Drives roof area, siding area and gutter length for exterior services. flooring_type: For flooring only: carpet, tile, vinyl, hardwood or mix. num_windows: For windows only: actual window count, if known. ceiling_height_ft: Override the default 8.5 ft ceiling height. roof_sqft: Override the roof area derived from home size. include_permits: Add estimated permit fees as separate lines. include_contingency: Add a 10% contingency line for conditions found on site. include_line_items: Include itemized quantities and unit costs. roof_pitch: Roof slope if known: low, standard, steep or very_steep. Steep roofs add area and a steep-slope labor surcharge. roof_shape: gable, hip or complex; sets the gutter/eave length. home_type: detached, townhouse_end, townhouse_middle or condo; shared walls reduce siding, trim and gutters (condo exteriors are flagged as usually the HOA's responsibility). year_built: Year the home was built. Before 1978 adds EPA lead-safe (RRP) work practices to painting, windows and drywall. Each property detail you pass narrows the likely range for the services it affects. Returns totals per service, a confidence range, the main assumptions, and questions to ask the homeowner that would tighten the estimate.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 4Show 4 read-only tools
  • check_quoteCompare a contractor's quoted price with BidBud's likely range for the same scope.No findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.
    Description, as the server wrote it
    Compare a contractor's quoted price with BidBud's likely range for the same scope. Prices the scope at economy, mid-range and premium quality and judges the quote against the likely range (confidence band) of the quality level being compared. Verdicts: "low" (below the range: ask what is excluded), "fair", "high" (above the range but within premium pricing) and "very_high" (above even the premium range). When to use: a homeowner has a contractor's price and asks whether it is reasonable. Limits: judges the price only, not the contractor, workmanship or exact materials; US residential homes only; a planning comparison, not an appraisal or a bid. Args: quoted_price: The contractor's total price in USD for the listed services. home_sqft: Finished square footage of the home. num_rooms: Number of rooms. services: The services the quote covers. quality_tier: Quality level the quote is for: "economy", "medium" (mid-range, default) or "high" (premium). zip_code: US ZIP code of the property, for regional labor pricing. state: Two-letter state code, used when the ZIP is unknown. stories: Above-grade stories (1, 1.5, 2 or 3; default 1). flooring_type: For flooring quotes: carpet, tile, vinyl, hardwood or mix. num_windows: For window quotes: number of windows being replaced. roof_pitch: Roof slope if known: low, standard, steep or very_steep. roof_shape: gable, hip or complex. home_type: detached, townhouse_end, townhouse_middle or condo. year_built: Year the home was built (before 1978 adds lead-safe work practices).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • compare_tiersPrice the same project at economy, mid-range and premium quality side by side.No findings

    Why it is in this group

    • The name "compare_tiers" says "compare": a word for reading.
    Description, as the server wrote it
    Price the same project at economy, mid-range and premium quality side by side. When to use: the homeowner asks "what's the difference between a basic and a high-end job?" or wants to choose a budget level. Limits: US residential homes only; tiers reflect typical materials and labor at each level, not specific products or brands; planning estimates, not bids. Args: home_sqft: Finished square footage of the home (200-20000). num_rooms: Number of rooms (1-50). services: Services to price, e.g. ["flooring", "painting"]. zip_code: 5-digit US ZIP code of the property, for regional labor pricing. state: Two-letter state code, used when the ZIP is unknown. stories: Above-grade stories (1, 1.5, 2 or 3; default 1). flooring_type: For flooring only: carpet, tile, vinyl, hardwood or mix. num_windows: For windows only: actual window count, if known. include_permits: Add estimated permit fees. include_contingency: Add a 10% contingency allowance. Returns the total for each tier, a per-service breakdown for each tier, and each service's totals across the three tiers.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_permit_guidanceSay whether each service typically needs a building permit, with typical fees, and (when a state is given) the state's building code, code authority and contractor licensing resour…No findings

    Why it is in this group

    • The name "get_permit_guidance" says "get": a word for reading.
    Description, as the server wrote it
    Say whether each service typically needs a building permit, with typical fees, and (when a state is given) the state's building code, code authority and contractor licensing resources. When to use: the homeowner asks whether a job needs a permit, or how to check a contractor's license in their state. Limits: typical requirements only; local rules vary, so confirm with the local building department. General guidance, not legal advice. Args: services: Services being planned, e.g. ["roofing", "electrical"]. state: Two-letter US state code, e.g. "PA".

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_servicesList the home-improvement services BidBud can estimate, the quality tiers, accepted input ranges, and which services get metro-area or state labor pricing.No findings

    Why it is in this group

    • The name "list_services" says "list": a word for reading.
    Description, as the server wrote it
    List the home-improvement services BidBud can estimate, the quality tiers, accepted input ranges, and which services get metro-area or state labor pricing. When to use: first, when unsure whether a job is supported or which details to ask the homeowner for. Limits: US residential homes only; only the services listed here.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:34 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.bidbudai.com/mcp: tools/list returned 5 tools to an anonymous client, including estimate_project (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,408 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ons, and questions to ask the homeowner that would tighten the estimate."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 changed.~5 changedView diff

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http estimating https://mcp.bidbudai.com/mcp
claude mcp add --transport http estimating https://mcp.bidbudai.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__estimating__list_services",
      "mcp__estimating__check_quote",
      "mcp__estimating__get_permit_guidance",
      "mcp__estimating__compare_tiers"
    ],
    "ask": [
      "mcp__estimating__estimate_project"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as estimating. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.bidbudai/estimating/verify?hash=d472426c6b35adddc6112b51ed03c696e737554158c4d8e564787eaea8a9a7e9" | jq -e '.changed == false'

Pinned hash d472426c6b35, from Nov 9, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.bidbudai/estimating/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.bidbudai/estimating
[![Anlyon Radar](https://radar.anlyon.com/badge/com.bidbudai/estimating.svg)](https://radar.anlyon.com/servers/com.bidbudai/estimating)

Source: MCP Registry. Synced Oct 26, 2026, 02:17 UTC.

BidBud Estimating MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BidBud Estimating MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BidBud Estimating MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BidBud Estimating MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BidBud Estimating MCP server have?

5 tools: 1 write, 4 read. estimate_project, list_services, check_quote, get_permit_guidance and compare_tiers.

Does the BidBud Estimating MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BidBud Estimating MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BidBud Estimating MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 26, 2026. Every change is on this page and in its Atom feed.