_ registry / mcp http-sse · checked 7h ago

zandomeni-mcp

https://lrqkraglvppygtmwwsie.supabase.co

Registry code: 18aace58ddec70dd

api record

Tools for the SCA Zandomeni law firm website (zandomeni.eu). Use `search_blog_posts` to find Romanian-language legal articles by keyword, `get_blog_post` to read one, `list_expertise_areas` to enumerate practice areas, and `get_contact_info` for firm contact details. Focus regional: Timișoara / județul Timiș / Banat.

endpoint
https://lrqkraglvppygtmwwsie.supabase.co/functions/v1/mcp
protocol
http-sse ·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 zandomeni-mcp live?
Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
Is zandomeni-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does zandomeni-mcp have?
4 tools: get_blog_post, search_blog_posts, list_expertise_areas, get_contact_info.
Is zandomeni-mcp 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 99.2%· all time 99.2%

latency
1,763ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 390 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search romanian legal articles
  • read a law firm article
  • list law firm practice areas
  • get law firm contact
takes → gives
text → text, data
tools
4 reads
_ 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 4 tools
2 open 2 never probed 2 of 4 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.

  • list_expertise_areas reads open 7h ago

    List the practice areas covered by SCA Zandomeni (Timișoara) with links to each area page.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_contact_info reads open 7h ago

    Return the public contact details of SCA Zandomeni — Timișoara (phone, email, website, service area).

    mcp-tool

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

    Fetch a single SCA Zandomeni blog article by slug. Returns title, description, canonical URL and article text.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "minLength": 1,
          "description": "Article slug (the part after /blog/ in the URL)."
        },
        "maxChars": {
          "type": "integer",
          "default": 6000,
          "maximum": 20000,
          "minimum": 500,
          "description": "Max characters of article text to return."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • search_blog_posts reads unknown never probed

    Search the SCA Zandomeni legal blog (~550 articles, Romanian) by keyword against article slugs. Returns matching URLs on zandomeni.eu.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Keyword(s) to match in the article slug/URL (Romanian, no diacritics)."
        }
      },
      "additionalProperties": false
    }
    arguments 21 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 18aace58ddec70dd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/18aace58ddec70dd/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/18aace58ddec70dd/badge.svg)](https://brick.blue/agent/18aace58ddec70dd?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
80%

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.

_ also on supabase.co 124 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

116 more sit on this domain. All of them.