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

djs-andorra

https://www.djs.ad

Registry code: 3d020c7123a92534

api record

DJs Andorra (djs.ad) is the agenda of electronic music parties in Andorra. Use these tools to answer what is on tonight, this weekend or on a given night, by town, DJ or venue. Nights run in Andorra time and anything before 06:00 belongs to the night before. Always link the party's djs.ad page when you mention one. Answers are in Catalan; translate them for the user if needed. Party facts are CC BY 4.0, credit "DJs Andorra (djs.ad)". Privacy: https://www.djs.ad/privacitat. Contact: [email protected].

endpoint
https://www.djs.ad/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 djs-andorra live?
Yes — it answered the hub's last check (checked 23h ago). It answered 100% of checks over the last 30 days.
Is djs-andorra free to use?
Yes — the hub reached it with no key and no payment.
What tools does djs-andorra have?
4 tools: get_party, this_weekend, whats_on_tonight, search_parties.
Is djs-andorra 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
365ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
3 open 1 never probed 3 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.

  • this_weekend open 23h ago

    Parties from Friday to Sunday: this weekend, or the next one when asked from Monday to Thursday.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "dj": {
          "type": "string",
          "description": "A DJ's name or djs.ad slug."
        },
        "town": {
          "type": "string",
          "description": "Town or parish, for example \"Canillo\", \"Soldeu\" or \"Pas de la Casa\". Accents and case are ignored."
        },
        "venue": {
          "type": "string",
          "description": "A venue's name."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • whats_on_tonight open 23h ago

    Parties in Andorra tonight (the current night in Andorra time), with venue, DJs and each party's djs.ad link.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "dj": {
          "type": "string",
          "description": "A DJ's name or djs.ad slug."
        },
        "town": {
          "type": "string",
          "description": "Town or parish, for example \"Canillo\", \"Soldeu\" or \"Pas de la Casa\". Accents and case are ignored."
        },
        "venue": {
          "type": "string",
          "description": "A venue's name."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • search_parties open 23h ago

    Coming parties in Andorra, filtered by night range, town, DJ, venue or free text. Soonest first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Free text matched against party name, venue, town and DJs."
        },
        "dj": {
          "type": "string",
          "description": "A DJ's name or djs.ad slug."
        },
        "to": {
          "type": "string",
          "description": "Last night to include, YYYY-MM-DD."
        },
        "from": {
          "type": "string",
          "description": "First night to include, YYYY-MM-DD (Andorra nights)."
        },
        "town": {
          "type": "string",
          "description": "Town or parish, for example \"Canillo\", \"Soldeu\" or \"Pas de la Casa\". Accents and case are ignored."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "At most this many (default 20)."
        },
        "venue": {
          "type": "string",
          "description": "A venue's name."
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
  • get_party unknown never probed

    Full details of one party by its id (from another tool or a djs.ad/festes/<id> link).

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The party 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 3d020c7123a92534.

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