# Traffic Parrot > Traffic Parrot simulates APIs and messaging. Request or withdraw a trial, read docs, send feedback. - name: com.trafficparrot/public - version: 1.0.1 - connection class: R0 (autonomous) - trust: 100/100 - quality: 85/100 (good) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/com.trafficparrot%2Fpublic - tools: https://api.protogrid.dev/v1/servers/com.trafficparrot%2Fpublic/tools **An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe. ## Connection (mcpServers) ```json { "mcpServers": { "public": { "type": "http", "url": "https://mcp.trafficparrot.com/" } } } ``` ## Trust - hygiene: 100 - liveness: 100 - freshness: 100 - provenance: 100 - drivers: +repository +namespace-matches-repo +dns-namespace +website +reachable +uptime-100% +updated-14d-ago - Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. ## Quality 85/100 (good) ### protocol: 75 (weight 25) - warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28 - n/a `protocol.stateless`: only applies to 2026-07-28 servers - pass `protocol.transport`: streamable HTTP - n/a `protocol.list_ttl`: only applies to 2026-07-28 servers ### authorization: n/a (weight 15) - n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 86 (weight 30) - pass `tools.descriptions`: every tool has a description - warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context - pass `tools.schemas`: every tool has an object input schema - pass `tools.annotations`: 6 of 6 tools declare readOnlyHint or destructiveHint - warn `tools.directory_hints`: 3 of 6 tools declare all four hints; missing: get_trial_status (destructiveHint, idempotentHint); get_documentation (destructiveHint, idempotentHint); get_trial_onboarding (destructiveHint, idempotentHint) - pass `tools.token_cost`: about 1,763 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump ### stability: 100 (weight 15) - pass `stability.changes`: 4 tool changes in 30 days - pass `stability.rug_pull`: no tool changed its meaning under the same name ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package - tools: 6, about 1,763 tokens to load them all - tool set hash: dcf18c1743f4db8d6f4055c85f79527b - tools last changed: 2026-10-06T23:15:15.555Z - badge: [![protogrid quality](https://protogrid.dev/badge/com.trafficparrot/public.svg)](https://protogrid.dev/servers/com.trafficparrot/public) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-10-06 `get_trial_status` changed (outputSchema) - 2026-10-06 `delete_trial_request` changed (outputSchema) - 2026-10-06 `submit_feature_request` changed (outputSchema) - 2026-10-06 `request_trial` changed (outputSchema) Full history: https://api.protogrid.dev/v1/servers/com.trafficparrot%2Fpublic/changes ## Remotes - https://mcp.trafficparrot.com/ (streamable-http, auth none, reachable true, uptime30d 1) ## Packages _none_ ## Tools (6) - `delete_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. - `get_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`: 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. - `get_trial_status`: 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. - `request_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 takes about a minute to build and the download appears on that page. The trial link goes only to that email address. This tool returns a reference id and no link, so you cannot fetch the download for your user: relay the email steps instead. An address already on Traffic Parrot's trial list gets no new email; the link in its earlier trial email shows the new request. - `submit_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.