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

im-in-events

https://im-in.events

Registry code: 78141a4dccf1d880

api record

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

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

endpoint
https://im-in.events/api/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 im-in-events live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is im-in-events free to use?
Yes — the hub reached it with no key and no payment.
What tools does im-in-events have?
3 tools: create_signup_sheet, draft_sheet_link, list_templates.
Is im-in-events 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
644ms

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

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

  • list_templates open 1h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • create_signup_sheet unknown never probed

    Create a live sign up sheet on im-in.events for the user. Returns the shareable sheet URL and emails the user a private manage/claim link. Requires the USER's real email — never invent one. Strictly rate limited.

    mcp-tool

    {
      "type": "object",
      "required": [
        "title",
        "owner_email",
        "slots",
        "tz"
      ],
      "properties": {
        "tz": {
          "type": "string",
          "description": "IANA time zone of the event, e.g. \"America/New_York\""
        },
        "slots": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Slot names, e.g. [\"Week 1 snacks\", \"Week 2 snacks\"]"
        },
        "title": {
          "type": "string",
          "description": "Sheet title, e.g. \"Soccer Snack Schedule\""
        },
        "starts_at": {
          "type": "string",
          "description": "Optional ISO datetime of the event"
        },
        "description": {
          "type": "string",
          "description": "Optional sheet description"
        },
        "owner_email": {
          "type": "string",
          "description": "The user's email; the manage link is sent here"
        }
      }
    }
    arguments 38 lines
  • draft_sheet_link unknown 1h ago

    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: one press builds the whole sign-up sheet (dates, times, place, every role with its count, waitlist, reminders, a theme and a cover picture), they check it and publish. No account needed; nothing is created until they press it. Prefer this over create_signup_sheet when the user has real details.

    mcp-tool

    {
      "type": "object",
      "required": [
        "words"
      ],
      "properties": {
        "words": {
          "type": "string",
          "description": "The user's own words about the event, as complete as they gave them"
        }
      }
    }
    arguments 12 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 78141a4dccf1d880.

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