Publisher portfolio
Wolfe-Jam
Explore the MCP servers published by Wolfe-Jam, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 3
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 0
Active servers with a recorded connection probe
- Latest probe connected
- 0
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 3
Distinct source repositories linked by the active listings
Portfolio overview
MCP servers
Compare connection status and measurements. Open a server for its tools, check results, and client configuration.
| Server / capability | Last probe | Median latency | Checks passed | Last checked |
|---|---|---|---|---|
MCP Context Card MCP server for a project's context (AGENTS.md), memory, and identity — base or drop-in extension. | Not measured | Not measured | 4 / 6 | Not checked yet |
mcp-better AAIF-verified modern MCP setup optimised to the 2026-07-28 model (BETTER textbook). | Not measured | Not measured | 4 / 6 | Not checked yet |
Rust MCP Preflight Check an MCP Registry listing before you publish: README mcp-name line, server.json, name. | Not measured | Not measured | 4 / 6 | Not checked yet |
Company & identity
About Wolfe-Jam
Wolfe-Jam publishes MCP servers under the io.github.Wolfe-Jam namespace. This namespace is associated with a GitHub login in the MCP Registry.
Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.