_ registry / mcp streamable-http · checked 4h ago

PPC for law firms (ppclawfirms.co.uk)

https://ppclawfirms.co.uk

Registry code: ad1f4f27a017df3d

api record

PPC for law firms (https://ppclawfirms.co.uk/): the site's own MCP server, served from its domain. Google Ads for UK law firms, run one practice area at a time. Tell us which work you want more of and get a fixed monthly fee before any advert goes live.

[enquiry] ENQUIRY SERVER for PPC for law firms (https://ppclawfirms.co.uk/). What it does: starts an ENQUIRY with PPC for law firms for ppc for law firms; the PPC for law firms team reads it and replies to the person directly, and the details go to nobody else. What it is NOT: a purchase, an order, or a guaranteed quote. Free, no obligation.…

endpoint
https://ppclawfirms.co.uk/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 it live, free and safe measured by this hub
Is PPC for law firms (ppclawfirms.co.uk) live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is PPC for law firms (ppclawfirms.co.uk) free to use?
Yes — the hub reached it with no key and no payment.
What tools does PPC for law firms (ppclawfirms.co.uk) have?
3 tools: submit_enquiry, enquiry_fields, enquiry_describe.
Is PPC for law firms (ppclawfirms.co.uk) 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,273ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 249 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • request a quote for google ads for a law firm
  • list enquiry form fields
  • submit a business enquiry to providers
takes → gives
text → data
tools
2 reads1 sends messages
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

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.

  • enquiry_describe reads open 12h ago

    Read first. States plainly what submit_enquiry does on PPC for law firms: it starts an enquiry with PPC for law firms, whose team reads it and replies directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • submit_enquiry sends messages unknown never probed

    Submits an enquiry to PPC for law firms: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before the PPC for law firms team sees it. Consent means the person has read and agreed to: "Happy to be contacted about this enquiry by the company that runs this site."

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "answers",
        "consent"
      ],
      "properties": {
        "answers": {
          "type": "object",
          "description": "the person's answers, keyed by field key",
          "additionalProperties": {
            "type": [
              "string",
              "number",
              "boolean"
            ]
          }
        },
        "consent": {
          "type": "boolean",
          "description": "true only when the person has agreed to: Happy to be contacted about this enquiry by the company that runs this site."
        },
        "confirmation": {
          "type": "string",
          "description": "the confirmation token from step 1, after the person has approved the summary"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • enquiry_fields reads unknown never probed

    Every field of the PPC for law firms enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ad1f4f27a017df3d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ad1f4f27a017df3d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ad1f4f27a017df3d/badge.svg)](https://brick.blue/agent/ad1f4f27a017df3d?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.

_ how we know
card completeness
70%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.