VerifyUK Property Check

io.github.namnam57Published by GitHub account namnam57v0.5.1Updated Oct 24, 2026

Cited English property planning-constraint screening and batch tools for AI agents.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant screen English property planning constraints, including batch checks, for AI agents.

What you can do
  • Screen properties against English planning constraints, one property at a time.
  • Run batch screening across multiple properties.
  • Return cited results so findings can be traced to their source.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when an assistant needs to check English property planning constraints, such as for conveyancing, development or site due-diligence questions, and when many properties must be screened at once.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. An API key supplied in the X-API-Key header is required for authenticated access.
Before you install
The server requires an API key in the X-API-Key header; keep it private and check how it is stored and transmitted. Screening results are planning-constraint indications only and should not be treated as legal or professional property advice.

Installation

In SourceWeft

  1. Open VerifyUK Property Check in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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.namnam57%2Fverifyuk-property-check/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.

{
  "mcpServers": {
    "verifyuk-property-check": {
      "type": "http",
      "url": "https://verifyuk-property-check-production.up.railway.app/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.5.1LatestSep 16, 2026

Score

60% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Check integrations