MCPaaS uses endpoints, they need a name, so we called them Namepoints. It's your handle on MCPaaS — a permanent address for your AI context. Claim one at mcpaas.live/claim.
Is it free?
Yes, all our tools are available for free. FAFHub sync is free. Namepoint handles with 2 numbers like james99 or katie78 are free. Prestige names like katie without numbers start at $2/mo founding price.
What is MCPaaS?
MCP as a Service. Persistent AI context delivered from 300+ edge locations via Cloudflare Workers. Your namepoint is your address for context.
What is FAFHub?
FAFHub imports project.faf files from any Git repo (GitHub, GitLab, Bitbucket, Gitea) and makes them live namepoints.
What is a .faf file?
The IANA-registered format (application/vnd.faf+yaml) for project DNA. Gives AI tools persistent context about your codebase.
Why do I need .faf if I have CLAUDE.md or AGENTS.md?
FAF defines your entire project DNA and scores it. AI consumes it in milliseconds. MD is prose — instructions, not definitions. It's not structured data. AI interprets prose and has to build context from scratch every time. It varies, and drift creeps in over time. FAF gets AI optimized, so you can use your time and tokens on coding your project with your AI assistant in sync, no drift. FAF was IANA-registered in October 2025 — before many of these .md formats had even been introduced, let alone registered as a standard. FAF defines. MD instructs. AI codes.
Does .faf work with Claude Code Skills?
Yes. FAF predates Skills — and when Anthropic chose YAML front-matter for the Skills format, it tied in beautifully with YAML-based .faf. The faf-expert skill is available in awesome-skills and gives Claude deep knowledge of the .faf format, scoring, and bi-sync.
Does .faf work with MCP?
Yes — FAF is the only official Anthropic MCP for persistent project context (#2759, merged October 2025). Since then we've shipped faf-mcp for Cursor/IDEs, grok-faf-mcp (first Grok and web MCP), gemini-faf-mcp on FastAPI, and rust-faf-mcp on RMCP.
What happens when two agents read the same context at once?
Each agent gets its own independent snapshot. Reads (99% of MCPaaS traffic) are stateless KV gets at the nearest edge — perfectly concurrent. Writes are last-write-wins, but write_soul appends entries rather than replacing, so multi-agent writes are safe in practice.
Does context just grow forever? Can I prune it?
It's your context — you're the boss. Every namepoint has tagged sections ([public][faf][claude][agents][gemini][grok][cursor][private]) and a full editor. Download, copy, edit, or rebuild from your repo in milliseconds with FAFHub. You control what stays and what goes.
How do I create a .faf file?
Run npx faf-cli init in your project, or npx faf-cli auto for zero-config generation.
