Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
XFA's remote MCP server — query device posture, compliance, policies & CVEs. Read-only.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.xfa.tech/mcpRun this in your terminal
claude mcp add --transport http xfa https://mcp.xfa.tech/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"xfa": {
"url": "https://mcp.xfa.tech/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"xfa": {
"type": "http",
"url": "https://mcp.xfa.tech/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.xfa.tech/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain xfa.tech (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
XFA is a BYOD device-trust platform. This is XFA's remote [Model Context Protocol](https://modelcontextprotocol.io) server — query your organization's device posture, compliance, policies, and software/CVE status from Claude, ChatGPT, Cursor, and other AI assistants. Read-only.
This repository is the connector package for AI marketplaces. The MCP server itself is hosted by XFA at https://mcp.xfa.tech/mcp; nothing runs locally. Authentication is OAuth 2.0 (PKCE) — you sign in with your XFA account on connect.
| Surface | Status | Where to submit / find |
|---|---|---|
| Official MCP Registry | ✅ Live | tech.xfa/xfa · registry.modelcontextprotocol.io |
| Glama | ⏳ Propagating from registry | glama.ai/mcp/servers |
| Smithery | ⏳ Propagating from registry | smithery.ai |
| PulseMCP | ⏳ Propagating from registry | pulsemcp.com |
| mcp.so | ⏳ Propagating from registry | mcp.so |
| Cursor Marketplace | 🕒 Submitted — pending approval | cursor.com/marketplace/publish |
| Claude Connectors Directory | ✅ Live | claude.ai/directory/mcp-xfa-tech |
| ChatGPT app directory | ✅ Live | chatgpt.com/plugins/… |
| Gemini / Antigravity CLI | ✅ Installable · ⏳ gallery auto-crawl | gemini-cli-extension topic set; also via the MCP Registry |
| awesome-mcp-servers | 🕒 PR open — #12739 | Security section |
_Legend: ✅ live · ⏳ propagating (no action) · 🕒 pending. Update a row when its listing goes live._
Gemini note: the Gemini CLI gallery has no submission form — it crawls public repos
tagged with the
gemini-cli-extensionGitHub topic daily (already set). Gemini CLI merged
into Antigravity CLI (June 2026); Antigravity discovers MCP servers via the MCP Registry,
where this server is already live, so no separate Antigravity submission is needed.
One-click:
cursor://anysphere.cursor-deeplink/mcp/install?name=xfa&config=eyJ1cmwiOiJodHRwczovL21jcC54ZmEudGVjaC9tY3AifQ==
Or add to ~/.cursor/mcp.json:
{
"mcpServers": { "xfa": { "url": "https://mcp.xfa.tech/mcp" } } }
Settings → Connectors → Add custom connector → URL https://mcp.xfa.tech/mcp.
Settings → Connectors → Add → MCP server URL https://mcp.xfa.tech/mcp.
Install the extension:
gemini extensions install https://github.com/gl-ventures/xfa-mcp
The bundled gemini-extension.json points at the remote server; Gemini discovers OAuth from the server metadata and prompts you to sign in on first use.
Point the client at the remote URL https://mcp.xfa.tech/mcp (streamable HTTP / SSE, OAuth 2.0).
All tools are read-only. The live server is the source of truth — clients fetch the current tool list from the endpoint on every connection, so this list may lag the deployed server. See the Connect an AI assistant docs for the maintained reference.
Your organization (scoped to the signed-in user's org)
| Tool | Description |
|---|---|
get_organization | Get your XFA organization |
get_current_user | Get the signed-in user |
list_devices | List devices (active in the last 30 days) |
get_device | Get a single device |
get_compliance_summary | Org-wide compliance summary |
get_posture_trends | Posture trends over time |
list_policies | List policies |
Software & vulnerabilities (XFA's tracked-software catalog)
| Tool | Description |
|---|---|
get_latest_version | Latest known version of a piece of software |
list_versioned_software_catalog | List the software XFA tracks |
get_software_version_info | Status of a specific software version |
get_cves_for_version | CVEs affecting a software version |
OAuth 2.0 with PKCE (S256), scope mcp:read. On connect you are redirected to XFA to authorize; no API keys or tokens are stored in this package. The client auto-discovers the OAuth endpoints from the server's already-published metadata:
https://mcp.xfa.tech/.well-known/oauth-protected-resourcehttps://mcp.xfa.tech/.well-known/oauth-authorization-serverThe MCP Registry workflow validates server.json on every change and publishes to the official MCP Registry on pushes to main (or via Run workflow). It authenticates by DNS against the v=MCPv1 TXT record on the xfa.tech apex.
To release a new version: bump version in server.json, merge to main.
Required repo secret: `MCP_REGISTRY_KEY_PEM` — the Ed25519 private key PEM (pairs with the DNS TXT record). Keep the matching key backed up in a password manager.
MIT — see LICENSE.