Lie Detector Test
REMOTE · LIEDETECTORTEST.COM · SCANNED AUG 3
Find polygraph (lie detector) offices, pricing and service info across the US, Canada and the UK.
Available components
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 →
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 call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 670 tokens (~134/item across 5 items; 5 tools + 0 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · liedetectortest.com
claude mcp add --transport http com-liedetectortest-lie-detector-test https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp
[mcp_servers.com-liedetectortest-lie-detector-test] url = "https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-liedetectortest-lie-detector-test": {
"type": "remote",
"url": "https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-liedetectortest-lie-detector-test --url https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp --transport streamable-http
mcp_servers:
com-liedetectortest-lie-detector-test:
url: "https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp" {
"mcpServers": {
"com-liedetectortest-lie-detector-test": {
"type": "http",
"url": "https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
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 3 Aug 2026 · Probed https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=liedetectortest.com | CN=WE1,O=Google Trust Services,C=US | 2 Jul 2026 | 30 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | c63068985728e0f213f383b9f75d1903 |
| SANs: liedetectortest.com, *.liedetectortest.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 |
DNSSEC insecure
Validation of liedetectortest.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| liedetectortest.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 |
|---|---|
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp | Verified | 200 | |
| http (plaintext) | http://liedetectortest.com/wp-json/ldt-mcp/v1/mcp | HTTPS enforced | 301 | https://liedetectortest.com/wp-json/ldt-mcp/v1/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.
find_offices ~109
Find lie detector (polygraph) test offices near a place. Search by city, state/region, or country (United States, Canada, or United Kingdom). Returns each matching office with its address, all-inclusive prices, and a booking link.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Maximum offices to return (1-50, default 15). |
| query | string | yes | A city, state/region, or country, e.g. "Miami", "Florida", "London", "Ontario". |
No output schema declared.
No examples provided.
get_booking_status ~82
Check the status of an existing confirmed booking by its reference (e.g. LDT-2026072062783). Returns the booking status and location. A booking started via start_booking is not confirmed until the person completes payment on the website.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_reference | string | yes | The booking reference, e.g. "LDT-2026072062783". |
No output schema declared.
No examples provided.
get_pricing ~105
Get polygraph examination pricing for a location. Returns the all-inclusive price tiers (single person, couple/two-person total, and group per-examinee) plus the non-refundable booking-fee deposit (fully refunded if we cannot accept your case or arrange your appointment) ($100 USD/CAD, or £150 in the UK).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A city, state/region, or country, e.g. "Miami", "Texas", "United Kingdom". |
No output schema declared.
No examples provided.
get_service_info ~47
Get general information about the lie detector test service: what is offered, how booking works, the deposit and refund policy, the service area, and what happens after booking. Takes no arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_booking ~268
Start a lie detector test booking for a person. Records the enquiry and returns a reference plus a ready-to-complete booking link with the office pre-filled. IMPORTANT: the person must finish on the website themselves — choose a time, accept the terms, sign the agreement, pay the non-refundable deposit (fully refunded if we cannot book you), and complete a short pre-examination assessment. An agent cannot sign or pay on their behalf. Do not put the person's contact details in any URL.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Contact email address. | |
| location | string | yes | City, state/region or country for the test, e.g. "Miami", "Florida", "London". |
| name | string | yes | Full name of the person to be tested (or the person booking). |
| phone | string | — | Contact phone number (optional but recommended). |
| preferred_dates | string | — | Preferred date(s)/time(s), free text, e.g. "Aug 5 afternoon or Aug 8 morning" (optional). |
| reason | string | — | Short reason/type of test, e.g. "infidelity", "employment", "legal" (optional). |
| service_type | string | yes | One of: single (one person), couple (two people), or group (three or more). |
No output schema declared.
No examples provided.