Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Jentic Remote MCP Server

REMOTE · API.JENTIC.COM · SCANNED SEP 20

Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.

Available components

+3 this week 92 Trust /100
Trust breakdown (7 categories)

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 Security89
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1306 tokens (~186/item across 7 items; 4 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Jentic Remote MCP Server server?

Jentic Remote MCP Server is a hosted endpoint at https://api.jentic.com/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 · api.jentic.com

# add to Claude Code
claude mcp add --transport http jentic-mcp-server 'https://api.jentic.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "jentic-mcp-server": {
      "url": "https://api.jentic.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jentic-mcp-server": {
      "type": "http",
      "url": "https://api.jentic.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.jentic-mcp-server]
url = "https://api.jentic.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jentic-mcp-server": {
      "type": "remote",
      "url": "https://api.jentic.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jentic-mcp-server --url 'https://api.jentic.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jentic-mcp-server:
    url: "https://api.jentic.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jentic-mcp-server": {
      "Transport": "http",
      "Url": "https://api.jentic.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add jentic-mcp-server -t streamable-http -u 'https://api.jentic.com/mcp'
// mcp.json
{
  "mcpServers": {
    "jentic-mcp-server": {
      "type": "http",
      "url": "https://api.jentic.com/mcp"
    }
  }
}

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

Changelog

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.

  • 20 Sept 26 0
    • Stability: 0.97 → pass security
  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability rose 1.

  • 7 Sept 26 +1

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

Diagnostics

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 20 Sept 2026 · Probed https://api.jentic.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jentic.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 18 Jul 2026 31 Jan 2027 RSA 2048 SHA256-RSA de3d172d693ae6f01afbeac5c516168
SANs: jentic.com, *.jentic.com
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.jentic.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jentic.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.jentic.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://api.jentic.com/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://api.jentic.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://api.jentic.com
Authorisation server https://api.jentic.com/.well-known/oauth-authorization-server
https://api.jentic.com/.well-known/openid-configuration

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.jentic.com/mcp Verified 200
http (plaintext) http://api.jentic.com/mcp HTTPS enforced
MCP tools · 4 exposed · ~1,048 tokens

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 →

Tool Tokens
execute ~350

Use this tool to execute the chosen action for the user using the provided details. Always include `inputs` even if there are none. To reduce context, use `include_paths` to return only the fields you need from the output. DEPRECATION NOTICE: This tool is being deprecated on 20 September 2026. Execution is moving to self-hosted Jentic One. It still works for now but will stop working on that date. To keep running operations, install Jentic One (https://jentic.com/jentic-one) and execute through its local broker. For a step-by-step install and onboarding guide, fetch the 'skill://onboard-jentic-one' MCP resource. Example operation UUIDs (from search_apis / load_execution_info): NewsAPI.org GET /everything: op_ba86fdce1bade1b7 NewsAPI.org GET /top-headlines: op_8ae297966b7f6da3 Finnhub.io GET /quote: op_f97a5db5e23f7b5a Coincap.io GET /v3/assets/"slug": op_e4a7f50d57fee805

NameTypeReqDescription
paramsobjectyesDictionary containing: - uuid (str, required): The UUID of the operation to execute (e.g., "op_..." or "wf_...") - inputs (dict, required): Input parameters for the execution - include_paths (list[st…

Structured output declared, but exposes no named fields.

No examples provided.

list_credentials ~237

Use this tool to list all API credentials the authenticated agent has access to. Use this if a user asks "What APIs can I use?", "What credentials do I have access to?", "What apps are available to me?", "What APIs are available to me?" This is useful for debugging or to understand what API credentials are available to the agent. DEPRECATION NOTICE: This tool is being deprecated on 20 September 2026. Execution is moving to self-hosted Jentic One. It still works for now but will stop working on that date. See https://jentic.com/jentic-one, or fetch the 'skill://onboard-jentic-one' MCP resource for a step-by-step install and onboarding guide. Returns: dict: Response with success status and list of credentials { "result": { "success": True, "credentials": [c.model_dump(exclude_none=False) for c in credentials], } } On error: { "result": { "success": False, "message": "Failed to load credentials", } }

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

load_execution_info ~301

Use this tool to get the full execution contract for a specific operation (its inputs, outputs, and authentication requirements). This tool must use the operation UUIDs returned from the search_apis tool. DEPRECATION NOTICE: This tool is being deprecated on 20 September 2026. Execution is moving to self-hosted Jentic One. It still works for now but will stop working on that date. To load an operation's contract and run it, install Jentic One (https://jentic.com/jentic-one) and use its `jentic inspect` / `jentic execute` flow. For a step-by-step install and onboarding guide, fetch the 'skill://onboard-jentic-one' MCP resource. Example operation UUIDs (returned from search_apis tool): NewsAPI.org GET /everything: op_ba86fdce1bade1b7 NewsAPI.org GET /top-headlines: op_8ae297966b7f6da3 Finnhub.io GET /quote: op_f97a5db5e23f7b5a Coincap.io GET /v3/assets/"slug": op_e4a7f50d57fee805

NameTypeReqDescription
requestobjectyesDictionary containing: - operation_uuids (list[str] | str): UUID(s) of operation(s) to load (e.g., "op_...")

Structured output declared, but exposes no named fields.

No examples provided.

search_apis ~160

Use this tool to explore for available actions or information based on what the user wants to do (e.g., 'find Discord servers', 'send a message'). Use this to discover what APIs and operations exist in the Jentic catalogue. Execution is moving to self-hosted Jentic One: to run a discovered operation, install Jentic One (https://jentic.com/jentic-one) and use its search -> inspect -> execute flow through the local broker.

NameTypeReqDescription
requestobjectyesDictionary containing search parameters: - query (str, required): Search query string - max_results (int, optional): Maximum number of results to return (default: 5) - api_names (list[str], optional)…

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Jentic Remote MCP Server server?

Jentic Remote MCP Server is listed in the public MCP registry as io.github.jentic/mcp-server. Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute. This page covers its hosted endpoint (https://api.jentic.com/mcp).

Is the Jentic Remote MCP Server server safe to use?

Jentic Remote MCP Server scores 92 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 Jentic Remote MCP Server server expose?

Jentic Remote MCP Server exposes 4 tools: list_credentials, search_apis, load_execution_info, execute. Their descriptions and schemas cost roughly 1,048 tokens of context every time the server is loaded.

Does the Jentic Remote MCP Server server require authentication?

Yes. Jentic Remote MCP Server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Jentic Remote MCP Server server still maintained?

Jentic Remote MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.