Home / MCP registry index / com.civilquants/civilquants
com.civilquants/civilquants
com.civilquants/civilquants in the official MCP registry.
Endpoint https://api.civilquants.com/mcp.
The registry describes it as: Parametric estimating engine: CESMM4/NRM2/SMM7/MMHW Bills of Quantities for civils assemblies.
We read its 56 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
compute_connection_to_existing compute_hard_material_in_trench compute_ditch compute_pipework_testing compute_catchpit compute_manhole compute_manhole_precast compute_box_culvert compute_gully compute_headwall_attenuation_outlet compute_headwall_precast compute_headwall compute_carrier_pipe_run compute_french_drain compute_edge_drain compute_pipe_bedding compute_soakaway compute_attenuation_tank compute_swale compute_petrol_oil_interceptor compute_gabion_wall compute_reinforced_soil_wall compute_soil_nailed_slope compute_embankment_cross_section compute_end_area_earthworks compute_parapet compute_highway_drainage_channel compute_lighting_column compute_vehicle_restraint_system compute_road_marking compute_traffic_sign compute_flexible_pavement compute_permeable_pavement compute_rigid_pavement compute_anchored_wall compute_bored_pile_wall compute_cantilever_wall compute_counterfort_wall compute_gravity_wall compute_kerb_run compute_pad_foundation compute_strip_foundation compute_utility_chamber compute_utility_kiosk_base compute_combined_services_trench compute_single_service_run render_skill_report save_project get_project list_projects recompute_project compute_multi_section_assembly resolve_assembly_from_description list_skills get_skill get_document_pipeline
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-civilquants-civilquants)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.