Nearby Notices
Related Servers
Alternatives to Nearby Notices
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables querying official UK public records from The Gazette, including insolvencies, winding-up petitions, and deceased estates.74 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve a full UK postcode report, perform fast geography lookups, compare up to five postcodes side by side, and search or fetch the underlying open dataset registry through the Model Context Protocol.1-
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve UK Companies House data including company profiles, officers, and filing history via the official API.4199 npm1MIT

Zyfy MCP Serverofficial
AlicenseAqualityDmaintenanceEnables natural language queries about UK postcodes and vehicles, including flood risk, crime rate, broadband coverage, property prices, MOT history, and ULEZ compliance.439 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables querying UK Companies House data via natural language, including company profiles, officers, filing history, and other statutory records.107 npmMIT
- FlicenseBqualityDmaintenanceProvides access to UK Companies House public data, enabling search and retrieval of company profiles, officers, filing history, and more through natural language queries.12-
TDQS
Scored across 3 tools
The three tools serve clearly distinct roles: coverage is a meta-information tool, find_notices_near searches by place, and read_notice retrieves a specific notice by id. There is no overlap in purpose or expected inputs, and the descriptions explicitly tell the agent when to use each.
The action-oriented tools use a consistent snake_case verb_noun pattern (find_notices_near, read_notice). The meta tool 'coverage' deviates by being a bare noun rather than a verb phrase, which is a minor inconsistency but still readable and clear.
Three tools are exactly right for a focused notice discovery and reading server: one explains scope and terms, one searches nearby, and one reads a full notice. No tool feels redundant or missing from the core workflow.
The surface covers scope, nearby search, and detail retrieval, but find_notices_near is capped at 12 newest results with no pagination and no filtering by notice kind, date, or authority. These are notable gaps for an agent that needs to browse beyond the most recent dozen notices.