Bump to Baby 4D Scans — Pregnancy Ultrasound Studio (Pretoria)
REMOTE · API.BUMPTOBABYSA.CO.ZA · 2 COMPONENTS
2D, Gender Reveal & 4D/5D pregnancy ultrasound packages & live slot availability in Pretoria.
Available components
Last scanned (15 hours ago)
Scores higher than 12% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. 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.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- 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 not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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 →
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.
- 10 Nov 26 27
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 21 Nov 2026 · Probed https://api.bumptobabysa.co.za/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bumptobabysa.co.za | CN=WE1,O=Google Trust Services,C=US | 20 Nov 2026 | 18 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 9f94c4332fd28e410e664c526dcff005 |
| SANs: bumptobabysa.co.za, api.bumptobabysa.co.za | ||||||
| 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 api.bumptobabysa.co.za. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| za. | DS published | 45749 | 8 | Verified |
| co.za. | DS published | 41369 | 8 | Verified |
| bumptobabysa.co.za. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://api.bumptobabysa.co.za/sse | Verified | 200 | |
| http (plaintext) | http://api.bumptobabysa.co.za/sse | HTTPS enforced | 301 | https://api.bumptobabysa.co.za/sse |
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.
How do I install the Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… MCP server?
Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… is a hosted endpoint at https://api.bumptobabysa.co.za/sse, 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.bumptobabysa.co.za
claude mcp add --transport http za-co-bumptobabysa-bumptobaby-mcp 'https://api.bumptobabysa.co.za/sse'
What is the Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… MCP server?
Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… is an MCP server listed in the public MCP registry as za.co.bumptobabysa/bumptobaby-mcp. 2D, Gender Reveal & 4D/5D pregnancy ultrasound packages & live slot availability in Pretoria. This page covers its hosted endpoint (https://api.bumptobabysa.co.za/sse).
Is the Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… MCP server safe to use?
Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… scores 27 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 Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… MCP server require authentication?
No. We connected to Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… MCP server still maintained?
Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… 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 Bump to Baby 4D Scans — Pregnancy Ultrasound Studio… MCP server?
VerifyMCP ran 5 checks on Bump to Baby 4D Scans — Pregnancy Ultrasound Studio…, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Bump to Baby 4D Scans — Pregnancy Ultrasound Studio…: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 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.