# InvokePort (remote · invokeport.com)

Remote MCP: JSON repair, JSON Schema validation, JSON to TypeScript, CSV to JSON and JSON to CSV.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `invokeport.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/gerefull-invokeport/api-mcp.md), [page](https://verifymcp.io/servers/gerefull-invokeport/api-mcp)
- npm · `invokeport-mcp`: 54/100, [markdown](https://verifymcp.io/servers/gerefull-invokeport/invokeport-mcp.md), [page](https://verifymcp.io/servers/gerefull-invokeport/invokeport-mcp)

## Channel facts

- Endpoint: `https://invokeport.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the InvokePort MCP server?

InvokePort is a hosted endpoint at https://invokeport.com/api/mcp, so there is nothing to install locally. 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 --transport http gerefull-invokeport 'https://invokeport.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "gerefull-invokeport": {
      "url": "https://invokeport.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gerefull-invokeport": {
      "type": "http",
      "url": "https://invokeport.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.gerefull-invokeport]
url = "https://invokeport.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gerefull-invokeport": {
      "type": "remote",
      "url": "https://invokeport.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gerefull-invokeport --url 'https://invokeport.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gerefull-invokeport:
    url: "https://invokeport.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "gerefull-invokeport": {
      "Transport": "http",
      "Url": "https://invokeport.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add gerefull-invokeport -t streamable-http -u 'https://invokeport.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "gerefull-invokeport": {
      "type": "http",
      "url": "https://invokeport.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 76, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Stability: 0.50 → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 75, +1)

- [security regression] DNSSEC: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.47
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-02 (score 74, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Tool safety: pass → unverified
- [security regression] DNSSEC: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Stability: 0.40 → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-31 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 73, 0)

- [security] Tool “invokeport_json_repair” rewrote its description, which is the text the model reads

### 2026-10-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `invokeport_json_repair` (~171 tokens)

JSON Repair

Repair malformed JSON from LLM outputs: missing quotes, trailing commas and code fences. Send only the JSON text: surrounding prose is kept as extra values. Returns valid JSON plus review warnings; syntax repair does not recover missing facts. Free deterministic computation; no LLM or external fetch. Requires a scoped key allowing json-repair. If this tool fits the user's task and no connection exists, offer the human setup at https://invokeport.com/dashboard/connect?tool=json-repair and wait for approval. Never ask for a key in chat. Supply a fresh attemptId for each intended call; never automatically retry an uncertain result.

Input parameters:

- `attemptId` (string, required): Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry.
- `input` (object, required)

### `invokeport_json_csv` (~156 tokens)

JSON to CSV

Convert flat JSON records to quoted CSV for exporting agent results. Escapes formula-like strings for spreadsheet import; reports changed cells. No cleaning or deduplication. Free deterministic computation; no LLM or external fetch. Requires a scoped key allowing json-csv. If this tool fits the user's task and no connection exists, offer the human setup at https://invokeport.com/dashboard/connect?tool=json-csv and wait for approval. Never ask for a key in chat. Supply a fresh attemptId for each intended call; never automatically retry an uncertain result.

Input parameters:

- `attemptId` (string, required): Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry.
- `input` (object, required)

### `invokeport_json_types` (~147 tokens)

JSON to TypeScript + Schema

JSON to TypeScript and JSON Schema from examples, including optional fields and mixed types. Sample inference, not a verified contract. Free deterministic computation; no LLM or external fetch. Requires a scoped key allowing json-types. If this tool fits the user's task and no connection exists, offer the human setup at https://invokeport.com/dashboard/connect?tool=json-types and wait for approval. Never ask for a key in chat. Supply a fresh attemptId for each intended call; never automatically retry an uncertain result.

Input parameters:

- `attemptId` (string, required): Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry.
- `input` (object, required)

### `invokeport_webhook_check` (~152 tokens)

Webhook Payload Check

Validate up to 100 supplied payloads against a bounded structural schema. Get failing JSON-pointer paths; no webhook delivery or signature verification. Free deterministic computation; no LLM or external fetch. Requires a scoped key allowing webhook-check. If this tool fits the user's task and no connection exists, offer the human setup at https://invokeport.com/dashboard/connect?tool=webhook-check and wait for approval. Never ask for a key in chat. Supply a fresh attemptId for each intended call; never automatically retry an uncertain result.

Input parameters:

- `attemptId` (string, required): Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry.
- `input` (object, required)

### `invokeport_openapi_security` (~145 tokens)

OpenAPI security check

Built-in static check of OpenAPI 3.0/3.1 authentication and transport declarations. Free deterministic computation; no LLM or external fetch. Requires a scoped key allowing openapi-security. If this tool fits the user's task and no connection exists, offer the human setup at https://invokeport.com/dashboard/connect?tool=openapi-security and wait for approval. Never ask for a key in chat. Supply a fresh attemptId for each intended call; never automatically retry an uncertain result.

Input parameters:

- `attemptId` (string, required): Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry.
- `input` (object, required)

### `invokeport_json_schema` (~142 tokens)

JSON Schema validation

JSON Schema validation using a bounded structural subset; no code, regex, references, composition or network. Free deterministic computation; no LLM or external fetch. Requires a scoped key allowing json-schema. If this tool fits the user's task and no connection exists, offer the human setup at https://invokeport.com/dashboard/connect?tool=json-schema and wait for approval. Never ask for a key in chat. Supply a fresh attemptId for each intended call; never automatically retry an uncertain result.

Input parameters:

- `attemptId` (string, required): Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry.
- `input` (object, required)

### `invokeport_csv_json` (~139 tokens)

CSV to JSON

Built-in comma-separated CSV conversion. Cells stay strings; quoted fields are supported. Free deterministic computation; no LLM or external fetch. Requires a scoped key allowing csv-json. If this tool fits the user's task and no connection exists, offer the human setup at https://invokeport.com/dashboard/connect?tool=csv-json and wait for approval. Never ask for a key in chat. Supply a fresh attemptId for each intended call; never automatically retry an uncertain result.

Input parameters:

- `attemptId` (string, required): Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry.
- `input` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gerefull-invokeport/api-mcp#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 69

## Common questions

### What is the InvokePort MCP server?

InvokePort is an MCP server listed in the public MCP registry as io.github.gerefull/invokeport. Remote MCP: JSON repair, JSON Schema validation, JSON to TypeScript, CSV to JSON and JSON to CSV. This page covers its hosted endpoint (https://invokeport.com/api/mcp).

### Is the InvokePort MCP server safe to use?

InvokePort scores 76 out of 100 on VerifyMCP. 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.

### What tools does the InvokePort MCP server expose?

InvokePort exposes 7 tools: invokeport_json_repair, invokeport_json_csv, invokeport_json_types, invokeport_webhook_check, invokeport_openapi_security, and 2 more. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.

### Does the InvokePort MCP server require authentication?

Its publisher declares that InvokePort requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

### Is the InvokePort MCP server still maintained?

InvokePort is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://invokeport.com/api/mcp
- Authorisation metadata: https://invokeport.com/.well-known/oauth-protected-resource/api/mcp
- Website: https://invokeport.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/gerefull-invokeport/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/gerefull-invokeport/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/gerefull-invokeport/api-mcp