accueil / serveurs / Dev & Code / app.housefile/licensing
app.housefile/licensing
serveur MCP (Model Context Protocol) · housefile-licensing 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que app.housefile/licensing est sûr ?
Au dernier audit MCP Hub, le serveur MCP « app.housefile/licensing » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 4 outils
- check_property_licensing≈ 1232 tokens
Looks up a postcode in England in HouseFile’s records of council licensing schemes and returns each scheme in force there, with its dates, fee, source link and the date the records were last verified, plus the national HMO rule. Schemes not in force yet are listed under upcoming. It works to postcode precision, so near a scheme’s edge it says so. Give occupants and households to settle the mandatory HMO test in England.
Paramètres, retour & exemple (5)
Paramètrespostcode· string · requis
A full UK postcode in any spacing or case, such as "e8 1dy"occupants· integer · optionnel
How many people live in the propertyas_of_date· string · optionnel
YYYY-MM-DD. Defaults to today; at most 24 months aheadhouseholds· integer · optionnel
How many separate households they formaddress_line· string · optionnel
House number or name and street. Accepted, but the lookup works to postcode precision, and the address is never stored
Exemple d'appel{"name": "check_property_licensing", "arguments": {"postcode": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"council": "texte", "country": "England", "covered": true, "schemes": [], "postcode": "texte", "upcoming": [], "as_of_date": "texte", "disclaimer": "texte", "housefile_url": "texte", "council_gss_code": "texte", "council_address_checker": "texte"}} - licensing_coverage≈ 368 tokens
Which councils HouseFile’s records cover, with the number of published schemes for each and when they were last verified. Use it to tell the user honestly whether their area is covered.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "licensing_coverage", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "councils": [], "council_count": 1, "housefile_url": "texte", "published_scheme_count": 1, "most_recent_verification": "texte"}} - list_council_schemes≈ 754 tokens
Lists a council’s licensing schemes from HouseFile’s records: in force, starting soon, proposed, and ended in the last 12 months, each with its area, dates, fee, source link and last verified date. Takes a council name, part of a name or a GSS code. If several councils match, it returns them to choose from.
Paramètres, retour & exemple (1)
Paramètrescouncil· string · requis
A council name, part of one, or its GSS code, such as "Croydon" or "E09000008"
Exemple d'appel{"name": "list_council_schemes", "arguments": {"council": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "result": "found", "council": "texte", "schemes": [], "candidates": [], "disclaimer": "texte"}} - upcoming_licensing_changes≈ 820 tokens
What’s coming: schemes proposed or starting soon, and recent changes to schemes in HouseFile’s records (started, ended, fee or area changed), newest first. Optionally for one council, and for a number of months ahead and back (6 by default, at most 24).
Paramètres, retour & exemple (2)
Paramètrescouncil· string · optionnel
A council name, part of one, or its GSS codewithin_months· integer · optionnel
Months ahead and back to look, 6 by default
Exemple d'appel{"name": "upcoming_licensing_changes", "arguments": {"council": "texte", "within_months": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "found", "council": "texte", "upcoming": [], "candidates": [], "disclaimer": "texte", "within_months": 1, "recent_changes": []}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».