# AgentPixel (remote · agentpixel.io)

Most visitors never fill out a form. Turn the ones who click Accept into contacts your agent reads.

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

## Components

- remote · `agentpixel.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/io-agentpixel-agentpixel/agentpixel.md), [page](https://verifymcp.io/servers/io-agentpixel-agentpixel/agentpixel)

## Channel facts

- Endpoint: `https://agentpixel.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.4`

## 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**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (configure_consent).
  - 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**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2547 tokens (~181/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 15 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 AgentPixel MCP server?

AgentPixel is a hosted endpoint at https://agentpixel.io/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 io-agentpixel-agentpixel 'https://agentpixel.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-agentpixel-agentpixel": {
      "url": "https://agentpixel.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-agentpixel-agentpixel": {
      "type": "http",
      "url": "https://agentpixel.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-agentpixel-agentpixel]
url = "https://agentpixel.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-agentpixel-agentpixel --url 'https://agentpixel.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-agentpixel-agentpixel:
    url: "https://agentpixel.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-agentpixel-agentpixel": {
      "Transport": "http",
      "Url": "https://agentpixel.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-agentpixel-agentpixel -t streamable-http -u 'https://agentpixel.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-agentpixel-agentpixel": {
      "type": "http",
      "url": "https://agentpixel.io/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 75, +1)

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

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

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 72, +1)

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

### 2026-10-27 (score 71, +1)

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

### 2026-10-25 (score 70, +1)

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

### 2026-10-23 (score 69, +1)

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

### 2026-10-21 (score 68, +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.

## MCP tools (14)

### `try_sample` (~62 tokens)

See sample output

Labeled sample of what an account gets: a pixel, a consent receipt and two contacts.

        Needs no account and no key. Every record is synthetic and marked so.
        Call this first to show the person what AgentPixel returns, then call signup_free.

Output parameters:

- `consent_receipt` (object)
- `contacts` (array)
- `next_step` (string)
- `note` (string)
- `pixel` (object)
- `synthetic` (boolean)

### `signup_free` (~216 tokens)

Start 30-day trial

Start a 30-day trial, no card. After that, $1 per account per month for 3 pixels and 500 new contacts per UTC calendar month.

        Sends a 6-digit code to the email address. Returns account_id and signup_token; keep both.
        Next: ask the person for the 6-digit code in the AgentPixel email, then call confirm_signup(account_id, code, signup_token).
        The signup_token lasts 24 hours.

Input parameters:

- `code`: Optional trial code from a directory or listing, such as SMITHERY60. An unknown code never blocks signup. Example: GLAMA60
- `display_name` (string, required): Name shown on the account, such as the person's name or the business name. 1 to 200 characters. Example: Pat Lee
- `email` (string, required): Email address of the person who will own the account. The 6-digit code is sent here. Ask the person for it; never invent or guess an address. Example: pat@example.com

Output parameters:

- `account_id` (string)
- `email_verified` (boolean)
- `plan` (string)
- `signup_token` (string)
- `status` (string)

### `confirm_signup` (~278 tokens)

Confirm signup email

Confirm the email with the 6-digit code, or check whether the email link was clicked.

        Preferred: confirm_signup(account_id, code, signup_token). The first confirmation returns api_key; store it, it is shown once.
        Link clicked instead: call confirm_signup(account_id, signup_token) every 5 seconds, up to 10 minutes, until email_verified is true, then call create_api_key.
        A code allows 5 attempts and lasts 24 hours. For a new code, call resend_code(email).

Input parameters:

- `account_id`: account_id returned by signup_free. Use with code, or with signup_token alone to check whether the email link was clicked. Example: 3f1c2b9e-1d2a-4c5b-9e8f-0a1b2c3d4e5f
- `code`: The 6-digit code from the AgentPixel email. Ask the person to read it to you. Example: 482913
- `signup_token`: signup_token returned by signup_free. With code, the first confirmation also returns the API key. Alone with account_id, returns whether the email is confirmed.
- `verification_token`: Older method: the token value from the confirmation link URL (?token=...). Prefer account_id and code.

Output parameters:

- `confirmed` (boolean)
- `message` (string)

### `resend_code` (~119 tokens)

Send a new email code

Send a new 6-digit code to the email of an existing account.

        Use it when the code expired, was lost or was entered wrong 5 times. Limits: 1 per minute, 5 per day.
        The old code stops working. With an expired signup_token, use the new code on POST /v1/accounts/{account_id}/signup-token to get a new token.

Input parameters:

- `email` (string, required): Email address used at signup. A new 6-digit code and link are sent there. Example: pat@example.com

Output parameters:

- `sent` (boolean)

### `create_api_key` (~132 tokens)

Issue private API key

Issue an API key after the email is confirmed.

        Not needed when confirm_signup already returned api_key. Each call issues another key, so call it once.
        Returns the key once. Store it securely and attach it to the connection.

Input parameters:

- `account_id` (string, required): account_id returned by signup_free. Example: 3f1c2b9e-1d2a-4c5b-9e8f-0a1b2c3d4e5f
- `signup_token` (string, required): signup_token returned by signup_free. It lasts 24 hours.

Output parameters:

- `api_key` (string)
- `prefix` (string)

### `whoami` (~83 tokens)

Check account identity

Which account this connection's API key belongs to.

        status is the account state after email confirmation. plan is "free" (the trial plan id) during the 30-day trial,
        paid after the subscription, or unlimited for internal accounts. trial_ends_at is when the trial ends.
        key_prefix is the start of the key, not the key.

Output parameters:

- `account_id` (string)
- `data_kind` (string)
- `evaluation_expires_at`
- `evaluation_install_url`
- `evaluation_mode` (boolean)
- `key_prefix` (string)
- `next_action` (string)
- `paid_until`
- `plan` (string)
- `resolution_state` (string)
- `status` (string)
- `trial_ends_at`

### `setup_status` (~54 tokens)

Read installation progress

Whether this account can use pixels and whether a tag is installed.

        setup_complete is true once at least one pixel's tag has been seen on
        its site. good_standing is the account, not the tag.

Output parameters:

- `good_standing` (boolean)
- `installed_count` (integer)
- `pixel_count` (integer)
- `setup_complete` (boolean)

### `list_pixels` (~25 tokens)

List my pixels

Pixels on this account. Each item has pixel_id, domain, and install_status.

Output parameters:

- `pixels` (array)

### `create_pixel` (~103 tokens)

Create site pixel

Create a pixel for a domain.

        Does not create an API key. The account must already be active.
        Next: call configure_consent(pixel_id, controller_name, purposes) and install the snippet it returns.
        Do not install a snippet before consent is configured. install_status starts as not_checked until check_install runs.

Input parameters:

- `domain` (string, required): Public hostname of the site, without scheme, port, path or IP address. Example: shop.example.com

Output parameters:

- `check_error`
- `checked_at`
- `consent_enabled`
- `data_kind` (string)
- `domain` (string)
- `evaluation_mode` (boolean)
- `install_status` (string)
- `pixel_id` (string)
- `snippet`

### `get_pixel` (~64 tokens)

Read pixel and install tag

One pixel, including the HTML snippet to paste on its site.

Input parameters:

- `pixel_id` (string, required): pixel_id returned by create_pixel or list_pixels, never an account_id. Example: px_7a1b2c3d4e5f6a7b

Output parameters:

- `check_error`
- `checked_at`
- `consent_enabled`
- `data_kind` (string)
- `domain` (string)
- `evaluation_mode` (boolean)
- `install_status` (string)
- `pixel_id` (string)
- `snippet`

### `check_install` (~109 tokens)

Check and save installation

Fetch the pixel's homepage and store whether the tag is there.

        install_status becomes installed or not_installed. check_error says
        why a check could not decide. Evaluator accounts fetch only the fixed
        https://staging.allsourcedata.io/evaluation-test/ page and reject redirects.

Input parameters:

- `pixel_id` (string, required): pixel_id of the pixel whose homepage to check. Example: px_7a1b2c3d4e5f6a7b

Output parameters:

- `check_error`
- `checked_at`
- `consent_enabled`
- `data_kind` (string)
- `domain` (string)
- `evaluation_mode` (boolean)
- `install_status` (string)
- `pixel_id` (string)
- `snippet`

### `configure_consent` (~468 tokens)

Configure consent and policy

Turn on and set up the consent bar for a pixel.

        Changing any setting makes a new policy version, and returning visitors are asked again.
        Returns the policy link and the script tag to put on the site.

Input parameters:

- `contact_channels`: Optional. How the site owner may contact a visitor who consents. Any of: email, phone, sms, agentic. Example: ["email"]
- `controller_contact`: Optional. Email address or web address where visitors can reach the site owner about their data. Shown in the hosted notice. Example: privacy@example.com
- `controller_jurisdiction`: Optional. Where the site owner is based, as plain text, such as a country or US state. Shown in the hosted notice. Example: Florida, USA
- `controller_name` (string, required): Name of the business or person that owns the site. It is shown in the consent bar as the party asking the visitor for permission. 1 to 200 characters. Example: Example Shop LLC
- `controller_type`: Optional. One of company, person or organization. Describes the site owner in the hosted notice. Example: company
- `data_sharing`: Optional. true if the site owner shares consented contact data with other parties, false if not. Shown in the hosted notice. Example: false
- `disclosed_parties`: Optional. Names of the other parties the site owner wants the hosted notice to list, one name per item. Example: ["Example CRM Inc."]
- `pixel_id` (string, required): pixel_id of the pixel to configure. Example: px_7a1b2c3d4e5f6a7b
- `purposes` (array, required): What the consent bar asks the visitor to allow. One or more of: analytics, resolution, newsletter, email_sharing, phone_sharing, partner_email, partner_calls, partner_sms. Include resolution, or no v…
- `site_policy_url`: Optional. HTTPS address of the site's own privacy policy. The bar links to it, and the hosted notice becomes a short add-on about identification. Leave empty to use the hosted notice on its own. Exam…

Output parameters:

- `consent_enabled` (boolean)
- `pixel_id` (string)
- `policy_hash` (string)
- `policy_url` (string)
- `policy_version` (integer)
- `purposes` (array)
- `snippet` (string)

### `get_policy` (~68 tokens)

Read hosted privacy notice

Hosted privacy and data-use policy HTML for a pixel.

        A pixel with consent turned off has no policy yet.

Input parameters:

- `pixel_id` (string, required): pixel_id whose hosted notice to read. Example: px_7a1b2c3d4e5f6a7b

Output parameters:

- `pixel_id` (string)
- `policy_html` (string)

### `get_contacts` (~189 tokens)

Read contacts

Contacts for one pixel.

        Pass on as a UTC day, or after as the high_water from the previous pull. Use high_water as the next cursor.
        New contacts can arrive between reads. This does not identify new visitors.
        Evaluation returns labeled synthetic examples only after current resolution consent is saved; withdrawal hides them.

Input parameters:

- `after`: Cursor for incremental reads: the high_water value from your previous pull, or 0 to start at the first stored contact. Use exactly one of on or after. Example: 0
- `on`: UTC calendar date in YYYY-MM-DD form. Returns contacts stored on that day. Use exactly one of on or after. Example: 2026-10-12
- `pixel_id` (string, required): pixel_id whose contacts to read. Example: px_7a1b2c3d4e5f6a7b

Output parameters:

- `after`
- `contacts` (array)
- `data_kind`
- `evaluation_mode`
- `high_water`
- `on`
- `pixel_id` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 69
- 2026-10-23: 69
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 67
- 2026-10-19: 67
- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 65
- 2026-10-13: 64
- 2026-10-12: 64
- 2026-10-10: 62

## Common questions

### What is the AgentPixel MCP server?

AgentPixel is an MCP server listed in the public MCP registry as io.agentpixel/agentpixel. Most visitors never fill out a form. Turn the ones who click Accept into contacts your agent reads. This page covers its hosted endpoint (https://agentpixel.io/mcp).

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

AgentPixel scores 75 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 AgentPixel MCP server expose?

AgentPixel exposes 14 tools: try_sample, signup_free, confirm_signup, resend_code, create_api_key, and 9 more. Their descriptions and schemas cost roughly 1,970 tokens of context every time the server is loaded.

### Does the AgentPixel MCP server require authentication?

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

### Is the AgentPixel MCP server still maintained?

AgentPixel 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://agentpixel.io/mcp
- Repository: https://github.com/byron-allsourcedata/agentpixel-mcp
- Website: https://agentpixel.io/connect
- Changelog RSS feed: https://verifymcp.io/servers/io-agentpixel-agentpixel/agentpixel.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-agentpixel-agentpixel/agentpixel.json
- HTML version of this page: https://verifymcp.io/servers/io-agentpixel-agentpixel/agentpixel