Back to Browse

Xfa MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

XFA device security, read-only: which devices pass their checks or have known vulnerabilities.

About

XFA device security, read-only: which devices pass their checks or have known vulnerabilities.

Remote endpoints: streamable-http: https://mcp.xfa.tech/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "tech-xfa-xfa": {
      "url": "https://mcp.xfa.tech/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

XFA MCP

XFA is user-driven device security that keeps work moving. Its main value is Verify device security at sign-in: XFA checks every device at sign-in and warns people first. People are prompted to install the XFA app themselves at their first sign-in, and they fix issues themselves: they press Fix and approve the suggested fix where XFA offers one, or follow a step by step guide, and XFA checks again. It covers company, personal and contractor laptops and phones, with no IT team or MDM needed; your organization's settings decide what gets blocked. XFA can also Discover all devices through your identity provider.

This is XFA device security, XFA's remote Model Context Protocol server. Ask Claude, ChatGPT, Cursor and other AI assistants about your organization's devices, their check results, how well they meet your policy, and whether the OS and last-used browser are up to date, and known vulnerabilities (CVEs). Read-only, and scoped to the one organization you approve when you sign in. Device results carry no names or emails of the people who use them.

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.

Where it's published

SurfaceStatusWhere to submit / find
Official MCP Registry✅ Livetech.xfa/xfa · registry.modelcontextprotocol.io
Glama⏳ Propagating from registryglama.ai/mcp/servers
Smithery⏳ Propagating from registrysmithery.ai
PulseMCP⏳ Propagating from registrypulsemcp.com
mcp.so⏳ Propagating from registrymcp.so
Cursor Marketplace🕒 Submitted — pending approvalcursor.com/marketplace/publish
Claude Connectors Directory✅ Liveclaude.ai/directory/mcp-xfa-tech
ChatGPT app directory✅ Livechatgpt.com/plugins/…
Gemini / Antigravity CLI✅ Installable · ⏳ gallery auto-crawlgemini-cli-extension topic set; also via the MCP Registry
awesome-mcp-servers🕒 PR open — #12739Security 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-extension GitHub 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.

Install

Cursor

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" }
  }
}

Claude

Settings → Connectors → Add custom connector → URL https://mcp.xfa.tech/mcp.

ChatGPT

Settings → Connectors → Add → MCP server URL https://mcp.xfa.tech/mcp.

Gemini CLI

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.

VS Code / Windsurf / Zed / other MCP clients

Point the client at the remote URL https://mcp.xfa.tech/mcp (streamable HTTP / SSE, OAuth 2.0).

Tools

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)

ToolDescription
get_organizationGet your XFA organization
get_current_userGet the signed-in user
list_devicesList devices (active in the last 30 days)
get_deviceGet a single device
get_compliance_summaryHow well the organization meets its policy
get_posture_trendsA few check figures over time
list_policiesList policies

Software & vulnerabilities (XFA's tracked-software catalog)

ToolDescription
get_latest_versionLatest known version of a piece of software
list_versioned_software_catalogList the software XFA tracks
get_software_version_infoStatus of a specific software version
get_cves_for_versionCVEs affecting a software version

Authentication

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-resource
  • https://mcp.xfa.tech/.well-known/oauth-authorization-server

Support

Maintainers

The 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.

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!