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

status-social

https://status-social.com

Registry code: ea2c9b35b7b51ec4

api record

Status Social creates shareable event invite links for get-togethers such as parties, dinners, birthdays, trips and society socials. Guests RSVP on the link; the host adds date polls, shared costs and photos there. Tools: status_create_event (new draft invite, returns a private claim link for the user and an invite link for guests), status_get_event (details and RSVPs), status_update_event (change title, details, place, date, time or theme). No account or API key. Not for calendar entries, solo reminders, one-to-one meetings, or selling tickets to public events.

endpoint
https://status-social.com/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 status-social live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is status-social free to use?
Yes — the hub reached it with no key and no payment.
What tools does status-social have?
3 tools: status_create_event, status_update_event, status_get_event.
Is status-social 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
361ms

last good check

priced tools
0

of 3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 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.

  • status_create_event unknown never probed

    Create a shareable event invite link where guests RSVP, for a party, dinner, birthday, trip, night out or other get-together; the host can then add a date poll and split costs on the same page. Use when the user is planning something with other people and wants a link to send round. Not for calendar entries, solo reminders, one-to-one meetings or selling tickets to public events. Only title is required; details, location, date, time, timeZone, theme and hostName are optional. No account or API key. Returns claimUrl (private to the user: opening it and signing in makes them the host; until then the event is a draft and guests cannot join), inviteUrl (for guests, works once claimed), eventUrl, eventId and editKey (for status_get_event and status_update_event, valid 7 days).

    mcp-tool

    {
      "type": "object",
      "required": [
        "title"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Event date as YYYY-MM-DD. Leave out if the date is not set yet"
        },
        "time": {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
          "description": "Start time as 24-hour HH:mm, local to timeZone, e.g. 19:30. Needs date"
        },
        "theme": {
          "enum": [
            "party",
            "dinner",
            "garden",
            "sport",
            "holiday",
            "plain"
          ],
          "type": "string",
          "description": "Visual style of the invite page: party, dinner, garden, sport, holiday, plain. Defaults to party"
        },
        "title": {
          "type": "string",
          "maxLength": 100,
          "description": "Event name shown at the top of the invite, e.g. \"Sam's 30th\" or \"Book club dinner\""
        },
        "details": {
          "type": "string",
          "description": "Invite message for guests: what is happening, what to bring, dress code, cost per person"
        },
        "hostName": {
          "type": "string",
          "description": "The user's first name, shown as host on the invite until they claim it"
        },
        "location": {
          "type": "string",
          "maxLength": 200,
          "description": "Venue name or address, e.g. \"The Albion, Bristol\""
        },
        "timeZone": {
          "type": "string",
          "description": "IANA time zone for date and time, e.g. Europe/London (the default) or America/New_York"
        }
      }
    }
    arguments 52 lines
  • status_update_event unknown never probed

    Change the title, details, place, date, time or theme of an event invite made with status_create_event. Send eventId, editKey and only the fields to change. The invite link stays the same and guests see the change straight away. Does not change a date poll, the guest list or costs, and cannot cancel or delete the event.

    mcp-tool

    {
      "type": "object",
      "required": [
        "eventId",
        "editKey"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Event date as YYYY-MM-DD. Leave out if the date is not set yet"
        },
        "time": {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
          "description": "Start time as 24-hour HH:mm, local to timeZone, e.g. 19:30. Needs date"
        },
        "theme": {
          "enum": [
            "party",
            "dinner",
            "garden",
            "sport",
            "holiday",
            "plain"
          ],
          "type": "string",
          "description": "Visual style of the invite page: party, dinner, garden, sport, holiday, plain. Defaults to party"
        },
        "title": {
          "type": "string",
          "maxLength": 100,
          "description": "Event name shown at the top of the invite, e.g. \"Sam's 30th\" or \"Book club dinner\""
        },
        "details": {
          "type": "string",
          "description": "Invite message for guests: what is happening, what to bring, dress code, cost per person"
        },
        "editKey": {
          "type": "string",
          "description": "editKey returned by status_create_event"
        },
        "eventId": {
          "type": "string",
          "description": "eventId returned by status_create_event"
        },
        "location": {
          "type": "string",
          "maxLength": 200,
          "description": "Venue name or address, e.g. \"The Albion, Bristol\""
        },
        "timeZone": {
          "type": "string",
          "description": "IANA time zone for date and time, e.g. Europe/London (the default) or America/New_York"
        }
      }
    }
    arguments 57 lines
  • status_get_event unknown 1h ago

    Read an event invite made with status_create_event: who is coming and how many people have replied (each guest's name and RSVP: confirmed for yes, maybe, pass for no, or pending), its title, details, place, date, time and theme, and whether the user has claimed it. Needs the eventId and editKey from status_create_event. Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "eventId",
        "editKey"
      ],
      "properties": {
        "editKey": {
          "type": "string",
          "description": "editKey returned by status_create_event"
        },
        "eventId": {
          "type": "string",
          "description": "eventId returned by status_create_event"
        }
      }
    }
    arguments 17 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 ea2c9b35b7b51ec4.

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