Jensing
REMOTE · JENSING.COM
Public facts about Jensing: its companies and how it helps businesses free up time with AI.
Available components
Last scanned (1 day ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category AI and Machine Learning
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability41
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 475 tokens (~19/item across 24 items; 5 tools + 19 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
- 4 Nov 26 67
First indexed and scored.
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 4 Nov 2026 · Probed https://jensing.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jensing.com | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6830c36378151a2513c81e4ebfba68a7 |
| SANs: jensing.com, brand-backup.jensing.com, *.brand-backup.jensing.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jensing.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jensing.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://connect.facebook.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://www.googletagmanager.com https://*.google-analytics.com https://*.google.com https://*.doubleclick.net https://www.facebook.com; font-src 'self'; connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://*.google.com https://*.doubleclick.net https://www.facebook.com; frame-src https://www.googletagmanager.com https://www.facebook.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jensing.com/mcp | Verified | 200 | |
| http (plaintext) | http://jensing.com/mcp | HTTPS enforced | 301 | https://jensing.com/mcp |
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 →
get_article Read a knowledge base article ~42
Read one article in full, by the id search_knowledge returned.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Article id. |
| language | string | – | Language of the answer. |
No output schema declared.
No examples provided.
get_company Read about a company ~41
Read about one company, by the slug list_companies returned.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the answer. |
| slug | string | yes | Company slug. |
No output schema declared.
No examples provided.
how_to_contact How to contact Jensing ~43
Get the email address, the enquiry form and who answers. For when the user wants to talk to Jensing.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the answer. |
No output schema declared.
No examples provided.
list_companies List the companies ~48
List the companies on jensing.com, with industry, stage and a one-line description.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | Only this industry. |
| language | string | – | Language of the answer. |
No output schema declared.
No examples provided.
search_knowledge Search the knowledge base ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the answer. |
| query | string | yes | A question or keywords. |
No output schema declared.
No examples provided.
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.
remote · jensing.com
claude mcp add --transport http com-jensing-jensing 'https://jensing.com/mcp'
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 67 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.