Wedding Cost Checker MCP server

• Registry namecom.weddingcostchecker/siteverified in the MCP registry

The registry name sits under weddingcostchecker.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-20
• Tools10
• Server calls itselfWedding Cost Checker (weddingcostchecker.com)
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 728 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer1433 ms
• Space in an agent's context≈ 1,239 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsB · 75 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 5 of 10
• Not saying whether it only reads or can destroy: 10 of 10

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• dataset_columns

  The columns, which of them are numeric, the row count and the provenance banner of the Wedding Cost Checker dataset. Call this first to learn the schema.

• dataset_search

  Rows of the Wedding Cost Checker dataset whose cells contain the query (case-insensitive), up to 50.

• dataset_row

  The rows of the Wedding Cost Checker dataset where a column equals a value exactly (case-insensitive).

• dataset_compare

  The rows of the Wedding Cost Checker dataset whose column is any of the given values, in the order given — for "X vs Y" questions.

• dataset_stats

  count, min, max, mean, median and sum of a numeric column of the Wedding Cost Checker dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).

• dataset_top

  The highest (or lowest) rows of the Wedding Cost Checker dataset by a numeric column — "which is the most/least X".

• dataset_provenance

  The source, the date it was computed, the licence and the citation for the Wedding Cost Checker dataset. Read this to attribute a figure correctly.

• enquiry_describe

  Read first. States plainly what submit_enquiry does on Wedding Cost Checker: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives…

• enquiry_fields

  Every field of the Wedding Cost Checker enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

• submit_enquiry

  Submits an enquiry to Wedding Cost Checker — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a…