Invokera Discover

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
97%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~478Tokens (tool definitions)
~1005 BTypical response size
Minimal attention impact (0.37% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://invokera.com/discoverstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_tools(query, category, limit)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Keywords, e.g. \"housing price\" or \"stock signal\". Empty lists popular tools."
    },
    "category": {
      "type": "string",
      "description": "Optional category filter.",
      "enum": [
        "other",
        "data",
        "commerce",
        "productivity",
        "social",
        "finance"
      ]
    },
    "limit": {
      "type": "integer",
      "description": "Max results, 1-25 (default 10).",
      "minimum": 1,
      "maximum": 25
    }
  }
}
🟢describe_tool(project_slug, tool_name)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "project_slug": {
      "type": "string",
      "description": "The projectSlug from a search_tools result."
    },
    "tool_name": {
      "type": "string",
      "description": "The toolName from a search_tools result."
    }
  },
  "required": [
    "project_slug",
    "tool_name"
  ]
}
🟢invoke_tool(project_slug, tool_name, arguments)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "project_slug": {
      "type": "string",
      "description": "The projectSlug from a search_tools result."
    },
    "tool_name": {
      "type": "string",
      "description": "The toolName from a search_tools result."
    },
    "arguments": {
      "type": "object",
      "description": "Arguments matching the tool inputSchema from describe_tool."
    }
  },
  "required": [
    "project_slug",
    "tool_name"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools