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.

Okapi

REMOTE · MCP.OKAPI.BOT

Breaking changes of third-party APIs: check your code's API calls before they break.

Available components

+53 this week 73 Trust /100

Last scanned (23 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 804 tokens (~134/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 18 Nov 26 +51
    • Authorization: unverified → partial ▲ security
    • HTTPS: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 77 functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 6 Nov 26 20

    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 21 Nov 2026 · Probed https://mcp.okapi.bot/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=okapi.bot CN=WE1,O=Google Trust Services,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 cdad6ac90d49357113864a0d94ef03b0
SANs: okapi.bot, mcp.okapi.bot, *.mcp.okapi.bot
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 mcp.okapi.bot. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
bot. DS published 58741 8 Verified
okapi.bot. No DS 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=31536000; includeSubDomains
content-security-policy default-src 'self';base-uri 'none';font-src 'self' https://fonts.gstatic.com;form-action 'self';frame-ancestors 'none';img-src 'self' data: https://avatars.githubusercontent.com;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;upgrade-insecure-requests;connect-src 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.okapi.bot/mcp Verified 200
http (plaintext) http://mcp.okapi.bot/mcp HTTPS enforced 308 https://mcp.okapi.bot/mcp
MCP tools · 6 exposed · ~656 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
check_calls ~116

Before writing or changing code that calls a third-party API, send the calls (URL, method, models, parameters, version headers, SDK) and get each one's status (broken, at_risk, redirected, deprecated, ok, unknown) with the breaking changes that hit it: what breaks, when, what to migrate to, the provider's source. Works without a key (25 calls, the changes providers announced); a free key adds the ones Okapi inferred and 100 calls a request.

NameTypeReqDescription
callsarrayyes–
NameTypeReqDescription
callsarrayyes–
checkedAtstringyes–
noticestring–Without a key: how many more changes a free key would show.

No examples provided.

get_breaking_change ~93

One breaking change by its id (openai/gpt-4o) or its okapi.bot page URL: its facts, what it targets, the migration. Needs a free API key (Authorization: Bearer okapi_…).

NameTypeReqDescription
idstring–Its id: provider/slug, as search_breaking_changes gives it.
urlstring–Or its page on okapi.bot.
NameTypeReqDescription
announcedAt–––
effectiveAt–––
idstringyesprovider/slug: the end of its okapi.bot page address.
kindstring––
migration–––
model–––
outcomestring––
pagestringyesIts okapi.bot page: link it when you cite the change.
providerobject––
statusstringyes–
summary–––
targetsobject––
titlestringyes–

No examples provided.

get_repository_calls ~116

Every API call Okapi found in one of your repositories at its last scan, each with its file and line, its status and the breaking changes that hit it; the broken and at risk first. Needs a free API key (Authorization: Bearer okapi_…).

NameTypeReqDescription
repositorystringyesowner/name, or its id from list_repositories.
statusstring–Only the calls in this status.
workspacestring–A workspace's id from list_repositories; your personal one when left out.
NameTypeReqDescription
callsarrayyes–
totalinteger––

No examples provided.

list_repositories ~79

Your repositories Okapi reaches through its GitHub App, in a workspace, each with its last scan (status, calls found, providers), and your workspaces. Needs a free API key (Authorization: Bearer okapi_…).

NameTypeReqDescription
workspacestring–A workspace's id from list_repositories; your personal one when left out.
NameTypeReqDescription
repositoriesarrayyes–
workspacesarray––

No examples provided.

search_breaking_changes ~187

The breaking changes 1 to 10 providers announced: those to come (the nearest first), or in effect within a year, with their day, what changes, what to use instead and the okapi.bot page to cite. A provider by its okapi.bot slug: find it with search_providers. 20 a page (50 at most): pass nextCursor back as cursor for the next. Needs a free API key (Authorization: Bearer okapi_…).

NameTypeReqDescription
cursorstring–The nextCursor of the page before.
kindstring––
limitinteger–Changes a page: 20 by default.
providersarrayyesProviders' okapi.bot slugs: openai, anthropic, stripe-api.
whenstring–upcoming (the default), past (in effect within a year) or all.
NameTypeReqDescription
dataarrayyes–
nextCursor–yes–

No examples provided.

search_providers ~65

API providers by name, host or slug (stripe, api.openai.com), each with its okapi.bot slug and how many breaking changes Okapi publishes for it. Needs a free API key (Authorization: Bearer okapi_…).

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
dataarrayyes–

No examples provided.

Install

How do I install the Okapi MCP server?

Okapi is a hosted endpoint at https://mcp.okapi.bot/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 · mcp.okapi.bot

# add to Claude Code
claude mcp add --transport http bot-okapi-okapi 'https://mcp.okapi.bot/mcp'
Common questions

What is the Okapi MCP server?

Okapi is an MCP server listed in the public MCP registry as bot.okapi/okapi. Breaking changes of third-party APIs: check your code's API calls before they break. This page covers its hosted endpoint (https://mcp.okapi.bot/mcp).

Is the Okapi MCP server safe to use?

Okapi scores 73 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 Okapi MCP server expose?

Okapi exposes 6 tools: check_calls, search_breaking_changes, get_breaking_change, search_providers, list_repositories, get_repository_calls. Their descriptions and schemas cost roughly 656 tokens of context every time the server is loaded.

Does the Okapi MCP server require authentication?

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

Is the Okapi MCP server still maintained?

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

VerifyMCP ran 13 checks on Okapi, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.