Tyk review MCP configuration and Redis script checks
Pinned checks of Tyk MCP extension schemas and an isolated Redis sliding-log script, with deployment, licensing and runtime-testing boundaries.
AgentIndex · Published 2026-11-05 · Updated 2026-11-05
Tyk is relevant to teams that need a common governance layer for API and MCP access. Selection starts with the intended integration: proxying a remote MCP service, exposing REST operations as tools, and choosing the authentication and policy features required by that deployment.
We checked bundled MCP extension schemas and independently executed a Redis sliding-log script. The schema rejected selected configuration mistakes and the script reported window counts. Neither result establishes complete gateway authentication, HTTP rejection behavior or MCP interoperability.
Pinned source and local scope
We fixed commit b9b2beed22f656ea6779c6d0d4834f24afb289d8 on November 5, 2026. A full source build failed when host temporary storage filled. We removed the task-created toolchain and caches afterward. This was an environment limitation, not a verified Tyk build defect, and the gateway was never launched.
The completed checks used Python 3.12.13, jsonschema 4.26.0 and Redis 8.10.0. Python Draft4Validator read two extension schemas directly; we did not run Tyk's Go validator or combine a complete OpenAPI document. Redis ran in its own disposable process on a private Unix socket. The reproduction fixture records source hashes and limitations.
| Check | Observed behavior |
|---|---|
| Minimal valid gateway extension | Accepted |
| Missing active state, listen path or upstream setup | Selected invalid specimens rejected |
| String value for the strip flag | Rejected |
| MCP primitive name containing spaces | Rejected |
| String readOnlyHint or unknown primitive property | Rejected |
| Empty MCP extension | Structurally accepted |
| Well-formed URL at an unavailable local port | Structurally accepted |
| Three direct Redis script calls | Prior counts 0, 1, 2; remaining 1, 0, 0 |
| Window advance, separate keys and expiry | Updated as expected for the fixtures |
Seventeen checks passed. Structural acceptance does not establish reachability, and counter output does not establish an HTTP rate-limit response.
Catch configuration mistakes before deployment
The gateway extension requires state and listening-path information. Removing active state or the path value, or supplying a string instead of a boolean, produced errors. An empty upstream was rejected. The MCP primitive schema constrained names, annotation types and unexpected properties. Gateway schema, MCP schema
Those checks are useful during configuration review. They provide localized feedback about types and required values before traffic is involved. But a valid URL pointed at an unavailable local port still passed, and an empty MCP extension passed its own schema. A callable tool needs a complete definition, valid operation mapping, credentials, an upstream response and a compatible client.
The readOnlyHint test is particularly easy to overinterpret. We established that the field expects a boolean. We did not establish that an upstream operation is harmless or read-only. Enforce and test actual permissions rather than treating an annotation as an access-control decision.
A counter is only one part of enforcement
We executed the original sliding_log_add.lua with a limit argument of two. Three calls reported prior counts of zero, one and two, with remaining values one, zero and zero. The third attempt was still inserted into the sorted set. Advancing the window removed older entries, separate keys kept independent counts and expiry was applied. Lua implementation
The script records attempts; a caller decides whether to block. Its Go wrapper is marked deprecated and incomplete in the pinned source, and we did not execute that wrapper. Direct script output must not be presented as an end-to-end production enforcement result. Calling code
Reusing an identical timestamp reused the same sorted-set member in our fixture. An integration needs clear semantics for keys, time and request identity before interpreting counters under concurrency or failure. This review contains no throughput, latency or distributed-deployment benchmark.
Match the MCP integration to the product
The official documentation distinguishes remote MCP proxies from REST-to-MCP conversion. It specifies Tyk OAS definitions, Streamable HTTP, version requirements and enterprise conditions. Stdio is not supported as that remote transport, and REST conversion and some authentication capabilities have separate licensing requirements. Official integration limits
For a trial, identify the client's transport, upstream service, credential owner and required tool permissions first. Then exercise normal calls, missing credentials, denied access and exceeded limits against a controlled real service. Verify whether each request reached the upstream. Those runtime checks remain necessary; they were not completed here.
Licensing and adoption
The pinned root license places code outside ee under MPL 2.0 and assigns the ee directory a separate commercial license. We corrected the catalog's previous NOASSERTION field to reflect the source's stated scope. This review does not describe the entire tree as a single permissively licensed package. Root license, enterprise directory notice
The README's open-source quick start uses Gateway and Redis, while the full management platform introduces other components and conditions. Teams already maintaining API policies can consider a bounded Tyk trial. For a single local tool, first assess whether the additional gateway operations are justified. Project entry point
Continue with the MCP server selection guide for service choices, or the MCP TypeScript SDK review when building a server.