Traffic Parrot
REMOTE · MCP.TRAFFICPARROT.COM
Traffic Parrot simulates APIs and messaging. Request or withdraw a trial, read docs, send feedback.
Available components
Last scanned (22 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Testing and QA
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_trial_request). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 18 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.trafficparrot.com/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.trafficparrot.com | CN=WR3,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | f5dcebc9e20c88d80af6f99c036f6259 |
| SANs: mcp.trafficparrot.com, trial.trafficparrot.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.trafficparrot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| trafficparrot.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.trafficparrot.com/ | Verified | 200 | |
| http (plaintext) | http://mcp.trafficparrot.com/ | HTTPS enforced | 301 | https://mcp.trafficparrot.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
delete_trial_request Withdraw a trial request ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email the request was made for. Must match, so one caller cannot erase another's request. | |
| requestId | string | yes | The request id returned by request_trial. |
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | – | The withdrawn request's id. Present only when withdrawn is true. |
| withdrawn | boolean | yes | Whether a request was withdrawn and its personal data erased. False when no request matches that id and email. |
No examples provided.
get_documentation Read the Traffic Parrot documentation ~83
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trial_onboarding Get a Traffic Parrot trial running ~90
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trial_status Check the status of a trial request ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | The request id returned by request_trial. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | Whether a trial request matches that id. |
| requestId | string | yes | The request id asked about. |
| state | string | – | The request's state. Present only when found is true. |
No examples provided.
request_trial Request a Traffic Parrot trial ~700
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…
| Name | Type | Req | Description |
|---|---|---|---|
| agentClient | string | – | Which agent or client is making this call, e.g. 'Claude Code', 'Cursor'. |
| company | string | – | Company evaluating Traffic Parrot. |
| string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | The trial request's id. get_trial_status and delete_trial_request take it. |
| state | string | yes | The request's state, as get_trial_status reports it. |
No examples provided.
submit_feature_request Send Traffic Parrot a feature request ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentClient | string | – | Which agent or client is making this call. |
| detail | string | yes | What the feature should do and why it is needed. |
| string | – | Contact email, if the user is willing to share one. Optional. | |
| title | string | yes | One-line summary of the requested feature. |
| Name | Type | Req | Description |
|---|---|---|---|
| sent | boolean | yes | The feature request was sent to the Traffic Parrot team. |
No examples provided.
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.
remote · mcp.trafficparrot.com
claude mcp add --transport http com-trafficparrot-public 'https://mcp.trafficparrot.com/'
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 80 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.