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

meseriasi

https://www.meseriasi.ro

Registry code: 56c611a17bcfe9f9

api record

MCP server for meseriasi.ro, a Romanian homeowner-tradesperson marketplace.

from a public catalogue that lists it, not from the operator

endpoint
https://www.meseriasi.ro/api/mcp
door code
b5ccd7abde87986c
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 meseriasi live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is meseriasi free to use?
Yes — the hub reached it with no key and no payment.
What tools does meseriasi have?
6 tools: request_chat_otp, start_conversation, contact_tradesperson, create_project, get_tradesperson_profile, search_tradespeople.
Is meseriasi 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
99.5%

90 days 99.6%· all time 100%

latency
4,026ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 695 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search romanian tradespeople
  • get a tradesperson profile
  • post a home project
  • start a conversation with a tradesperson
takes → gives
text → data
tools
2 reads1 changes data2 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 6 tools
1 open 5 never probed 1 of 6 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.

  • search_tradespeople reads open 11h ago

    Search for tradespeople on meseriasi.ro by location and/or category (trade type). Returns a paginated list of matching profiles.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "number",
          "description": "Page number (default 1)"
        },
        "category": {
          "type": "string",
          "description": "Trade type / profession category (e.g. \"electrician\", \"instalator\", \"zugrav\")"
        },
        "location": {
          "type": "string",
          "description": "City or region name to filter by (e.g. \"București\", \"Cluj-Napoca\")"
        },
        "per_page": {
          "type": "number",
          "description": "Results per page, max 50 (default 10)"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • request_chat_otp sends messages unknown never probed

    Send a one-time password (OTP) to the user's email so they can verify their identity before starting a conversation with a tradesperson. Call this first, then call start_conversation with the OTP the user receives.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "The homeowner's email address"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • start_conversation sends messages unknown never probed

    Verify the OTP sent to the user's email and start a direct conversation with a tradesperson. Creates a homeowner account automatically if the email is new.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email",
        "otp",
        "tradesperson_id",
        "message"
      ],
      "properties": {
        "otp": {
          "type": "string",
          "description": "The 6-digit OTP code the user received by email"
        },
        "email": {
          "type": "string",
          "description": "The homeowner's email address (same as used in request_chat_otp)"
        },
        "message": {
          "type": "string",
          "description": "The initial message to send to the tradesperson"
        },
        "tradesperson_id": {
          "type": "string",
          "description": "UUID of the tradesperson to contact"
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • contact_tradesperson unknown never probed

    Open the inline contact form for a specific tradesperson. Returns the tradesperson's display name so the UI can collect the user's email and message; the messaging itself happens via request_chat_otp then start_conversation. Use this when the user wants to message or get in touch with a tradesperson they found.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tradesperson_id"
      ],
      "properties": {
        "tradesperson_id": {
          "type": "string",
          "description": "UUID of the tradesperson to contact"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • create_project changes data unknown never probed

    Create a new project on meseriasi.ro as a homeowner. Notifies nearby tradespeople automatically. Requires the caller to supply a valid Supabase access token in the "access_token" argument.

    mcp-tool

    {
      "type": "object",
      "required": [
        "access_token",
        "title",
        "tradeType",
        "location"
      ],
      "properties": {
        "title": {
          "type": "string",
          "description": "Short descriptive title for the project (max 255 chars)"
        },
        "budget": {
          "type": "number",
          "description": "Approximate budget in RON (optional)"
        },
        "location": {
          "type": "string",
          "description": "City / address where the work is needed"
        },
        "tradeType": {
          "type": "string",
          "description": "Category of trade required (e.g. \"electrician\", \"instalator\")"
        },
        "description": {
          "type": "string",
          "description": "Detailed description of the work needed"
        },
        "access_token": {
          "type": "string",
          "description": "Supabase JWT access token for the homeowner account"
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
  • get_tradesperson_profile reads unknown 11h ago

    Fetch the full profile of a tradesperson by their UUID (or legacy WordPress integer ID). Includes bio, location, trade type, and bid statistics.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Tradesperson UUID or legacy integer ID"
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 56c611a17bcfe9f9.

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

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.