MCP security report

mockbird.mockbird.workers.dev

D46/100
Security grade DA few things are worth a closer look before connecting.
Connected ✓15 tools scanned

https://mockbird.mockbird.workers.dev/mcp

mediumuptime_monitor
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumheartbeat
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumwatch_service_status
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
lowheartbeat
Unusually long tool description
Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.
low
Not on gate's verified list
This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.
lowinspect_requests
Captures and exposes raw request headers/bodies
The inspector returns captured headers (including arbitrary x-* headers) and body snippets for any request hitting the mock API. While authorization is redacted to its scheme, other sensitive headers (e.g. API keys sent as x-api-key, custom auth tokens) could be logged and returned verbatim to whoever holds the adminKey. This is inherent to the tool's debugging purpose but is a capability worth flagging since it could inadvertently surface credentials a user points at the mock endpoint during testing.
lowcustom_route
Arbitrary response templating with request reflection
custom_route lets a caller define catch-all routes (e.g. /webhooks/*) that echo back {{headers.x}}, {{body}}, etc. Combined with inspect_requests, this creates a general-purpose request bin. This is a legitimate, disclosed feature for webhook testing, but agents should be cautious about using it to capture data from real third-party systems (e.g. pointing a production webhook at a catch-all route) since captured payloads/headers are retained and retrievable by anyone with the adminKey.
lowuptime_monitor
Sends status data to arbitrary user-supplied webhook
The notify parameter forwards monitoring alerts (with HMAC signature) to any HTTPS URL supplied by the caller. This is standard, disclosed functionality, but agents should confirm with the user before wiring monitoring data to a webhook endpoint, especially if the notify URL is inferred rather than explicitly provided by the user.
lowheartbeat
Sends status data to arbitrary user-supplied webhook
Same pattern as uptime_monitor: the notify parameter routes missed-check-in alerts to any external HTTPS endpoint. Disclosed and functional, but worth confirming the destination is genuinely user-intended rather than agent-assumed.
lowwatch_service_status
Sends status data to arbitrary user-supplied webhook
Same notify-to-arbitrary-webhook pattern as uptime_monitor/heartbeat; low risk but agents should verify the notify URL was explicitly provided by the user rather than guessed or reused from another context.
Embed this badge

Show your MCP server’s security grade

MCP security grade D

Paste this into your README:

[![MCP security](https://gateturbo.com/badge/scan/510764f7-4717-4fbc-b11d-9ea337969cf5)](https://gateturbo.com/report/510764f7-4717-4fbc-b11d-9ea337969cf5)

Scanned 9/8/2026 · This is a point-in-time snapshot of the server’s public tools. Re-scan.

Connect this server safely with gate.

Continuous re-scans, drift alerts, per-tool allow/ask/block, and a log of every call.

Monitor it — free