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.

Fitssey MCP by usefulapi

REMOTE · FITSSEY.USEFULAPI.IO

Read Fitssey schedules, class capacity, stock, pass pricing, sales and attendance reports.

−40 this week 18 Trust /100

Last scanned (7 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 6 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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 −44
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.07 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 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.

  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • MCP protocol: fail → pass ▲ functional
    • New prompt “check_studio_product_stock” functional
    • New prompt “compare_pass_offerings” functional
    • New prompt “inspect_recorded_sales” functional
    • New prompt “review_active_passes_and_attendance” functional
    • New prompt “review_upcoming_class_capacity” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.2.0 → 1.4.0 functional
    • Server version: 1.1.0 → 1.2.0 functional
    • Server version: 1.0.2 → 1.1.0 functional
  • 30 Oct 26 58

    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 6 Nov 2026 · Probed https://fitssey.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 fitssey.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://fitssey.usefulapi.io/mcp Redirected 302 https://usefulapi.io/fitssey/
http (plaintext) http://fitssey.usefulapi.io/mcp Inconclusive 302 http://fitssey.usefulapi.io/mcp
MCP tools · 15 exposed · ~847 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
fitssey_get_active_passes_report ~87

Read one page of active client passes with client IDs and validity; cached by Fitssey for five minutes. Interpret remain with sessionType: limitedVisits counts visits, limitedTime counts minutes, and -1 means no session limit. Excludes names and emails. This page is not a full membership total.

NameTypeReqDescription
countinteger––
pageinteger––

No output schema declared.

No examples provided.

fitssey_get_client_visits_report ~83

Read one page of class visits for at most 31 days, with client IDs, pass and payment status. Excludes names, emails and private notes. This page is not a complete attendance total.

NameTypeReqDescription
countinteger––
endDatestringyes–
pageinteger––
startDatestringyes–

No output schema declared.

No examples provided.

fitssey_get_contract ~35

Read one contract’s ID, name and online-sale flag; no payment or bank details.

NameTypeReqDescription
contractstringyes–

No output schema declared.

No examples provided.

fitssey_get_pricing_option ~38

Read one pass offering and its session, expiry and price settings. Excludes private notes.

NameTypeReqDescription
pricingOptionstringyes–

No output schema declared.

No examples provided.

fitssey_get_product ~32

Read one product’s stock, SKU and price. Excludes private notes.

NameTypeReqDescription
productstringyes–

No output schema declared.

No examples provided.

fitssey_get_sales_report ~78

Read one page of sales for at most 31 days, preserving vendor monetary numbers. Excludes customer names, emails, addresses and invoice tax identifiers. This page is not total revenue.

NameTypeReqDescription
countinteger––
endDatestringyes–
pageinteger––
startDatestringyes–

No output schema declared.

No examples provided.

fitssey_get_schedule ~48

Read scheduled classes and remaining capacities for a date range of at most 31 days. No bookings are changed.

NameTypeReqDescription
endDatestringyes–
startDatestringyes–

No output schema declared.

No examples provided.

fitssey_get_schedule_event ~39

Read one scheduled event, capacities and assigned teachers. Excludes livestream URLs, passwords and private notes.

NameTypeReqDescription
scheduleEventstringyes–

No output schema declared.

No examples provided.

fitssey_list_classes ~57

Read one page of the class catalog and categories. Excludes descriptions and private notes.

NameTypeReqDescription
countinteger––
pageinteger––
sortDirstring––
sortFieldstring––

No output schema declared.

No examples provided.

fitssey_list_contracts ~60

Read contract catalog IDs, names and online-sale flags. Excludes private notes and payment details.

NameTypeReqDescription
countinteger––
pageinteger––
sortDirstring––
sortFieldstring––

No output schema declared.

No examples provided.

fitssey_list_courses ~46

Read online-bookable courses and their scheduled sessions for a date range of at most 31 days.

NameTypeReqDescription
endDatestringyes–
startDatestringyes–

No output schema declared.

No examples provided.

fitssey_list_locations ~57

Read studio locations, business addresses and rooms. Excludes entrance instructions and phone details.

NameTypeReqDescription
countinteger––
pageinteger––
sortDirstring––
sortFieldstring––

No output schema declared.

No examples provided.

fitssey_list_pricing_options ~58

Read pass catalog, session allowance and prices in the vendor’s smallest currency unit.

NameTypeReqDescription
countinteger––
pageinteger––
sortDirstring––
sortFieldstring––

No output schema declared.

No examples provided.

fitssey_list_products ~59

Read one page of products with SKU, stock and prices in the vendor’s smallest currency unit.

NameTypeReqDescription
countinteger––
pageinteger––
sortDirstring––
sortFieldstring––

No output schema declared.

No examples provided.

fitssey_list_staff ~70

Read one page of studio staff IDs and names; optionally filter by role. Excludes contact and profile details.

NameTypeReqDescription
countinteger––
iamRolestring––
pageinteger––
sortDirstring––
sortFieldstring––

No output schema declared.

No examples provided.

Install

How do I install the Fitssey MCP by usefulapi server?

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

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

What is the Fitssey MCP by usefulapi server?

Fitssey MCP by usefulapi is listed in the public MCP registry as io.usefulapi/fitssey. Read Fitssey schedules, class capacity, stock, pass pricing, sales and attendance reports. This page covers its hosted endpoint (https://fitssey.usefulapi.io/mcp).

Is the Fitssey MCP by usefulapi server safe to use?

Fitssey 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 Fitssey MCP by usefulapi server expose?

Fitssey MCP by usefulapi exposes 15 tools: fitssey_list_classes, fitssey_list_locations, fitssey_list_staff, fitssey_list_products, fitssey_get_product, and 10 more. Their descriptions and schemas cost roughly 847 tokens of context every time the server is loaded.

Does the Fitssey MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Fitssey 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 Fitssey MCP by usefulapi server still maintained?

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

VerifyMCP ran 4 checks on Fitssey 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 Fitssey 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.