# Pentest requests, security headers checker, guides (remote · penetrationtestservices.com)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `penetrationtestservices.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-penetrationtestservices-site/penetrationtestservices.md), [page](https://verifymcp.io/servers/com-penetrationtestservices-site/penetrationtestservices)

## Channel facts

- Endpoint: `https://penetrationtestservices.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-penetrationtestservices-site 'https://penetrationtestservices.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-penetrationtestservices-site": {
      "url": "https://penetrationtestservices.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-penetrationtestservices-site": {
      "type": "http",
      "url": "https://penetrationtestservices.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-penetrationtestservices-site]
url = "https://penetrationtestservices.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-penetrationtestservices-site": {
      "type": "remote",
      "url": "https://penetrationtestservices.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-penetrationtestservices-site --url 'https://penetrationtestservices.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-penetrationtestservices-site:
    url: "https://penetrationtestservices.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-penetrationtestservices-site": {
      "Transport": "http",
      "Url": "https://penetrationtestservices.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-penetrationtestservices-site -t streamable-http -u 'https://penetrationtestservices.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-penetrationtestservices-site": {
      "type": "http",
      "url": "https://penetrationtestservices.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 78, +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.

### 2026-11-18 (score 77, +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.

### 2026-11-16 (score 76, +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.

### 2026-11-14 (score 75, +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.

### 2026-11-12 (score 74, +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.

### 2026-11-11 (score 73, +1)

- [security improvement] DNSSEC: fail → pass

### 2026-11-10 (score 72, +2)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 67% → 100%
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “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”

### 2026-11-09 (score 70)

First indexed and scored.

## MCP tools (5)

### `search_site` (~60 tokens)

Search penetrationtestservices.com

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

Input parameters:

- `limit` (integer): Maximum number of results to return (1 to 20)
- `query` (string, required): Words to search for

### `get_page` (~42 tokens)

Read a page as Markdown

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

Input parameters:

- `path` (string, required): Path starting with /

### `how_to_contact` (~33 tokens)

How to contact Excession Labs

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

### `request_pentest` (~320 tokens)

Request a security test from Excession Labs

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.

Input parameters:

- `authorized` (boolean, required): Must be true: the person owns these systems or may arrange a test of them
- `company` (string): The person's company or organization name
- `email` (string, required): The person's work email; Excession Labs replies here
- `name` (string, required): The person's name
- `notes` (string): Other context from the person, up to 2,000 characters. No credentials or customer data.
- `person_consent` (boolean, required): Must be true: the person asked for this request and agreed to be contacted by email
- `reason` (string): Why the person needs the test
- `targets` (array, required): Systems to test: URLs, API base URLs or short descriptions. No credentials.
- `test_type` (string, required): Kind of test: web_app, api, saas_multi_tenant, ai_application (LLM app or agent) or other
- `timeline` (string): When the person needs the result, in their words
- `website` (string): Company website

### `check_security_headers` (~103 tokens)

Check a website's security headers

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.

Input parameters:

- `url` (string, required): Public http or https address, for example https://example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-penetrationtestservices-site/penetrationtestservices#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 72
- 2026-11-09: 70

## 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.

## Links

- Remote endpoint: https://penetrationtestservices.com/mcp
- Repository: https://github.com/Excession-Labs/mcp-servers
- Website: https://penetrationtestservices.com/developers/
- Changelog RSS feed: https://verifymcp.io/servers/com-penetrationtestservices-site/penetrationtestservices.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-penetrationtestservices-site/penetrationtestservices/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-penetrationtestservices-site/penetrationtestservices.json
- HTML version of this page: https://verifymcp.io/servers/com-penetrationtestservices-site/penetrationtestservices
