Invokary: MCP server, CLI and agent surfaces

Yes: Invokary runs a public MCP server at mcp.invokary.com that listed 6 tools to a client with no credentials on 4 November 2026. Examples: list_platforms, get_platform_requirements, get_requirement. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool.

Fact sheet

Company	Invokary (registry title: Invokary Platform Requirements)
Domain	invokary.com
Category	Communication & Support (assigned by this directory from the registry description)
MCP server	Verified (No authentication)
Ora score	none: Ora returned no cached score for invokary.com when asked on 5 November 2026
Company found through	the GitHub MCP Registry; the official MCP Registry
Last verified	4 November 2026

MCP server

Endpoint	`https://mcp.invokary.com/mcp`
How it was found	listed in the GitHub MCP Registry; the official MCP Registry
Transport	streamable-http
HTTP status	200
Protocol version	2025-11-25
Server	platform-requirements 1.0.0
Capabilities	tools
Tools	6
Resources	0
Prompts	0
Connected	4 November 2026, 20:03 UTC
Handshake time	197 ms over 1 attempt

Tools listed

6 tools

list_platforms
get_platform_requirements
get_requirement
compare_platforms
search_requirements
list_platform_changes

Connector log

2 connections on 4 November 2026, read-only methods only

19:57:59Z https://mcp.invokary.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 532 ms
20:03:19Z https://mcp.invokary.com/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 197 ms

Authentication

Auth type	No authentication

The sign-in route, step by step

Send the handshake to https://mcp.invokary.com/mcp over streamable-http. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
Send tools/list, then resources/list and prompts/list if the capabilities name them.
Send no token. The connector sent none and the server answered, so any MCP client can read this list.
Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Invokary. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
Surface	Result
OpenAPI file	No OpenAPI file at the root paths checked.
WebMCP in the initial HTML	Not checked: the home page was not read by the shared crawl.
MCP discovery file	Not checked: the domain is not in the shared crawl for this edition.
A2A agent card	Not checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)	Not checked: the domain is not in the shared crawl for this edition.
agents.json	Not checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadata	Not checked: the domain is not in the shared crawl for this edition.
NLWeb endpoint	Not checked in this edition.

Registry listings

Registry listings
Registry	Listed
Official MCP Registry	Yes: com.invokary/platform-requirements
GitHub MCP Registry	Yes
awesome-remote-mcp-servers	No
Smithery	Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
Glama	Not checked: Glama's API needs a key and attribution terms.