# Perceptlayer (remote · api.perceptlayer.com)

Live web data for AI agents: structured JSON from 248 websites through one API key.

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

## Components

- remote · `api.perceptlayer.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-perceptlayer-web-data/api.md), [page](https://verifymcp.io/servers/com-perceptlayer-web-data/api)

## Channel facts

- Endpoint: `https://api.perceptlayer.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 584 tokens (~194/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Perceptlayer MCP server?

Perceptlayer is a hosted endpoint at https://api.perceptlayer.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-perceptlayer-web-data 'https://api.perceptlayer.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-perceptlayer-web-data": {
      "url": "https://api.perceptlayer.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-perceptlayer-web-data": {
      "type": "http",
      "url": "https://api.perceptlayer.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-perceptlayer-web-data]
url = "https://api.perceptlayer.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-perceptlayer-web-data": {
      "type": "remote",
      "url": "https://api.perceptlayer.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-perceptlayer-web-data --url 'https://api.perceptlayer.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-perceptlayer-web-data:
    url: "https://api.perceptlayer.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-perceptlayer-web-data": {
      "Transport": "http",
      "Url": "https://api.perceptlayer.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-perceptlayer-web-data -t streamable-http -u 'https://api.perceptlayer.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-perceptlayer-web-data": {
      "type": "http",
      "url": "https://api.perceptlayer.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-05 (score 74, 0)

- [security] Tool “search_endpoints” rewrote its description, which is the text the model reads

### 2026-11-04 (score 74, +1)

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

### 2026-11-01 (score 73, +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-10-30 (score 72, +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-10-28 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 70)

First indexed and scored.

## MCP tools (3)

### `search_endpoints` (~181 tokens)

Search data endpoints

Find Perceptlayer endpoints for a website or kind of data. The catalogue has 1642 endpoints across 248 sources, so search before calling. Query with the site and the data you want, e.g. "amazon product reviews", "airbnb listing", "linkedin company", "google maps places", "zillow property". Returns compact matches: endpoint ID (pass it to get_endpoint or call_endpoint), name, HTTP method, credits per call, tier ("restricted" endpoints need the account's restricted-endpoint terms accepted) and required parameters. Free; no API key needed.

Input parameters:

- `limit` (integer): Maximum results (default 10).
- `query` (string, required): Site and/or data wanted, in a few words, e.g. "tripadvisor hotel reviews".
- `vertical` (string): Optional: only return endpoints in this vertical.

### `get_endpoint` (~88 tokens)

Get endpoint details

Get the full parameter list for one endpoint: each parameter's name, type, whether it is required, allowed values and limits, plus an example set of parameters, the credit cost and tier. Call this before call_endpoint unless you already know the parameters. Free; no API key needed.

Input parameters:

- `endpoint` (string, required): Endpoint ID from search_endpoints, e.g. "airbnb.listing".

### `call_endpoint` (~195 tokens)

Call a data endpoint

Run one endpoint and return its JSON response. Spends the endpoint's credits from the user's balance on success only; failed calls are free. Pass parameters exactly as get_endpoint lists them (array parameters as JSON arrays). The result reports credits used and remaining. Errors come back with a code: invalid_parameters (fix the parameters and retry), not_found (no data for these parameters), rate_limited or temporarily_unavailable (wait and retry), insufficient_credits, restricted_endpoint (the user must accept the restricted-endpoint terms in their dashboard), invalid_api_key (the MCP server config needs a valid API key). Responses over 100,000 characters are truncated; use paging or limit parameters to fetch less.

Input parameters:

- `endpoint` (string, required): Endpoint ID from search_endpoints, e.g. "airbnb.listing".
- `params` (object): Parameters for the endpoint, e.g. {"listing_id": "18648717"}.

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70

## Common questions

### What is the Perceptlayer MCP server?

Perceptlayer is an MCP server listed in the public MCP registry as com.perceptlayer/web-data. Live web data for AI agents: structured JSON from 248 websites through one API key. This page covers its hosted endpoint (https://api.perceptlayer.com/mcp).

### Is the Perceptlayer MCP server safe to use?

Perceptlayer scores 74 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 Perceptlayer MCP server expose?

Perceptlayer exposes 3 tools: search_endpoints, get_endpoint, call_endpoint. Their descriptions and schemas cost roughly 464 tokens of context every time the server is loaded.

### Does the Perceptlayer MCP server require authentication?

No. We connected to Perceptlayer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Perceptlayer MCP server still maintained?

Perceptlayer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.perceptlayer.com/mcp
- Website: https://docs.perceptlayer.com/ai-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-perceptlayer-web-data/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-perceptlayer-web-data/api.json
- HTML version of this page: https://verifymcp.io/servers/com-perceptlayer-web-data/api