# io.github.bvenkata/mcp-api-connect (pypi · mcp-api-connect)

Protocol- & auth-agnostic API connector: SOAP/REST behind any auth, config-driven. Lib/API/MCP.

- Trust score: 36/100 (low)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `mcp-api-connect`: 36/100 (this document), [markdown](https://verifymcp.io/servers/bvenkata-mcp-api-connect/mcp-api-connect.md), [page](https://verifymcp.io/servers/bvenkata-mcp-api-connect/mcp-api-connect)

## Channel facts

- Registry: `pypi`
- Package: `mcp-api-connect`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 17 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 24 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the io.github.bvenkata/mcp-api-connect server?

io.github.bvenkata/mcp-api-connect runs locally as a PyPI package, launched with uvx mcp-api-connect. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add bvenkata-mcp-api-connect -- uvx mcp-api-connect
```

### Cursor

```json
{
  "mcpServers": {
    "bvenkata-mcp-api-connect": {
      "command": "uvx",
      "args": [
        "mcp-api-connect"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bvenkata-mcp-api-connect": {
      "command": "uvx",
      "args": [
        "mcp-api-connect"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add bvenkata-mcp-api-connect -- uvx mcp-api-connect
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bvenkata-mcp-api-connect": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-api-connect"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bvenkata-mcp-api-connect --command uvx --arg mcp-api-connect
```

### Hermes

```yaml
mcp_servers:
  bvenkata-mcp-api-connect:
    command: "uvx"
    args: ["mcp-api-connect"]
```

### Netclaw

```json
{
  "McpServers": {
    "bvenkata-mcp-api-connect": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-api-connect"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add bvenkata-mcp-api-connect -t stdio -c uvx -a mcp-api-connect
```

### Other

```json
{
  "mcpServers": {
    "bvenkata-mcp-api-connect": {
      "command": "uvx",
      "args": [
        "mcp-api-connect"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-15 (score 36, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 21, −15)

- [security regression] Malware scan: pass → unverified

### 2026-08-28 (score 36, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-27 (score 21)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/bvenkata-mcp-api-connect/mcp-api-connect#diagnostics

## Score history

- 2026-09-21: 36
- 2026-09-20: 36
- 2026-09-19: 36
- 2026-09-18: 36
- 2026-09-17: 36
- 2026-09-16: 36
- 2026-09-15: 36
- 2026-09-14: 21
- 2026-09-13: 36
- 2026-09-12: 36
- 2026-09-11: 36
- 2026-09-10: 36
- 2026-09-09: 36
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36
- 2026-09-02: 36
- 2026-09-01: 36
- 2026-08-31: 36
- 2026-08-30: 36
- 2026-08-29: 36
- 2026-08-28: 36
- 2026-08-27: 21

## Common questions

### What is the io.github.bvenkata/mcp-api-connect server?

io.github.bvenkata/mcp-api-connect is listed in the public MCP registry as io.github.bvenkata/mcp-api-connect. Protocol- & auth-agnostic API connector: SOAP/REST behind any auth, config-driven. Lib/API/MCP. This page covers its PyPI package (mcp-api-connect).

### Is the io.github.bvenkata/mcp-api-connect server safe to use?

io.github.bvenkata/mcp-api-connect scores 36 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### Is the io.github.bvenkata/mcp-api-connect server still maintained?

io.github.bvenkata/mcp-api-connect is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/mcp-api-connect/
- Socket report: https://socket.dev/pypi/package/mcp-api-connect
- Repository: https://github.com/bvenkata/mcp-api-connect
- Changelog RSS feed: https://verifymcp.io/servers/bvenkata-mcp-api-connect/mcp-api-connect.xml
- Changelog JSON feed: https://verifymcp.io/servers/bvenkata-mcp-api-connect/mcp-api-connect.json
- HTML version of this page: https://verifymcp.io/servers/bvenkata-mcp-api-connect/mcp-api-connect