---
title: "Our work: a published MCP server, no clients yet | Invokary"
description: "What we have built so far: our own read-only MCP server, its tests, where it is listed and what it does not show yet. Client case studies come later."
canonical: "https://invokary.com/work"
dateModified: "2026-10-08"
---

# What we have built so far

## What has Invokary built so far?

Invokary has no client case studies yet. What we can show is our own MCP server: six read-only tools on the current MCP spec, checked in CI against the five positive and three negative test cases a ChatGPT submission asks for, and listed in Claude's Connectors Directory and the official MCP Registry. Its code is public, so you can read every line.

## What we built

A remote MCP server that answers what Claude, ChatGPT, Cursor and the MCP Registry require before they list a connector. It runs on Cloudflare Workers, speaks MCP 2026-07-28 without sessions, and still serves clients that open with the 2025 handshake.

- **Endpoint**: https://mcp.invokary.com/mcp
- **Tools**: list\_platforms, get\_platform\_requirements, get\_requirement, compare\_platforms, search\_requirements, list\_platform\_changes
- **Annotations**: Every tool has a title and is marked read-only, non-destructive, idempotent and closed-world.
- **Sign-in**: None. It reads public data only.
- **License**: MIT

- [Connect to the server](https://invokary.com/open-source)
- [Read the code on GitHub](https://github.com/Invokary/platform-requirements-mcp)
- [See its MCP Registry record](https://registry.modelcontextprotocol.io/v0.1/servers/com.invokary%2Fplatform-requirements/versions/latest)

## How it's checked

A ChatGPT submission asks for exactly five prompts the server should answer and three it shouldn't. Ours run in CI on every change: each of the five calls its tool, for both current and 2025-style clients, and must return the requirements it names. The three negative prompts go into the submission as written.

## Where it's listed

We submit to each directory from our own accounts, the way we submit a client's connector from theirs. Each row changes when a submission does.

*Where the server is listed, and when*

| Official MCP Registry | [Listed](https://registry.modelcontextprotocol.io/v0.1/servers/com.invokary%2Fplatform-requirements/versions/latest) · · October 5, 2026 |
| --- | --- |
| Claude Connectors Directory | [Listed](https://claude.ai/new#customize/connectors/id/invokary-platform-requirements) · · October 7, 2026 |
| ChatGPT Plugins Directory | Not submitted yet |
| Cursor Marketplace | Not submitted yet |

## What this doesn't show yet

The server has no sign-in, so it doesn't show OAuth or Client ID Metadata Documents. Its tests check that each tool answers correctly, not that a model picks the right tool from everything in its context. A client connector needs both, and our first client case study will show them, with the client's approval.

## Find out where you stand in five days.

$750. Credited in full to your build.

[Book a $750 Audit](https://invokary.com/book)