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

eventcompletion

https://eventcompletion.com

Registry code: 611e6eaab361ee2f

api record

EventCompletion tracks the progress of events between a start and an end date and keeps a curated, source-verified catalogue (sports, festivals, trade shows, French school holidays, French political calendar…). Use search_events / upcoming_events / get_event to answer questions about dates; every event has a page_url worth citing. Dates are inclusive calendar days. To add an event, call register_agent once (keep the api_key, send it as "Authorization: Bearer <key>"), confirm the contact e-mail, then create_event.

endpoint
https://eventcompletion.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 eventcompletion live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is eventcompletion free to use?
Yes — the hub reached it with no key and no payment.
What tools does eventcompletion have?
5 tools: create_event, register_agent, get_event, search_events, upcoming_events.
Is eventcompletion 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
380ms

last good check

priced tools
0

of 5 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 5 tools
2 open 3 never probed 2 of 5 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.

  • search_events open 2h ago

    Search EventCompletion's curated events by words in the name or description (every word must match, any order), optionally filtered by status, category and language. Returns dates, progress, location and the page URL.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Default 10."
        },
        "query": {
          "type": "string",
          "description": "Words to look for, e.g. \"fiba world cup\" or \"vacances zone b\"."
        },
        "status": {
          "enum": [
            "ongoing",
            "upcoming",
            "completed",
            "all"
          ],
          "type": "string",
          "description": "Default: all."
        },
        "category": {
          "type": "string",
          "description": "e.g. sport, culture, trade-show, tech, school, politics, institutions, civic, music, market, tv-film."
        },
        "language": {
          "enum": [
            "fr",
            "en"
          ],
          "type": "string",
          "description": "Language of the event page."
        }
      }
    }
    arguments 37 lines
  • upcoming_events open 2h ago

    Events that start soonest (curated catalogue). Use it for "what is coming up?" questions.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1
        },
        "category": {
          "type": "string"
        },
        "language": {
          "enum": [
            "fr",
            "en"
          ],
          "type": "string"
        },
        "within_days": {
          "type": "integer",
          "maximum": 730,
          "minimum": 1,
          "description": "Only events starting within this many days. Default 90."
        }
      }
    }
    arguments 26 lines
  • create_event unknown never probed

    Create a public progress page for an event (needs an API key whose contact e-mail is confirmed; max 10 per day). The event is unlisted: it is reachable by its URL but not featured in the catalogue or sitemap. Dates are inclusive calendar days.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "start_date",
        "end_date"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 120,
          "minLength": 3
        },
        "end_date": {
          "type": "string",
          "description": "Last day (inclusive), YYYY-MM-DD, not before start_date."
        },
        "language": {
          "enum": [
            "fr",
            "en"
          ],
          "type": "string",
          "description": "Language of the page. Default en."
        },
        "start_date": {
          "type": "string",
          "description": "First day, YYYY-MM-DD."
        },
        "description": {
          "type": "string",
          "maxLength": 500
        }
      }
    }
    arguments 35 lines
  • register_agent unknown never probed

    Issue an API key for your agent (shown once, keep it). Send it as "Authorization: Bearer <key>" on later requests for higher rate limits. Give a contact_email to be able to create events: a confirmation link is sent to it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 60,
          "minLength": 3,
          "description": "Name of your agent or client, e.g. \"Acme research assistant\"."
        },
        "contact_email": {
          "type": "string",
          "description": "Optional but required to create events. A human must confirm it."
        }
      }
    }
    arguments 18 lines
  • get_event unknown 2h ago

    Details of one event by slug (the last part of its URL), including progress right now and where its dates were verified.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "e.g. \"wimbledon-2027\"."
        }
      }
    }
    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 611e6eaab361ee2f.

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

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.