Perceptlayer

com.perceptlayerPublished by perceptlayer.comOfficial publisherv1.1.0Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Perceptlayer gives an assistant structured JSON web data from about 250 sites through one API key, via search, parameter lookup and paid endpoint calls.

What you can do
  • Search a catalogue of 1659 endpoints across 248 sources by site and data type
  • Read one endpoint's full parameter list, example parameters, credit cost and tier
  • Run an endpoint and get its JSON response, with credits used and remaining reported
When to use it
Useful when an assistant needs live structured data from marketplaces, travel, real estate, cars, jobs, search engines, reviews, social networks, apps or SEO sources, and you would rather pay per call than build scrapers.
Requirements
Remote streamable HTTP endpoint at api.perceptlayer.com; no local package. A Perceptlayer API key is needed for call_endpoint, sent as an Authorization Bearer token or X-API-Key header. Search and parameter lookup work without a key. A credit balance is required for paid calls.
Before you install
call_endpoint spends credits from your balance on each successful call; failed calls are free. The API key is a live secret passed in the Authorization header, so keep it out of shared configs. Calls send your queries and parameters to a third-party service.

Installation

In SourceWeft

  1. Open Perceptlayer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.perceptlayer%2Fweb-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "perceptlayer": {
      "type": "http",
      "url": "https://api.perceptlayer.com/mcp"
    }
  }
}

Tools

3

search_endpoints

Search data endpoints

Find Perceptlayer endpoints for a website or kind of data. The catalogue has 1659 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.

Parameterslimitqueryrequiredvertical

get_endpoint

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.

Parametersendpointrequired

call_endpoint

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.

Parametersparamsendpointrequired

Version history

1
  1. v1.1.0LatestOct 29, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.