mcpbeat Sign in

Invokera Discover MCP Server

answering

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

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

Uptime history 49 days of history · worst day 93%
49 days agonow
95.6%
Uptime 24h
87 of 91 checks
3
Tools
read from the server
323 ms
Response time
average over 24h
open, no key
Access
streamable-http

Invokera Discover does not always answer

Over the last week it answered 98.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add discover --transport http https://invokera.com/discover
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "discover": {
      "url": "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
{
  "mcpServers": {
    "discover": {
      "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

URLTransportStateLatencyChecked
https://invokera.com/discover streamable-http answering 216 ms 5 min ago

Alternatives to Invokera Discover

same job, measured the same way
Apiosk Connect
by obcraft

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

83 installs/wk 3 tools answering
Crabeye MCP Bridge
by crabeye-ai

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

30 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
Directory
by anots

Discover and query every business on ANOTS — search, ask, or find-and-ask over MCP.

3 tools answering
dylog
by imjakezimmer32

Notes, files, GitHub, and Drive through one MCP connection.

answering
BizClaw Business Directory MCP
by bizclaw

Search, compare, and contact real-world companies through a public MCP business directory.

9 tools answering
Recall
by imjakezimmer32

Notes, files, GitHub, and Drive through one MCP connection.

answering
PPN Hub — public APIs over MCP
by ppn-hub

One MCP endpoint over 69 public PPN APIs: search_apis to discover, execute_api to call. Free tier.

3 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 87 of 91 checks got a reply (95.6%), average response time 323 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 with the file path 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 323 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.