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.

Scorekeeper

REMOTE · WWW.SCOREKEEPER.CO

Create live scoreboards, connect with OAuth, and prepare checkout or Stripe CLI payments.

−10 this week 65 Trust /100

Last scanned (23 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Entertainment and Games

Recent critical change

Authorization (29 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 Security63
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1053 tokens (~95/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability check failed: schema churn in the 7 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 6 additions. See how to fix → Fail
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (91% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.

  • 29 Oct 26 −12
    • Authorization: pass → fail ▼ critical
    • Stability: unverified → fail ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 100% → 91% ▼ functional
    • Schema quality: 78 → 95 ▼ functional
    • Schema quality: 392 → 765 ▼ functional
    • Tool coverage: 100% → 89% ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.1.0 → 1.2.0 functional
    • Server version: 1.0.0 → 1.1.0 functional
    • New tool “create_payment_order” functional
    • New tool “get_payment_order” functional
    • New tool “create_checkout” functional
    • New tool “get_account” functional
    • New tool “get_checkout” functional
    • New tool “get_service_info” functional
  • 28 Oct 26 75

    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 4 Nov 2026 · Probed https://www.scorekeeper.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.scorekeeper.co CN=YR1,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 RSA 2048 SHA256-RSA 5d2beb7c5883f5622e8ed094da45a5ea08f
SANs: *.scorekeeper.co, scorekeeper.co
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.scorekeeper.co. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
scorekeeper.co. 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
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.scorekeeper.co/api/mcp Verified 200
http (plaintext) http://www.scorekeeper.co/api/mcp HTTPS enforced 308 https://www.scorekeeper.co/api/mcp
MCP tools · 11 exposed · ~812 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_checkout ~120

Create a private Stripe checkout for a current offer after the user expresses purchase intent. Explain price, duration and annual renewal before proceeding. This tool does not charge a card: give checkoutUrl privately to the buyer for payment authorization. Reuse the exact requestId/input after uncertainty; never create a replacement checkout to retry. Pro and Studio passes accept months=1–12 and never auto-renew; annual offers are recurring. Requires billing:checkout.

NameTypeReqDescription
monthsinteger––
offerIdstringyes–
requestIdstringyes–
NameTypeReqDescription
amountCentsintegeryes–
checkoutStatusstringyes–
checkoutUrlstring|nullyes–
currencystringyes–
fulfillmentStatusstringyes–
idstringyes–
monthsintegeryes–
offerIdstringyes–
paymentStatusstringyes–

No examples provided.

create_payment_order ~135

Prepare an owner-bound one-time payment order after purchase intent, only when get_service_info pricing.paymentMethods.stripe_cli_pay.available is true. Returns the exact @scorekeeper recipient, USD amount and unique memo for stripe pay. Supports pro_week, pro and studio (1–12 calendar months), never annual subscriptions. This tool sends no money. Separately obtain authorization for the actual Stripe transfer and payer-selected funding account. Reuse identical requestId/input on retry; never pay twice or send without the returned memo.

NameTypeReqDescription
monthsinteger––
offerIdstringyes–
requestIdstringyes–
NameTypeReqDescription
accessExpiresAtnumber|nullyes–
amountCentsintegeryes–
createdAtnumberyes–
currencystringyes–
expiresAtnumberyes–
fulfillmentStatusstringyes–
idstringyes–
instructions–yes–
monthsintegeryes–
nextActionstringyes–
offerIdstringyes–
orderStatusstringyes–
paymentStatusstringyes–
pollAfterSecondsintegeryes–
referencestringyes–

No examples provided.

create_scoreboard ~80

Create a public, shareable two-team scoreboard at zero. Requires explicit user intent to create; title and team names are public. Free boards allow 50 total spectator views and show branding. Retry the identical requestId and input after a timeout.

NameTypeReqDescription
requestIdstringyes–
teamsarrayyes–
titlestringyes–
NameTypeReqDescription
capabilitiesarrayyes–
idstringyes–
limitsobjectyes–
linksobjectyes–
revisionstringyes–
teamsarrayyes–
titlestringyes–

No examples provided.

get_account ~45

Read only the connected account's current plan, expiry, board capacity and permissions. Call before offering a paid upgrade. Requires explicit billing:read permission; returns no personal or payment details.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_checkout ~66

Read the connected account's checkout by its returned opaque id. Only fulfillmentStatus=fulfilled confirms webhook-granted access; paid/completed alone is insufficient. Poll no more often than every 15 seconds. Return to the requested scoreboard task once access is granted.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
amountCentsintegeryes–
checkoutStatusstringyes–
checkoutUrlstring|nullyes–
currencystringyes–
fulfillmentStatusstringyes–
idstringyes–
monthsintegeryes–
offerIdstringyes–
paymentStatusstringyes–

No examples provided.

get_payment_order ~97

Check only the connected account's payment order and reconcile a bank receipt. May activate access after matching verified received funds. Only fulfillmentStatus=fulfilled confirms access; CLI output or sender status does not. Poll no more often than pollAfterSeconds (at least 60 seconds). Bank transfers can take business days. Never send a replacement payment while pending. review_required or reversed needs support reconciliation, not another payment.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
accessExpiresAtnumber|nullyes–
amountCentsintegeryes–
createdAtnumberyes–
currencystringyes–
expiresAtnumberyes–
fulfillmentStatusstringyes–
idstringyes–
instructions–yes–
monthsintegeryes–
nextActionstringyes–
offerIdstringyes–
orderStatusstringyes–
paymentStatusstringyes–
pollAfterSecondsintegeryes–
referencestringyes–

No examples provided.

get_scoreboard ~36

Read a scoreboard created through this API by the connected account, including stable team IDs and current revision.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
capabilitiesarrayyes–
idstringyes–
limitsobjectyes–
linksobjectyes–
revisionstringyes–
teamsarrayyes–
titlestringyes–

No examples provided.

get_service_info ~50

Start here to discover Scorekeeper's MCP/OAuth and guest REST onboarding, supported scoreboard operations, free limits, current prices and payment steps. Public; no account or authentication needed. Does not create anything.

Input schema present but exposes no named parameters.

NameTypeReqDescription
namestringyes–
publisherstringyes–
versionstringyes–

No examples provided.

hand_off_scoreboard ~58

Return the connected account owner’s private management link. Share it only with the intended scorer, never spectators. Does not transfer ownership. Reuse requestId on retry.

NameTypeReqDescription
idstringyes–
requestIdstringyes–
NameTypeReqDescription
expiresAtnumber|nullyes–
transfersOwnershipbooleanyes–
urlstringyes–

No examples provided.

list_scoreboards ~58

List the connected account's API-created generic scoreboards. Does not list unrelated legacy boards. Pass nextCursor as cursor to continue until null; a filtered page can be empty.

NameTypeReqDescription
cursorstring––
limitinteger––
NameTypeReqDescription
nextCursorstring|nullyes–
scoreboardsarrayyes–

No examples provided.

update_scoreboard ~67

Atomically set exact scores, increment scores, rename teams or change title. Use stable team IDs and the last read revision. Updates immediately appear publicly. On revision_conflict read the board and decide again; do not blindly replay a stale increment. Identical retry IDs return the previous result.

Input schema present but exposes no named parameters.

NameTypeReqDescription
capabilitiesarrayyes–
idstringyes–
limitsobjectyes–
linksobjectyes–
revisionstringyes–
teamsarrayyes–
titlestringyes–

No examples provided.

Install

How do I install the Scorekeeper MCP server?

Scorekeeper is a hosted endpoint at https://www.scorekeeper.co/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 · www.scorekeeper.co

# add to Claude Code
claude mcp add --transport http co-scorekeeper-scorekeeper 'https://www.scorekeeper.co/api/mcp'
Common questions

What is the Scorekeeper MCP server?

Scorekeeper is an MCP server listed in the public MCP registry as co.scorekeeper/scorekeeper. Create live scoreboards, connect with OAuth, and prepare checkout or Stripe CLI payments. This page covers its hosted endpoint (https://www.scorekeeper.co/api/mcp).

Is the Scorekeeper MCP server safe to use?

Scorekeeper scores 65 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 Scorekeeper MCP server expose?

Scorekeeper exposes 11 tools: get_service_info, get_account, create_checkout, get_checkout, create_payment_order, and 6 more. Their descriptions and schemas cost roughly 812 tokens of context every time the server is loaded.

Does the Scorekeeper MCP server require authentication?

No. We connected to Scorekeeper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Scorekeeper MCP server still maintained?

Scorekeeper is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.