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.

I'm In! Sign-up Sheets

REMOTE · IM-IN.EVENTS

Turn an email, notes or a flyer into a free sign-up sheet with reminders and waitlists.

Available components

66 Trust /100

Last scanned (21 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Productivity and Notes

Recent critical change

Authorization (17 Oct 2026). See the changelog before you install this server.

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 Security57
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 350 tokens (~116/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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
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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 18 Oct 26 +1

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

  • 17 Oct 26 +1
    • Authorization: unverified → fail ▼ critical
    • HSTS header: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.17 ▲ functional
  • 16 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 14 Oct 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.

  • 13 Oct 26 0
    • Schema quality: 103 → 116 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • “create_signup_sheet” reworded the description of “slots” cosmetic
  • 12 Oct 26 63

    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 18 Oct 2026 · Probed https://im-in.events/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=im-in.events CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 b7177872cbdc5530e21e2a37d1ac5a2
SANs: im-in.events, *.im-in.events
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of im-in.events. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
events. present 12487 8 Verified
im-in.events. absent 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
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://im-in.events/api/mcp Verified 200
http (plaintext) http://im-in.events/api/mcp HTTPS enforced 301 https://im-in.events/api/mcp
MCP tools · 3 exposed · ~350 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
create_signup_sheet ~208

Create a live sign-up sheet on im-in.events from a title, slot names and a time zone. Returns the shareable sheet URL and emails a private manage and claim link to owner_email, the user's own address. One sheet per owner email a day.

NameTypeReqDescription
descriptionstring–Optional sheet description
owner_emailstringyesThe user's email; the manage link is sent here
slotsarrayyesOne line per item people sign up for, 1 spot each. Add " x4" for 4 spots, or " (no limit)" so anyone can sign up, e.g. ["Week 1 snacks", "Setup crew x4", "Coming (no limit)"]
starts_atstring–Optional ISO datetime of the event
titlestringyesSheet title, e.g. "Soccer Snack Schedule"
tzstringyesIANA time zone of the event, e.g. "America/New_York"

No output schema declared.

No examples provided.

draft_sheet_link ~109

Turn the user's email, notes, flyer text or description of their event into a link that opens im-in.events with those words in the Describe it box. Pressing Make my draft there builds the whole sign-up sheet (dates, times, place, every role with its count, waitlist, reminders and its look) for the user to check and publish. Creates nothing and needs no account.

NameTypeReqDescription
wordsstringyesThe user's own words about the event, as complete as they gave them

No output schema declared.

No examples provided.

list_templates ~33

List I'm In! sign up sheet templates (potluck, meal train, volunteer shifts, ...) with their prefilled slots.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the I'm In! Sign-up Sheets MCP server?

I'm In! Sign-up Sheets is a hosted endpoint at https://im-in.events/api/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 · im-in.events

# add to Claude Code
claude mcp add --transport http events-im-in-sign-up-sheets 'https://im-in.events/api/mcp'
Common questions

What is the I'm In! Sign-up Sheets MCP server?

I'm In! Sign-up Sheets is an MCP server listed in the public MCP registry as events.im-in/sign-up-sheets. Turn an email, notes or a flyer into a free sign-up sheet with reminders and waitlists. This page covers its hosted endpoint (https://im-in.events/api/mcp).

Is the I'm In! Sign-up Sheets MCP server safe to use?

I'm In! Sign-up Sheets scores 66 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 I'm In! Sign-up Sheets MCP server expose?

I'm In! Sign-up Sheets exposes 3 tools: draft_sheet_link, list_templates, create_signup_sheet. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.

Does the I'm In! Sign-up Sheets MCP server require authentication?

No. We connected to I'm In! Sign-up Sheets without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the I'm In! Sign-up Sheets MCP server still maintained?

I'm In! Sign-up Sheets is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.