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.

Universe MCP by usefulapi

REMOTE · UNIVERSE.USEFULAPI.IO

Read events, ticket types, orders, attendees and daily ticket sales in Universe.

18 Trust /100

Last scanned (13 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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.

  • 2 Nov 26 −48
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.03 → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 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 5 Nov 2026 · Probed https://universe.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
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 universe.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://universe.usefulapi.io/mcp Redirected 302 https://usefulapi.io/universe/
http (plaintext) http://universe.usefulapi.io/mcp Inconclusive 302 http://universe.usefulapi.io/mcp
MCP tools · 9 exposed · ~874 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
universe_event_sales_by_day ~68

Return ticket sales per day for an event between two dates (YYYY-MM-DD, inclusive). Read-only.

NameTypeReqDescription
eventIdstringyesEvent id.
fromstringyesFirst day, YYYY-MM-DD.
tostringyesLast day, YYYY-MM-DD.

No output schema declared.

No examples provided.

universe_get_event ~55

Fetch one event by id: description, address, dates, capacity, tickets sold, sales amount, category and host. For ticket types use universe_list_ticket_types. Read-only.

NameTypeReqDescription
eventIdstringyesEvent id.

No output schema declared.

No examples provided.

universe_get_order ~50

Fetch one order by id: buyer, state, cost breakdown, time slot, checkout answers and the ticket items with their check-in state. Read-only.

NameTypeReqDescription
orderIdstringyesOrder id.

No output schema declared.

No examples provided.

universe_get_viewer ~39

Return the signed-in Universe user and the host accounts they can manage (team memberships). Use a host id with universe_list_events. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

universe_list_attendees ~144

List the attendees (ticket holders) of an event: name, email, ticket type, time slot, ticket state and checkout answers. Filter by ticket state, text match or time slot. Contains personal data. Read-only.

NameTypeReqDescription
eventIdstringyesEvent id.
limitinteger–Page size. Default 25, max 100.
matchstring–Text to match (name or email).
offsetinteger–Number of rows to skip. Default 0.
statesarray–Only tickets in these states, e.g. PAID.
timeSlotIdsarray–Only these time slot ids.

No output schema declared.

No examples provided.

universe_list_events ~149

List events (id, title, url, state, first date, venue, tickets sold). Without hostId it lists the signed-in user's own events; with hostId it lists that host account's events (ids come from universe_get_viewer). Read-only.

NameTypeReqDescription
hostIdstring–Host account id. Omit for your own events.
limitinteger–Page size. Default 25, max 100.
offsetinteger–Number of rows to skip. Default 0.
searchstring–Text to match in the event title (host events only).
statesarray–Only events in these states, e.g. POSTED.

No output schema declared.

No examples provided.

universe_list_orders ~149

List the orders of an event: buyer name and email, state, price breakdown, created and updated time. Filter by order state, text match or updated-since time. Contains buyer personal data. Read-only.

NameTypeReqDescription
eventIdstringyesEvent id.
limitinteger–Page size. Default 25, max 100.
matchstring–Text to match (buyer name, email or order reference).
offsetinteger–Number of rows to skip. Default 0.
statesarray–Only orders in these states, e.g. PAID.
updatedSincestring–Only orders updated since this ISO 8601 time.

No output schema declared.

No examples provided.

universe_list_ticket_types ~93

List the ticket types (rates) of an event: name, price, capacity, sold count, state and sales window. Read-only.

NameTypeReqDescription
eventIdstringyesEvent id.
limitinteger–Page size. Default 25, max 100.
offsetinteger–Number of rows to skip. Default 0.
statesarray–Only rates in these states.

No output schema declared.

No examples provided.

universe_list_time_slots ~127

List the dates and time slots of an event (start, end, capacity, tickets sold, state). Optionally filter by start date range (YYYY-MM-DD). Read-only.

NameTypeReqDescription
eventIdstringyesEvent id.
limitinteger–Page size. Default 25, max 100.
offsetinteger–Number of rows to skip. Default 0.
startAfterstring–Only slots that start after this date (YYYY-MM-DD).
startBeforestring–Only slots that start before this date (YYYY-MM-DD).

No output schema declared.

No examples provided.

Install

How do I install the Universe MCP by usefulapi server?

Universe MCP by usefulapi is a hosted endpoint at https://universe.usefulapi.io/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 · universe.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-universe 'https://universe.usefulapi.io/mcp'
Common questions

What is the Universe MCP by usefulapi server?

Universe MCP by usefulapi is listed in the public MCP registry as io.usefulapi/universe. Read events, ticket types, orders, attendees and daily ticket sales in Universe. This page covers its hosted endpoint (https://universe.usefulapi.io/mcp).

Is the Universe MCP by usefulapi server safe to use?

Universe MCP by usefulapi scores 18 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 Universe MCP by usefulapi server expose?

Universe MCP by usefulapi exposes 9 tools: universe_get_viewer, universe_list_events, universe_get_event, universe_list_ticket_types, universe_list_time_slots, and 4 more. Their descriptions and schemas cost roughly 874 tokens of context every time the server is loaded.

Does the Universe MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Universe MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Universe MCP by usefulapi server still maintained?

Universe MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 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 Universe MCP by usefulapi server?

VerifyMCP ran 4 checks on Universe MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Universe MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.