Developer · Remote MCP server
FairMind Project Context
Project memory for coding agents: requirements, decisions, code graph and delivery telemetry.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.fairmind/project-context- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-17
- Updated
- 2026-09-17
- Publisher
- ai.fairmind
- Namespace
- Namespace verified by the MCP Registry via the domain fairmind.ai · how
- Website
- www.fairmind.ai
- Repository
- github.com/FairMind-Gen-AI-Studio/fairmind-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://project-context.fairmind.ai/mcp/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect FairMind Project Context
FairMind Project Context is a remote MCP server: there is nothing to install. Its endpoint is https://project-context.fairmind.ai/mcp/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| FactReasonCheck exact npm/PyPI upgrades for evidence-backed breaking changes; query APIs and components. | Remote · HTTPLive check: ✓ handshake |
| Facturae Verifactu Lint18 reglas sobre tu XML Facturae antes de que FACe lo devuelva. | Local · stdio |
| fadehost.comManage FadeHost game servers, Discord bots and VPS: console, stats, backups, logs, lifecycle. | Remote · HTTPLive check: ✓ handshake |
| FailTraceDebugging experiments for coding agents: reproduce failures and verify fixes with test evidence. | Local · stdio |
| Fake Star AuditTransparent rule-based GitHub fake-star detector - LOW/MEDIUM/HIGH with per-rule evidence. | Local · stdio |
| Falcon BuilderBuild, debug, and publish production AI agent workflows in Falcon Builder from any MCP client. | Remote · HTTPLive check: sign-in required |
| FallaxFallax is a phishing simulation and security awareness training platform. Read your results. | Remote · HTTPLive check: sign-in required |
| FanoutInvestigate OpenTelemetry traces, metrics, and logs, and manage personal dashboards. | Remote · HTTP |