Home / MCP registry index / io.github.Ments123/dmd-costs-tools

DMD Costs legal costs tools

io.github.Ments123/dmd-costs-tools in the official MCP registry. Endpoint https://www.dmdcosts.co.uk/mcp.

The registry describes it as: Free legal costs tools for England and Wales: CPR deadlines, Part 36, fixed costs, fees, interest.

We read its 38 tools on 2026-10-29. 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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http dmd-costs-tools https://www.dmdcosts.co.uk/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "dmd-costs-tools": {
      "url": "https://www.dmdcosts.co.uk/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"dmd-costs-tools","type":"http","url":"https://www.dmdcosts.co.uk/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

search_legal_costs_help look_up_cpr_costs_rule get_statement_of_truth_wording calculate_cpr_deadline calculate_pre_action_protocol_deadlines calculate_limitation_period calculate_fast_track_timetable check_relief_from_sanctions check_appeal_route_and_deadline calculate_detailed_assessment_deadlines find_detailed_assessment_court calculate_deemed_service calculate_civil_court_fees find_court_fee_by_form calculate_interest_on_costs calculate_judgment_interest calculate_interest_on_damages calculate_part_36_offer calculate_statutory_demand_deadlines check_enforcement_options calculate_employment_tribunal_time_limit calculate_judicial_review_time_limits check_cpr_21_10_approval calculate_part_35_and_part_18_dates calculate_financial_remedy_timetable calculate_pi_portal_timescales explain_costs_order calculate_fixed_costs check_small_claims_costs calculate_litigant_in_person_costs check_security_for_costs check_solicitors_act_assessment check_vat_on_costs build_calderbank_offer calculate_employment_tribunal_costs calculate_court_of_protection_fixed_costs check_awaabs_law_timescales look_up_j_codes

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-ments123-dmd-costs-tools/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ments123-dmd-costs-tools)

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.