Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Status Social

REMOTE · STATUS-SOCIAL.COM

Turn a plan into a shareable event invite link from chat, check RSVPs and edit details.

67 Trust /100

Last scanned (20 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 942 tokens (~314/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://status-social.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=status-social.com CN=YR2,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 RSA 2048 SHA256-RSA 6a920537f90ca41d20d646a146b302e70b0
SANs: status-social.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of status-social.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
status-social.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://status-social.com/mcp Verified 200
http (plaintext) http://status-social.com/mcp HTTPS enforced 308 https://status-social.com/mcp
MCP tools · 3 exposed · ~818 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
status_create_event ~400

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).

NameTypeReqDescription
datestring–Event date as YYYY-MM-DD. Leave out if the date is not set yet
detailsstring–Invite message for guests: what is happening, what to bring, dress code, cost per person
hostNamestring–The user's first name, shown as host on the invite until they claim it
locationstring–Venue name or address, e.g. "The Albion, Bristol"
themestring–Visual style of the invite page: party, dinner, garden, sport, holiday, plain. Defaults to party
timestring–Start time as 24-hour HH:mm, local to timeZone, e.g. 19:30. Needs date
timeZonestring–IANA time zone for date and time, e.g. Europe/London (the default) or America/New_York
titlestringyesEvent name shown at the top of the invite, e.g. "Sam's 30th" or "Book club dinner"
NameTypeReqDescription
claimUrlstringyesPrivate link for the user only: opening it and signing in makes them the host
editKeystringyesCredential for status_update_event and status_get_event. Valid for 7 days.
eventobject–The event as guests see it
eventIdstringyes–
inviteUrlstringyesInvite link for guests; works once the user has claimed the event
messagestringyesPlain-language summary of the result

No examples provided.

status_get_event ~115

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.

NameTypeReqDescription
editKeystringyeseditKey returned by status_create_event
eventIdstringyeseventId returned by status_create_event
NameTypeReqDescription
eventobjectyesThe event as guests see it
messagestringyesPlain-language summary of the result

No examples provided.

status_update_event ~303

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.

NameTypeReqDescription
datestring–Event date as YYYY-MM-DD. Leave out if the date is not set yet
detailsstring–Invite message for guests: what is happening, what to bring, dress code, cost per person
editKeystringyeseditKey returned by status_create_event
eventIdstringyeseventId returned by status_create_event
locationstring–Venue name or address, e.g. "The Albion, Bristol"
themestring–Visual style of the invite page: party, dinner, garden, sport, holiday, plain. Defaults to party
timestring–Start time as 24-hour HH:mm, local to timeZone, e.g. 19:30. Needs date
timeZonestring–IANA time zone for date and time, e.g. Europe/London (the default) or America/New_York
titlestring–Event name shown at the top of the invite, e.g. "Sam's 30th" or "Book club dinner"
NameTypeReqDescription
eventobjectyesThe event as guests see it
messagestringyesPlain-language summary of the result

No examples provided.

Install

How do I install the Status Social MCP server?

Status Social is a hosted endpoint at https://status-social.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · status-social.com

# add to Claude Code
claude mcp add --transport http com-status-social-status-social 'https://status-social.com/mcp'
Common questions

What is the Status Social MCP server?

Status Social is an MCP server listed in the public MCP registry as com.status-social/status-social. Turn a plan into a shareable event invite link from chat, check RSVPs and edit details. This page covers its hosted endpoint (https://status-social.com/mcp).

Is the Status Social MCP server safe to use?

Status Social scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Status Social MCP server expose?

Status Social exposes 3 tools: status_create_event, status_get_event, status_update_event. Their descriptions and schemas cost roughly 818 tokens of context every time the server is loaded.

Does the Status Social MCP server require authentication?

No. We connected to Status Social without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Status Social MCP server still maintained?

Status Social is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Status Social MCP server?

VerifyMCP ran 13 checks on Status Social, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.