# Traffic Parrot (remote · mcp.trafficparrot.com)

Traffic Parrot simulates APIs and messaging. Request or withdraw a trial, read docs, send feedback.

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

## Components

- remote · `mcp.trafficparrot.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-trafficparrot-public/mcp.md), [page](https://verifymcp.io/servers/com-trafficparrot-public/mcp)

## Channel facts

- Endpoint: `https://mcp.trafficparrot.com/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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**: 63/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 (delete_trial_request).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1499 tokens (~187/item across 8 items; 6 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 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 (67% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 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 Traffic Parrot MCP server?

Traffic Parrot is a hosted endpoint at https://mcp.trafficparrot.com/, 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-trafficparrot-public 'https://mcp.trafficparrot.com/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-trafficparrot-public": {
      "url": "https://mcp.trafficparrot.com/"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-trafficparrot-public]
url = "https://mcp.trafficparrot.com/"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-trafficparrot-public:
    url: "https://mcp.trafficparrot.com/"
```

### Netclaw

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

### Vellum

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

### Other

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

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 81, +1)

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

### 2026-11-02 (score 80, +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-10-31 (score 79, +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-10-29 (score 78, +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-27 (score 77, +1)

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

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

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

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

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

### 2026-10-21 (score 74, +1)

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

## MCP tools (6)

### `request_trial` (~700 tokens)

Request a Traffic Parrot trial

Request a Traffic Parrot trial on behalf of the human you are working for.

Traffic Parrot is a commercial service-virtualization tool (HTTP, gRPC, JMS/IBM MQ,
RabbitMQ, ActiveMQ, AMQP, file transfers). Use this when your user wants to evaluate it.

IMPORTANT: this submits a real person's personal data (their business email, and
optionally their name, company and phone number) to Traffic Parrot. Only call it when
your user has asked for a trial and has agreed to be contacted. Do not invent an email
address.

The trial is issued under Traffic Parrot's evaluation agreement: https://trafficparrot.com/documentation/Traffic_Parrot_Software_Evaluation_Agreement_v1.4.pdf
Show it to your user and ask them to approve it before you call this tool.

Lawful basis: Legitimate interests (UK GDPR Article 6(1)(f)): responding to a request to evaluate our product, made on your behalf by a tool you were using. You can object at any time and we will erase the request.
Retention: A request nobody acts on is erased 168 hours after it is made. A request a person at Traffic Parrot has approved or rejected is kept for 365 days, then erased. We keep approved ones so we can answer questions about a trial that was issued, and rejected ones so we have a record of the decision, for example if the person writes in to ask why.
Privacy notice: https://trial.trafficparrot.com/privacy
Your user can withdraw the request at any time via the delete_trial_request tool.

As soon as you call this tool, your user's details go to Mailchimp (Traffic Parrot's
US-based email service) and the address you give is sent one email asking them to
confirm they want the trial. Confirming adds them to Traffic Parrot's trial mailing list
and sends a second email carrying the link to their trial status page. Ignoring the
first email sends nothing further.

A person at Traffic Parrot approves each request during UK working hours. It is not
instant: outside those hours expect the next working day. Once approved, the trial…

Input parameters:

- `agentClient` (string): Which agent or client is making this call, e.g. 'Claude Code', 'Cursor'.
- `company` (string): Company evaluating Traffic Parrot.
- `email` (string, required): Business email of the human this trial is for. Required. This is a real person's personal data.
- `humanInTheLoop` (boolean): Whether a human is present in the session and has asked for this trial.
- `name` (string): Name of the human this trial is for.
- `phone` (string): Contact phone number, if your user offers one. Optional, and personal data.
- `problem` (string): What they are trying to solve. Free text. This is the most useful field for the sales conversation.
- `protocols` (array): Which protocols will be evaluated.

Output parameters:

- `requestId` (string): The trial request's id. get_trial_status and delete_trial_request take it.
- `state` (string): The request's state, as get_trial_status reports it.

### `submit_feature_request` (~131 tokens)

Send Traffic Parrot a feature request

Send a feature request or product feedback to the Traffic Parrot team.
Use this when your user wants something Traffic Parrot does not currently do.
If you include a contact email it is a real person's personal data, so only include
one your user has agreed to share.

Input parameters:

- `agentClient` (string): Which agent or client is making this call.
- `detail` (string, required): What the feature should do and why it is needed.
- `email` (string): Contact email, if the user is willing to share one. Optional.
- `title` (string, required): One-line summary of the requested feature.

Output parameters:

- `sent` (boolean): The feature request was sent to the Traffic Parrot team.

### `delete_trial_request` (~101 tokens)

Withdraw a trial request

Withdraw a trial request and erase the personal data submitted with it.
Use this if your user changes their mind, or asks you to remove their details.
You must supply the email the request was made for, so one caller cannot erase
another's request.

Input parameters:

- `email` (string, required): The email the request was made for. Must match, so one caller cannot erase another's request.
- `requestId` (string, required): The request id returned by request_trial.

Output parameters:

- `requestId` (string): The withdrawn request's id. Present only when withdrawn is true.
- `withdrawn` (boolean): Whether a request was withdrawn and its personal data erased. False when no request matches that id and email.

### `get_trial_status` (~93 tokens)

Check the status of a trial request

Check the state of a trial request: waiting for approval, being prepared, ready, or
unavailable. Pass the request id that request_trial returned.
The reply is the state only, never a link: the trial link goes only to the email
address on the request. Once it is ready, tell your user to check that inbox.

Input parameters:

- `requestId` (string, required): The request id returned by request_trial.

Output parameters:

- `found` (boolean): Whether a trial request matches that id.
- `requestId` (string): The request id asked about.
- `state` (string): The request's state. Present only when found is true.

### `get_documentation` (~83 tokens)

Read the Traffic Parrot documentation

Read Traffic Parrot's product overview and documentation index (llms.txt), written
for agents. Use it to judge whether Traffic Parrot fits your user's problem and to
find the reference page for a protocol or feature.
It assumes Traffic Parrot is already running. To start it from the trial download and
create a first mock, call get_trial_onboarding.

### `get_trial_onboarding` (~90 tokens)

Get a Traffic Parrot trial running

How to get Traffic Parrot running from the trial download: the ports it uses, how to
start and stop it on each operating system, where the licence goes, and how to create
a first mock for each protocol (HTTP, gRPC, IBM MQ, JMS, file transfers, Thrift).
Call this once your user has the download, or earlier to tell them what to expect.

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 76
- 2026-10-25: 76
- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 71
- 2026-10-14: 71
- 2026-10-13: 70
- 2026-10-12: 70
- 2026-10-10: 69
- 2026-10-08: 68

## Common questions

### What is the Traffic Parrot MCP server?

Traffic Parrot is an MCP server listed in the public MCP registry as com.trafficparrot/public. Traffic Parrot simulates APIs and messaging. Request or withdraw a trial, read docs, send feedback. This page covers its hosted endpoint (https://mcp.trafficparrot.com/).

### Is the Traffic Parrot MCP server safe to use?

Traffic Parrot scores 81 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 Traffic Parrot MCP server expose?

Traffic Parrot exposes 6 tools: request_trial, submit_feature_request, delete_trial_request, get_trial_status, get_documentation, get_trial_onboarding. Their descriptions and schemas cost roughly 1,198 tokens of context every time the server is loaded.

### Does the Traffic Parrot MCP server require authentication?

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

### Is the Traffic Parrot MCP server still maintained?

Traffic Parrot 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://mcp.trafficparrot.com/
- Repository: https://github.com/trafficparrot/trafficparrot-mcp-public
- Website: https://trafficparrot.com/ai/agent-trial.html
- Changelog RSS feed: https://verifymcp.io/servers/com-trafficparrot-public/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-trafficparrot-public/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-trafficparrot-public/mcp