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.

JillionDB

REMOTE · JILLIONDB.COM

Review your AI agent's database changes on your schema, with plain-language risk, before they run.

Available components

0 this week 36 Trust /100

Last scanned (15 hours ago)

Scores higher than 19% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Databases

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 & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 36

    First indexed and scored.

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 21 Nov 2026 · Probed https://jilliondb.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jilliondb.com CN=SSL.com TLS Issuing RSA CA R1,O=SSL Corporation,C=US 9 Nov 2026 26 May 2027 RSA 2048 SHA256-RSA 7d99d38aac58bbab4a6d47f98455d29b
SANs: jilliondb.com, www.jilliondb.com
CN=SSL.com TLS Issuing RSA CA R1,O=SSL Corporation,C=US (CA) CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US 21 Oct 2022 18 Oct 2032 RSA 3072 SHA256-RSA 26b9ffe4596fa61e1af21c63d672748a
CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US (CA) CN=SecureTrust CA,O=SecureTrust Corporation,C=US 17 Dec 2025 30 Dec 2029 RSA 4096 SHA256-RSA 7eb4274fc1d305be94c9883277f8467e2144f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of jilliondb.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
jilliondb.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer realm="jilliondb"

Bearer realm="jilliondb"
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()
www-authenticate Bearer realm="jilliondb"

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jilliondb.com/mcp Auth required 401
http (plaintext) http://jilliondb.com/mcp HTTPS enforced 301 https://jilliondb.com/mcp
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the JillionDB MCP server?

JillionDB is a hosted endpoint at https://jilliondb.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 · jilliondb.com

# add to Claude Code
claude mcp add --transport http com-jilliondb-jilliondb 'https://jilliondb.com/mcp'
Common questions

What is the JillionDB MCP server?

JillionDB is an MCP server listed in the public MCP registry as com.jilliondb/jilliondb. Review your AI agent's database changes on your schema, with plain-language risk, before they run. This page covers its hosted endpoint (https://jilliondb.com/mcp).

Is the JillionDB MCP server safe to use?

JillionDB scores 36 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.

Does the JillionDB MCP server require authentication?

Yes. JillionDB 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 JillionDB MCP server still maintained?

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

What did VerifyMCP test on the JillionDB MCP server?

VerifyMCP ran 5 checks on JillionDB, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about JillionDB: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.