uk-planning-mcp
https://uk-planning-mcp.donniertf.workers.dev
Registry code: 9241523c03583281
UK planning data access for planning research and local planning authority summaries. Includes planning and LPA summary tool packs.
from a public catalogue that lists it, not from the operator
- endpoint
- https://uk-planning-mcp.donniertf.workers.dev/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is uk-planning-mcp live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
- Is uk-planning-mcp free to use?
- Not measured yet.
- What tools does uk-planning-mcp have?
- 4 tools: planning_discover, lpa_summary_pack, planning_pack, redeem_pack.
- Is uk-planning-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 94.6%· all time 94.6%
last good check
of 4 tools
- down → live
- degraded → down· HTTP 500
- live → degraded· HTTP 500
- down → live
- degraded → down· HTTP 500
- used for
- look up uk planning applications
- buy planning applications pack
- buy local planning authority summary
- takes → gives
- text → data
- tools
- 2 reads2 moves money
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
planning_discover reads unknown never probed
Free peek: up to 5 UK planning applications for an LPA name or postcode (e.g. Doncaster). Cached 24h. Soft-Offer outbound is OFF.
{ "type": "object", "required": [ "lpaOrPostcode" ], "properties": { "size": { "type": "number", "description": "Max results (default 5, max 5 for free)" }, "lpaOrPostcode": { "type": "string", "description": "LPA / council name OR UK postcode" } } }arguments 16 lineslpa_summary_pack moves money unknown never probed
Paid LPA summary pack: apps + status_mix + risk_flags. Returns Stripe Checkout URL (£0.49). Soft-Offer outbound is OFF.
{ "type": "object", "required": [ "lpaOrPostcode" ], "properties": { "size": { "type": "number", "description": "Pack size (default 25, max 100)" }, "lpaOrPostcode": { "type": "string", "description": "LPA / council name OR UK postcode" } } }arguments 16 linesplanning_pack moves money unknown never probed
Paid planning applications pack for an LPA / postcode. Returns Stripe Checkout URL (£0.49). Soft-Offer outbound is OFF.
{ "type": "object", "required": [ "lpaOrPostcode" ], "properties": { "size": { "type": "number", "description": "Pack size (default 25, max 100)" }, "lpaOrPostcode": { "type": "string", "description": "LPA / council name OR UK postcode" } } }arguments 16 linesredeem_pack reads unknown never probed
Instructions to redeem a paid Stripe Checkout session. Pass session_id from checkout.
{ "type": "object", "required": [ "session_id" ], "properties": { "session_id": { "type": "string", "description": "Stripe Checkout session id (cs_...)" } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id9241523c03583281.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9241523c03583281/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9241523c03583281?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.