AIBuilder Marketplace: software pricing dossiers

{
  "mcpServers": {
    "com.aibuildermarketplace/software-pricing": {
      "url": "https://api.aibuildermarketplace.com/mcp"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

15 shown · authentication unknown

• build_purchase_dossier

  Build a purchase file for 1 to 6 candidate products against the same requirements (same fields as check_choice). Returns per candidate the check with evidence, the cheapest fitting plan's cost where computable, our hands-on test results, unknowns and the vendor handoff with affiliate disclosure; a fixed order that never uses commission; a summary_markdown to show the user as is (it starts with the share link and says whether any candidate has a confirmed fit); a share_url; and depends_on facts so the file can be re-checked later. A feature counts as documented only from the vendor's own pages, never as tested by us. When requirements.modules names a setup ([{id, role}], e.g. a help desk plus a phone line), read setup_check for the verdict on the whole setup (its known costs per currency, open items and the budget for the setup as a whole); each candidate's own budget line compares that product alone.

  Schema valid · SHA-256 2c3655843a61…

  View input schema

  {
    "type": "object",
    "properties": {
      "product_ids": {
        "items": {
          "type": "string"
        },
        "title": "Product Ids",
        "type": "array"
      },
      "requirements": {
        "anyOf": [
          {
            "additionalProperties": true,
            "type": "object"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "title": "Requirements"
      },
      "question": {
        "default": "",
        "title": "Question",
        "type": "string"
      }
    },
    "required": [
      "product_ids"
    ],
    "title": "build_purchase_dossierArguments"
  }

• check_choice

  Check a software choice against requirements before buying. requirements (all optional): units, billing ('monthly'|'annual'), plan_id, budget_month {amount, currency}, needs_monthly_billing, max_commitment_months, needs_free_plan, avoid_cost_traps [quote_only, per_seat, usage_metered, renewal_jump, addons_extra, annual_lock], features [text], addons [ids], usage {id: quantity}, service (price only that part of a vendor's ladder, e.g. eor, contractor, contractor_of_record, global_payroll). Each requirement gets fits / does_not_fit / unknown / conflicting / recheck_needed / not_flagged / mentioned, with evidence. Outcome is no_blocking_requirement_found, blocking_requirement_found or insufficient_evidence; unknown never counts as a fit.