ai.foura/mcp
ai-foura-mcp declares 4 capabilities across 4 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
4 of 4 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
4 of 4 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
4 of 4 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
4 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
foura_single | read |
declared |
foura_proxy | read |
declared |
foura_browser | read |
declared |
foura_auto | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-05 | 7 | tools/list on https://mcp.foura.ai/mcp, published in the official MCP registry as ai.foura/mcp 0.7.3 |
| 2026-09-21 | 7 | tools/list on https://mcp.foura.ai/mcp, published in the official MCP registry as ai.foura/mcp 0.7.2 |
| 2026-09-14 | 7 | tools/list on https://mcp.foura.ai/mcp, published in the official MCP registry as ai.foura/mcp 0.6.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.