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.

Pentest requests, security headers checker, guides

REMOTE · PENETRATIONTESTSERVICES.COM

Request a penetration test, grade a website's HTTP security headers, and search pentest guides.

+3 this week 78 Trust /100

Last scanned (20 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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 Security77
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 620 tokens (~124/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 Management40
  • Stability observed for 12 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 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.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 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.

  • 11 Nov 26 +1
    • DNSSEC: fail → pass ▲ security
  • 10 Nov 26 +2
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 67% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • “request_pentest” reworded the description of “company” cosmetic
    • “request_pentest” reworded the description of “notes” cosmetic
    • “request_pentest” reworded the description of “reason” cosmetic
    • “request_pentest” reworded the description of “test_type” cosmetic
    • “search_site” reworded the description of “limit” cosmetic
  • 9 Nov 26 70

    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://penetrationtestservices.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=penetrationtestservices.com CN=WE1,O=Google Trust Services,C=US 9 Nov 2026 7 Feb 2027 ECDSA 256 ECDSA-SHA256 68ee29fb42d004a0e60ad9bc73eec94
SANs: penetrationtestservices.com, www.penetrationtestservices.com, *.www.penetrationtestservices.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 secure

Validation of penetrationtestservices.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
penetrationtestservices.com. DS published 2371 13 Verified
penetrationtestservices.com. Verified address RRset verified with the apex keys
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
streamable-http https://penetrationtestservices.com/mcp Verified 200
http (plaintext) http://penetrationtestservices.com/mcp HTTPS enforced 301 https://penetrationtestservices.com/mcp
MCP tools · 5 exposed · ~558 tokens

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 →

Tool Tokens
check_security_headers ~103

Fetch one public web page (one GET per redirect, like a browser visit) and grade its HTTP security headers: HTTPS, HSTS, Content-Security-Policy, clickjacking protection, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, version disclosure and cookie flags. Reads headers only. This is not a penetration test.

NameTypeReqDescription
urlstringyesPublic http or https address, for example https://example.com

No output schema declared.

No examples provided.

get_page ~42

Return the Markdown text of a page on penetrationtestservices.com, given its path (for example /guides/).

NameTypeReqDescription
pathstringyesPath starting with /

No output schema declared.

No examples provided.

how_to_contact ~33

Return the form URL and email address a person can use to contact Excession Labs. This tool does not send anything.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_pentest ~320

Send a request for a penetration test or an AI application security assessment to Excession Labs on behalf of a person who asked for it. Needs an agent key (POST /agent/auth, then Authorization: Bearer <key>). Excession Labs replies to the person by email to agree scope; testing starts only after a written scope and written authorization from the system owner. Never include passwords, API keys or customer data. Limits: 5 requests a day per key, 3 a day per email address.

NameTypeReqDescription
authorizedbooleanyesMust be true: the person owns these systems or may arrange a test of them
companystring–The person's company or organization name
emailstringyesThe person's work email; Excession Labs replies here
namestringyesThe person's name
notesstring–Other context from the person, up to 2,000 characters. No credentials or customer data.
person_consentbooleanyesMust be true: the person asked for this request and agreed to be contacted by email
reasonstring–Why the person needs the test
targetsarrayyesSystems to test: URLs, API base URLs or short descriptions. No credentials.
test_typestringyesKind of test: web_app, api, saas_multi_tenant, ai_application (LLM app or agent) or other
timelinestring–When the person needs the result, in their words
websitestring–Company website

No output schema declared.

No examples provided.

search_site ~60

Search the guides, service pages and research on penetrationtestservices.com. Returns titles, URLs and one-line summaries.

NameTypeReqDescription
limitinteger–Maximum number of results to return (1 to 20)
querystringyesWords to search for

No output schema declared.

No examples provided.

Install

How do I install the Pentest requests, security headers checker, guides MCP server?

Pentest requests, security headers checker, guides is a hosted endpoint at https://penetrationtestservices.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 · penetrationtestservices.com

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

What is the Pentest requests, security headers checker, guides MCP server?

Pentest requests, security headers checker, guides is an MCP server listed in the public MCP registry as com.penetrationtestservices/site. Request a penetration test, grade a website's HTTP security headers, and search pentest guides. This page covers its hosted endpoint (https://penetrationtestservices.com/mcp).

Is the Pentest requests, security headers checker, guides MCP server safe to use?

Pentest requests, security headers checker, guides scores 78 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 Pentest requests, security headers checker, guides MCP server expose?

Pentest requests, security headers checker, guides exposes 5 tools: search_site, get_page, how_to_contact, request_pentest, check_security_headers. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.

Does the Pentest requests, security headers checker, guides MCP server require authentication?

No. We connected to Pentest requests, security headers checker, guides without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Pentest requests, security headers checker, guides MCP server still maintained?

Pentest requests, security headers checker, guides 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 Pentest requests, security headers checker, guides MCP server?

VerifyMCP ran 13 checks on Pentest requests, security headers checker, guides, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.