Bank Code Lookup: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
Scored across 10 tools
The seven dataset_* tools each map to a distinct retrieval mode (schema, exact row, substring search, value comparison, aggregates, ranking, provenance), and the three enquiry tools cover describe/schema/submit. There is mild boundary overlap between dataset_row (exact match), dataset_search (contains), and dataset_compare (value list), but the descriptions make the distinctions usable.
Names are readable and mostly consistent: dataset_* plus a noun covers seven tools, and enquiry_* covers describe/fields. The one deviation is submit_enquiry, which uses a verb_noun form while its siblings use noun forms, but this is a minor and semantically justified exception.
Ten tools is well within the ideal 3-15 range for a single-dataset lookup server plus a small enquiry workflow. Every tool earns its place; nothing appears redundant or padded.
The read side of the dataset is thoroughly covered (schema, provenance, exact row, search, compare, stats, top), and the enquiry lifecycle has describe, field schema, and a two-step validated submission. Minor gaps remain: no pagination/cursor guidance for large search results and no explicit way to list datasets if more than one exists, but core workflows have no dead ends.
The columns, which of them are numeric, the row count and the provenance banner of the Bank Code Lookup dataset. Call this first to learn the schema.
Inputs: no named parameters.
The rows of the Bank Code Lookup dataset whose column is any of the given values, in the order given — for "X vs Y" questions.
Inputs: column (required), values (required).
The source, the date it was computed, the licence and the citation for the Bank Code Lookup dataset. Read this to attribute a figure correctly.
Inputs: no named parameters.
The rows of the Bank Code Lookup dataset where a column equals a value exactly (case-insensitive).
Inputs: value (required), column (required).
Rows of the Bank Code Lookup dataset whose cells contain the query (case-insensitive), up to 50.
Inputs: query (required), limit.
count, min, max, mean, median and sum of a numeric column of the Bank Code Lookup dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).
Inputs: column (required).
The highest (or lowest) rows of the Bank Code Lookup dataset by a numeric column — "which is the most/least X".
Inputs: column (required), limit, ascending.
Read first. States plainly what submit_enquiry does on Bank Code Lookup: 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 the details, the consent wording, and how the person confirms.
Inputs: no named parameters.
Every field of the Bank Code Lookup 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.
Inputs: no named parameters.
Submits an enquiry to Bank Code Lookup — 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 confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "By submitting you agree Bank Code Lookup emails you what it can verify about the code you sent, and shares nothing with a third party."
Inputs: answers (required), consent (required), confirmation.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Bank Convert: the site's own MCP server — compare, enquiry (enquiry = a human handoff, not a...
Procedure Cost Checker: the site's own MCP server — dataset, enquiry (enquiry = a human handoff,...
EntitySearch HQ: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
Rechner HQ: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not a...
Add one secure layer between your agents and this server.