Lie Detector Test
REMOTE · LIEDETECTORTEST.COM · SCANNED SEP 24
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 → 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 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 Usability80
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Lie Detector Test MCP server?
Lie Detector Test is a hosted endpoint at https://liedetectortest.com/wp-json/ldt-mcp/v1/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 · liedetectortest.com
claude mcp add --transport http com-liedetectortest-lie-detector-test 'https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp'
{
"mcpServers": {
"com-liedetectortest-lie-detector-test": {
"url": "https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp"
}
}
} {
"servers": {
"com-liedetectortest-lie-detector-test": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp"
}
}
} assistant mcp add com-liedetectortest-lie-detector-test -t streamable-http -u '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.
- 31 Aug 26 0
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 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
- 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 0
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 24 Sept 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 | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ec9e50c5538e6e481348b698cf06ba54 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. 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 →
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 £225 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.
What is the Lie Detector Test MCP server?
Lie Detector Test is an MCP server listed in the public MCP registry as com.liedetectortest/lie-detector-test. Find polygraph (lie detector) offices, pricing and service info across the US, Canada and the UK. This page covers its hosted endpoint (https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp).
Is the Lie Detector Test MCP server safe to use?
Lie Detector Test scores 79 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 Lie Detector Test MCP server expose?
Lie Detector Test exposes 5 tools: find_offices, get_pricing, get_service_info, start_booking, get_booking_status. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.
Does the Lie Detector Test MCP server require authentication?
No. We connected to Lie Detector Test without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lie Detector Test MCP server still maintained?
Lie Detector Test is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.