Invokera Discover MCP Server

by invokera Your server? Claim it

answering

Invokera Discover is answering right now. Last checked 2 min ago. It exposes 3 tools.

Search, inspect and invoke every public tool on Invokera through one MCP connection.

Uptime history 91 days of history · worst day 93%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

313 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Invokera Discover every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add discover --transport http https://invokera.com/discover

Settings → Connectors → Add custom connector, then paste this address

https://invokera.com/discover

~/.codex/config.toml

[mcp_servers.discover]
url = "https://invokera.com/discover"

.cursor/mcp.json

{
  "mcpServers": {
    "discover": {
      "url": "https://invokera.com/discover"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "discover": {
      "type": "http",
      "url": "https://invokera.com/discover"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

describe

describe_tool

Get the full input schema and calling instructions for one tool found via search_tools. Returns the JSON Schema plus the exact REST/MCP endpoint to call it on. Calling a tool requires that project's own endpoint token, obtained from its owner.

invoke

invoke_tool

Call a tool whose owner has enabled public invocation, without needing that project's token. Only works for tools opted in by their owner; others return not-found (use describe_tool for how to call them with a token). Usage is metered to the tool owner. Get project_slug/tool_name and the argument schema from search_tools + describe_tool first.

tools

search_tools

Search the Invokera catalog for published tools across all projects. Returns a ranked list of tools (name, project, summary, category) WITHOUT their input schemas. Call describe_tool next to get the full schema and calling instructions for a specific tool.

Endpoints

URL	Transport	State	Latency	Checked
https://invokera.com/discover	streamable-http	answering	273 ms	2 min ago

Alternatives to Invokera Discover

same job, measured the same way

SkillDash

by ajnasnb

Search and inspect source-pinned agent skills, plugins and tools through a free public MCP.

6 tools answering

OpenAPI Swagger MCP

by nhan7777

Discover, preview, call, and inspect configured Swagger/OpenAPI APIs through 11 fixed tools.

371 installs/wk local only

Apiosk Connect

by obcraft

Discover, pay for, execute, and publish APIs through Apiosk.

144 installs/wk 3 tools answering

Crabeye MCP Bridge

by crabeye-ai

One MCP connection for all your tools — with discovery, namespacing, and execution policies.

194 installs/wk local only

Noodle Biomedical Literature Discovery MCP

by helena-bioinformatics

Search biomedical papers, inspect publication records, and traverse citation or semantic graphs.

7 tools answering

Invokera Discover — questions

Answers built from our own checks of this server.

What can Invokera Discover do?

It exposes 3 tools, read directly from the server on our last check. Among them: describe_tool, invoke_tool, search_tools. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Invokera Discover working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 313 ms. The bar chart above shows every period we have measured.

How do I connect Invokera Discover?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Invokera Discover need an API key?

No. Invokera Discover completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Invokera Discover?

It answers our handshake in 313 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.