# Jensing (remote · jensing.com)

Public facts about Jensing: its companies and how it helps businesses free up time with AI.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `jensing.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-jensing-jensing/jensing.md), [page](https://verifymcp.io/servers/com-jensing-jensing/jensing)

## Channel facts

- Endpoint: `https://jensing.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 41/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 475 tokens (~19/item across 24 items; 5 tools + 19 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

Jensing is a hosted endpoint at https://jensing.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.

### Claude

```bash
claude mcp add --transport http com-jensing-jensing 'https://jensing.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-jensing-jensing": {
      "url": "https://jensing.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-jensing-jensing]
url = "https://jensing.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-jensing-jensing:
    url: "https://jensing.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-jensing-jensing": {
      "type": "http",
      "url": "https://jensing.com/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 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-04 (score 67)

First indexed and scored.

## MCP tools (5)

### `search_knowledge` (~83 tokens)

Search the knowledge base

Find answers about Jensing: who it helps, which problems it solves, how to get started, cost and funding, who approves the work, what it has built, why it started. Searches by meaning, so ask in plain words, in any language.

Input parameters:

- `language` (string): Language of the answer.
- `query` (string, required): A question or keywords.

### `get_article` (~42 tokens)

Read a knowledge base article

Read one article in full, by the id search_knowledge returned.

Input parameters:

- `id` (string, required): Article id.
- `language` (string): Language of the answer.

### `list_companies` (~48 tokens)

List the companies

List the companies on jensing.com, with industry, stage and a one-line description.

Input parameters:

- `industry` (string): Only this industry.
- `language` (string): Language of the answer.

### `get_company` (~41 tokens)

Read about a company

Read about one company, by the slug list_companies returned.

Input parameters:

- `language` (string): Language of the answer.
- `slug` (string, required): Company slug.

### `how_to_contact` (~43 tokens)

How to contact Jensing

Get the email address, the enquiry form and who answers. For when the user wants to talk to Jensing.

Input parameters:

- `language` (string): Language of the answer.

## Diagnostics

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

## Score history

- 2026-11-05: 68
- 2026-11-04: 67

## Common questions

### What is the Jensing MCP server?

Jensing is an MCP server listed in the public MCP registry as com.jensing/jensing. Public facts about Jensing: its companies and how it helps businesses free up time with AI. This page covers its hosted endpoint (https://jensing.com/mcp).

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

Jensing scores 68 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 Jensing MCP server expose?

Jensing exposes 5 tools: search_knowledge, get_article, list_companies, get_company, how_to_contact. Their descriptions and schemas cost roughly 257 tokens of context every time the server is loaded.

### Does the Jensing MCP server require authentication?

No. We connected to Jensing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Jensing MCP server still maintained?

Jensing is still listed as active in the MCP registry. We last reached this channel on 5 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://jensing.com/mcp
- Website: https://jensing.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-jensing-jensing/jensing.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jensing-jensing/jensing.json
- HTML version of this page: https://verifymcp.io/servers/com-jensing-jensing/jensing