InvokePort
REMOTE · INVOKEPORT.COM · 2 COMPONENTS
Remote MCP: JSON repair, JSON Schema validation, JSON to TypeScript, CSV to JSON and JSON to CSV.
Available components
Last scanned (34 minutes ago)
Scores higher than 66% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Nov 26 +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.
- 3 Nov 26 +1
- DNSSEC: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.47 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 2 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- DNSSEC: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.40 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Oct 26 +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.
- 30 Oct 26 0
- Tool “invokeport_json_repair” rewrote its description, which is the text the model reads security
- 29 Oct 26 +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.
- 27 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://invokeport.com/api/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of invokeport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| invokeport.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://invokeport.com/api/mcp | Unreachable | ||
| http (plaintext) | http://invokeport.com/api/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
invokeport_csv_json CSV to JSON ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attemptId | string | yes | Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry. |
| input | object | yes | – |
No output schema declared.
No examples provided.
invokeport_json_csv JSON to CSV ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attemptId | string | yes | Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry. |
| input | object | yes | – |
No output schema declared.
No examples provided.
invokeport_json_repair JSON Repair ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attemptId | string | yes | Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry. |
| input | object | yes | – |
No output schema declared.
No examples provided.
invokeport_json_schema JSON Schema validation ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attemptId | string | yes | Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry. |
| input | object | yes | – |
No output schema declared.
No examples provided.
invokeport_json_types JSON to TypeScript + Schema ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attemptId | string | yes | Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry. |
| input | object | yes | – |
No output schema declared.
No examples provided.
invokeport_openapi_security OpenAPI security check ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attemptId | string | yes | Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry. |
| input | object | yes | – |
No output schema declared.
No examples provided.
invokeport_webhook_check Webhook Payload Check ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attemptId | string | yes | Unique non-secret invocation ID. Retain on uncertain outcomes; do not invent a new ID to retry. |
| input | object | yes | – |
No output schema declared.
No examples provided.
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.
remote · invokeport.com
claude mcp add --transport http gerefull-invokeport 'https://invokeport.com/api/mcp'
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.