The free scheme for holding party wall security for expenses under section 12 of the Party Wall etc. Act 1996. All security is held liquid and unencumbered at the Bank of England, and released only on the award.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.securityforexpensesscheme.org
26tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.securityforexpensesscheme.org/mcp
Skill page: https://www.mcpbundles.com/skills/securityforexpensesscheme-mcp-c9747784c4
Explore capabilities (26)
read 8
write 17
Showing 25 of 26
Showing 25 of 26 tools from the public preview. Connect the server to inspect the full live tool list.
Check4
Get4
Request4
Draft3
List2
Submit2
Other capabilities6
Request a quote
write
request_quote
Submits a structured enquiry to UK Security for Expenses Scheme (UKSfES) asking the team to prepare a quote. The purpose field takes at least 100 characters in the enquirer's own words. No pricing is returned: the team follows up by email with the formal quote. Returns an opaque enquiry reference. A repeat submission with the same contact details creates nothing new: the existing enquiry stands unchanged and its reference is re-sent to the email address on it.
Request a quote — Submits a structured enquiry to UK Security for Expenses Scheme (UKSfES) asking the team to prepare a quote. The purpose field takes at least 100 characters in the enquirer's own words. No pricing is returned: the team follows up by email with the formal quote. Returns an opaque enquiry reference. A repeat submission with the same contact details creates nothing new: the existing enquiry stands unchanged and its reference is re-sent to the email address on it.
Request a callback — Asks the team to phone the enquirer back about an existing enquiry, identified by its enquiry reference. Takes an optional preferred time window as ISO 8601 date-times; without one, the team calls at the next opportunity.
Send an enquiry status code — Emails a one-time code to the address on an enquiry, identified by its enquiry reference. The code is needed to check the enquiry's status. It goes only to the address the enquiry was submitted with, expires in 15 minutes and works once.
Check an enquiry's status — Reports the current status of an enquiry, given its enquiry reference and the one-time code emailed to the enquiry's own address. Each code expires after 15 minutes and works once.
About this connection — Describes the authenticated connection in use: who is signed in, what access was granted, and how to manage or disconnect it.
Ask the account holder to confirm this connection — Emails the account holder a short-lived link asking them to confirm this connection is really theirs. Confirmation is optional and adds a trust marker that staff and the account holder can see. The approval happens in their browser, never in the conversation. Returns a confirmation id.
Check a confirmation's outcome — Reports the outcome of a confirmation this connection asked for, given its id (the confirmation_id or submission_id a tool returned). Approval happens in the person's browser; this tool only reads the result.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
What is the UK Security for Expenses Scheme MCP server?
The free scheme for holding party wall security for expenses under section 12 of the Party Wall etc. Act 1996. All security is held liquid and unencumbered at the Bank of England, and released only on the award.
How do I connect UK Security for Expenses Scheme to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate this server?
Request removal if you do not want UK Security for Expenses Scheme listed here, or claim the listing if you want to manage it on MCPBundles.
Operate UK Security for Expenses Scheme?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
Register a building — Registers the building that a UK Security for Expenses Scheme (UKSfES) escrow account will be opened for, and creates the client's record. Takes the building's street address, the owner's full legal name as it appears on the Land Registry title, and the title number if known. The account also needs the title register and/or party wall award.
Upload a building document — Sends a document for a registered building. Files up to 4 MB go in file_base64. For a larger file, omit file_base64 and give byte_size: the result then carries an upload_url for the raw bytes and an upload_id that completes the attachment. Every file is safety-checked (type, size, malware scan) before it is attached; PDFs and clear photos (JPEG, PNG or WebP) are accepted, 25 MB at most. title_register: The official copy of the Land Registry title register for the building, as a PDF from GOV.UK.
Attach an uploaded document — Completes a large-file upload: given the upload_id of an upload whose bytes have been PUT to its upload_url, runs the safety checks and attaches the document. Each upload_id works once.
Submit the opening for confirmation — Declares (or corrects) the details of the account being opened and submits it for the account holder's approval. Nothing is completed in the conversation: the account holder receives a short-lived approval link by email, reviews the declaration in their browser and approves it there. On approval the opening is queued for the team. Returns a confirmation id.
Check opening progress — Reports what is left before the account holder's account can open, as one list: each opening's steps and, where this connection may see them, the account holder's own checks (identity, funds, agreements, questions). Each item says whether it is done, in progress or to do, who acts next (the account holder, or the team), any date it is due by and a link to finish it. Plus any updates since the last check. Verification and account opening are completed by the team; this never reports check outcome
What is still outstanding — Lists what is left before the account holder's account can open, as one list: their compliance checks and, where this connection may see them, each opening's steps. Each item says whether it is done, in progress or to do, who acts next (the account holder, or the team), any date it is due by and a link to finish it. It reports what is outstanding, never the content already provided, and never screening results, risk assessments or internal review detail. Where an item was queried or did not pass
Draft KYC details — Saves or amends a draft of the account holder's KYC details (the account holder's personal details, or the company/charity/trust's details). Nothing is submitted: the draft becomes a declaration only after the account holder reviews every answer through an emailed link and approves it themselves. Each answer records its provenance: stated by the account holder in conversation, or taken from a document they provided. Calling again merges new answers over the existing draft. Returns the full store
Draft the source of funds declaration — Saves or amends a draft of the account holder's source of funds declaration (where the money being paid in comes from). Nothing is submitted: the draft becomes a declaration only after the account holder reviews every answer through an emailed link and approves it themselves. Each answer records its provenance: stated by the account holder in conversation, or taken from a document they provided. Calling again merges new answers over the existing draft. Returns the full stored draft.
Draft the source of wealth declaration — Saves or amends a draft of the account holder's source of wealth declaration (how the account holder's overall wealth was built up). Nothing is submitted: the draft becomes a declaration only after the account holder reviews every answer through an emailed link and approves it themselves. Each answer records its provenance: stated by the account holder in conversation, or taken from a document they provided. Calling again merges new answers over the existing draft. Returns the full stored draft.
Send a draft for the account holder's confirmation — Sends the current draft (kyc_details, sof or sow) to the account holder for confirmation. They receive an email with a secure link; the page shows every answer exactly as drafted, with its provenance, and the declaration wording they are signing. Only their approval there creates the declaration; nothing is submitted in the conversation. The link lasts 15 minutes. If they decline, later amendments start a fresh draft version.
Check a submission's outcome — Reports the outcome of a declaration sent for confirmation. Approval happens in the account holder's browser; this tool only reads the result.
Add a member for their own KYC — Records a member of the account holder's organisation (director, shareholder/UBO, trustee, beneficiary or settlor) who needs their own identity check. With invite=true and an email address, the member is invited DIRECTLY: the identity journey goes to their own email and they complete their own checks themselves, in their browser or via their own connected assistant. Their journey link is never available in this conversation, and nothing about their progress or details is readable here: each pers
Start the account holder's identity check — Starts the account holder's own photo-ID identity check and returns a secure link for them to complete in their browser. It is a biometric journey that only the account holder can complete. Its progress shows on the compliance checklist. This channel never sees documents, results or reasons.
List the account holder's accounts — Lists the accounts the account holder can see in their client portal, with each account's name, status, current balance and when that balance was last updated. Read-only. Returns each account's id. Account identifiers are shown masked to the last four characters only; this channel never has full bank details and cannot provide them.
Get an account's balance — Reports one account's current balance, status and when the balance was last updated, plus the exact payer name(s) to use when paying into it where those are on record. Read-only. Takes an account id. The account identifier is masked to its last four characters; full bank details are never available on this channel.
List an account's transactions — Lists the transactions the account holder can see on one account in their portal, newest first, 50 per page, each described in plain English (who the money came from or went to, and how) with its date, amount, reference and the portal's own status (posted, or still in progress). Can be narrowed, exactly as the portal's Transactions tab narrows: by dates, money in or out, and a name or reference to match. A narrowed list also gives money in and out over everything it selects, posted apart from st
Where a release from an account stands — Reports where each release or payment out of one account stands: what it depends on, what is still outstanding, who acts next (the account holder, the other side, or the team) and any date it is due. Covers releases under a party wall award, retention release notices and payment requests, in the words the account holder's portal uses. Read-only. Takes an account id. The team's own checks are one step; their detail, and the reasons for any hold, are not available on this channel.
Send a message to the team — Passes the person's question to the UK Security for Expenses Scheme (UKSfES) team as a support request: their name, email address, a topic and their message, with the tools already tried, and optionally a reference, a phone number and a good time to call. The person confirms it from an email before it reaches the team, unless the connection is signed in with that address. Takes no bank details. Topics: my_account (My account), payments (Payments), scheme_rules (How the scheme works), documents (
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does UK Security for Expenses Scheme provide?
MCPBundles probed 26 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does UK Security for Expenses Scheme require?
UK Security for Expenses Scheme may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.