PropXchain

io.github.Madhatt4Published by GitHub account Madhatt4v2.2.1Updated Oct 25, 2026

UK property transactions: status, checklists, documents, HM Land Registry intel.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & StorageBusiness & Commerce

Overview

AI-generated overview

A hosted MCP server for UK property transactions that lets an assistant read status, checklists, documents and Land Registry data, and draft messages to other,

What you can do
Join a transaction with an invite code and list the transactions and bots connected to it, then read status, details and the on-chain audit trail, or create and join transactions where permitted. Verify, list and upload documents, and read or update the transaction checklist. Pull HM Land Registry and property intelligence for an address. Explain each step of the process and draft messages to the other parties.
When to use it
Useful when you are buying or selling a home in the UK through PropXchain and want an assistant to track progress, summarise documents and checklists, look up property data, and draft updates for the seller, buyer, conveyancer or agent.
Requirements
Remote endpoint with OAuth 2.1 sign-in approved by email and a 6-digit code, plus a TX-XXXX-XXXX invite code from the transaction's share panel. A local stdio option exists as an npm package requiring Node.js, which creates an Ed25519 identity key on disk or reads BOT_PRIVATE_KEY.
Before you install
Access is scoped to transactions granted by invite code, but the assistant can upload documents, update checklists and send messages to other parties, so review before approving. The local option stores a private identity seed on disk; keep it protected and revoke access from the bot panel when done. Money and legal steps are not performed by the server.

Installation

In SourceWeft

  1. Open PropXchain in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Madhatt4%2Fpropxchain/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "propxchain": {
      "type": "http",
      "url": "https://mcp.propxchain.com/mcp"
    }
  }
}

README

@propxchain/mcp-server

[npm] [MCP]

MCP server for PropXchain, the UK platform for selling or buying a home: one shared, live record of the transaction for seller, buyer, conveyancer and estate agent. (Not Propchain/PROPC, the unrelated crypto token.)

Your AI assistant can join your transaction with its invite code, read status, checklists, documents and the audit trail, pull HM Land Registry and property data, explain each step, and draft messages to the other parties. Money and legal steps still wait for you.

Connect (hosted, no install)

PropXchain runs this server for you at:

https://mcp.propxchain.com/mcp
  • claude.ai / Claude Desktop: Settings, Connectors, Add custom connector, paste the URL, leave client ID and secret blank.
  • Claude Code: claude mcp add --transport http propxchain https://mcp.propxchain.com/mcp
  • ChatGPT, Cursor and other MCP clients: add a remote (Streamable HTTP) server with the URL above. Sign-in is OAuth 2.1, discovered automatically.

You approve the connection with your PropXchain email and a 6-digit code, then give your assistant a TX-XXXX-XXXX invite code. Remove it at any time from the transaction's bot panel.

Full setup walkthrough: propxchain.com/agent. Machine-readable manifest: propxchain.com/.well-known/mcp.json. Registry listing: server.json (io.github.Madhatt4/propxchain).

Run it locally instead (stdio)

For hosts without remote MCP support. The local server generates its own Ed25519 keypair on first launch (stored on disk, never copied across boundaries); access is still per transaction via invite code.

bash
npm install -g @propxchain/mcp-server

Then add to your Claude Desktop config (%APPDATA%/Claude/claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, ~/.config/Claude/claude_desktop_config.json on Linux):

json
{  "mcpServers": {    "propxchain": {      "command": "propxchain-mcp-server",      "env": { "IC_NETWORK": "ic" }    }  }}

For Claude Code, the equivalent single command is:

bash
claude mcp add propxchain propxchain-mcp-server -e IC_NETWORK=ic

Restart your agent. In a new chat, ask:

Join propxchain transaction TX-XXXX-XXXX as a bot called "Claude Desktop"

(Get the invite code from the share panel of any of your transactions on propxchain.com.)

Identity model

On first launch, the server reads or creates an Ed25519 seed at:

  • macOS / Linux: ~/.config/propxchain-mcp/identity.key (or $XDG_CONFIG_HOME/propxchain-mcp/identity.key if set)
  • Windows: %APPDATA%/propxchain-mcp/identity.key

The file is chmod 600 on POSIX and contains a single base64-encoded 32-byte seed plus a trailing newline. The bot's principal is derived from this seed and printed to stderr at startup.

Override for ops or CI: set BOT_PRIVATE_KEY in env to a base64-encoded 32-byte seed. When set, the server uses this instead of reading from disk.

Tools

17 tools across these categories:

CategoryTools
Bot managementpropxchain_join_transaction_as_bot, propxchain_list_my_transactions, propxchain_list_connected_bots
Transactionspropxchain_search_transactions, propxchain_get_transaction, propxchain_get_status, propxchain_create_transaction, propxchain_join_transaction, propxchain_get_transaction_chain
Documentspropxchain_verify_document, propxchain_list_documents, propxchain_upload_document
Checklistspropxchain_get_checklist, propxchain_update_checklist
Property intelligencepropxchain_get_property_intel
Educationpropxchain_explain_process, propxchain_send_message

Each tool's full schema is discoverable via the standard MCP tools/list call.

Security model

  • The bot principal only sees transactions the user has granted via invite code.
  • No write surface for funds, signatures, or transactions outside the granted ones.
  • Revocation is one click in the propxchain.com bot panel; calls transaction_manager.disconnectBot on chain.
  • The seed file lives on the user's local machine. The npm package contains no credentials.
  • npm provenance attestation is enabled on every release; verify with npm view @propxchain/mcp-server.

Build from source

bash
git clone https://github.com/Madhatt4/propxchain-mcp-server.gitcd propxchain-mcp-servernpm installnpm run build

npm run build compiles TypeScript and prepends a #!/usr/bin/env node shebang to dist/index.js (post-tsc, since tsc strips it). Test the binary directly:

bash
node dist/index.js

The server reads/creates the local identity file as above. To smoke-test the MCP protocol roundtrip, pipe an initialize + tools/list request:

bash
( printf '%s\n' \    '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' \    '{"jsonrpc":"2.0","method":"notifications/initialized"}' \    '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' ; \  sleep 2 ) | node dist/index.js

You should see your bot principal in stderr and the tool list in stdout.

Versioning

Releases are published manually via gh workflow run release.yml --field dry-run=false. Bump version in package.json first; the workflow refuses to republish an existing version and refuses pre-release suffixes on the latest tag. Pre-release validation runs the same MCP smoke test shown above before publishing.

License

UNLICENSED. The npm package is freely installable for use against PropXchain canisters; redistribution and modification rights are not granted.

Source: README.md at commit 61a7590

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.2.1LatestOct 9, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.