Ferryhopper MCP
https://mcp.ferryhopper.com/mcp
Severity breakdown
Worst finding
Tool `get_disruptions` accepts unconstrained string input
· get_disruptions
The following string parameter(s) have no `maxLength` constraint: `country`, `tripDate`. Unbounded strings let an attacker stuff arbitrary payloads through the tool, including indirect-injection content.
fix: Add a `maxLength` to each string property, or constrain with an `enum` or `pattern`. Most legitimate tool inputs fit under a few hundred bytes.
All 3 findings
- mediumTool `get_disruptions` accepts unconstrained string input· get_disruptionsunconstrained input
The following string parameter(s) have no `maxLength` constraint: `country`, `tripDate`. Unbounded strings let an attacker stuff arbitrary payloads through the tool, including indirect-injection content.
fix: Add a `maxLength` to each string property, or constrain with an `enum` or `pattern`. Most legitimate tool inputs fit under a few hundred bytes.
- mediumTool `get_direct_connections_for_ports` accepts unconstrained string input· get_direct_connections_for_portsunconstrained input
The following string parameter(s) have no `maxLength` constraint: `portLocation`. Unbounded strings let an attacker stuff arbitrary payloads through the tool, including indirect-injection content.
fix: Add a `maxLength` to each string property, or constrain with an `enum` or `pattern`. Most legitimate tool inputs fit under a few hundred bytes.
- mediumTool `search_trips` accepts unconstrained string input· search_tripsunconstrained input
The following string parameter(s) have no `maxLength` constraint: `arrivalLocation`, `date`, `departureLocation`. Unbounded strings let an attacker stuff arbitrary payloads through the tool, including indirect-injection content.
fix: Add a `maxLength` to each string property, or constrain with an `enum` or `pattern`. Most legitimate tool inputs fit under a few hundred bytes.
How this was scored
Source http — live HTTP MCP endpoint, classified against every rule. Findings are emitted by the public capframe.findings.v1 schema. Score = 100 − (10·Critical + 4·High + 2·Medium + 1·Low), clamped to [0, 100].
Disagree with a finding? Open an issue.