Skip to main content
Glama
invenio-mcp

invenio-mcp

by kiandevs
README.md
# invenio-mcp

MCP server for [Invenio](https://invenio.cc). Connects Claude Desktop, Cursor and other MCP clients to Invenio APIs (email risk, fraud checks, OSINT search).

## Setup

```bash
git clone https://github.com/kiandevs/invenio-mcp.git
cd invenio-mcp
npm install
```

### Claude Desktop

Add to `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "invenio": {
      "command": "node",
      "args": ["<PATH_TO_REPO>/dist/index.js"],
      "env": {
        "INVENIO_API_KEY": "your_api_key_here"
      }
    }
  }
}
```

### Cursor

Add to `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "invenio": {
      "command": "node",
      "args": ["<PATH_TO_REPO>/dist/index.js"],
      "env": {
        "INVENIO_API_KEY": "your_api_key_here"
      }
    }
  }
}
```

## Tools

- `invenio_check_email_risk` - Check email disposable status, MX records, gibberish score and fraud risk.
- `invenio_create_search_task` - Run OSINT search (user, email, phone).
- `invenio_get_search_task` - Fetch search results.
- `invenio_get_account_status` - Check current quota and plan.

## Env

- `INVENIO_API_KEY` (required) - API key from invenio.cc/dashboard/security.
- `INVENIO_BASE_URL` (optional) - Default `https://invenio.cc`.

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a clearly distinct action: checking email risk, creating an OSINT search task, retrieving search results, and checking account status. There is no overlap between the email-risk tool and the async search lifecycle tools, and the two get_* tools operate on clearly different resources.

Naming Consistency5/5

All tool names follow a consistent invenio_ prefix plus verb_noun pattern: check_email_risk, create_search_task, get_search_task, get_account_status. The convention is predictable and readable.

Tool Count5/5

Four tools is well-scoped for a focused OSINT/email-risk API wrapper. Each tool corresponds to a real operation and none appear redundant or filler.

Completeness4/5

The core workflows are covered: submit an OSINT search, poll for its results, run an email-risk check, and inspect remaining account limits. Minor gaps exist, such as listing or cancelling search tasks and possibly batch email checks, but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo issues