Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.fusionauth/mcp-api

NPM · @FUSIONAUTH/MCP-API · SCANNED SEP 24

Preview release of FusionAuth API MCP server

Available components

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 34 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 22835 tokens (~73/item across 310 items; 310 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 44 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deleteAPIKeyWithId" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 310 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.fusionauth/mcp-api server?

io.fusionauth/mcp-api runs locally as an npm package, launched with npx -y @fusionauth/mcp-api. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @fusionauth/mcp-api

# add to Claude Code
claude mcp add io-fusionauth-mcp-api -- npx -y @fusionauth/mcp-api
// .cursor/mcp.json
{
  "mcpServers": {
    "io-fusionauth-mcp-api": {
      "command": "npx",
      "args": [
        "-y",
        "@fusionauth/mcp-api"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-fusionauth-mcp-api": {
      "command": "npx",
      "args": [
        "-y",
        "@fusionauth/mcp-api"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add io-fusionauth-mcp-api -- npx -y @fusionauth/mcp-api
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-fusionauth-mcp-api": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@fusionauth/mcp-api"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-fusionauth-mcp-api --command npx --arg -y --arg @fusionauth/mcp-api
# ~/.hermes/config.yaml
mcp_servers:
  io-fusionauth-mcp-api:
    command: "npx"
    args: ["-y", "@fusionauth/mcp-api"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-fusionauth-mcp-api": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@fusionauth/mcp-api"
      ]
    }
  }
}
# add to Vellum
assistant mcp add io-fusionauth-mcp-api -t stdio -c npx -a -y @fusionauth/mcp-api
// mcp.json
{
  "mcpServers": {
    "io-fusionauth-mcp-api": {
      "command": "npx",
      "args": [
        "-y",
        "@fusionauth/mcp-api"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Analysed npm/@fusionauth/mcp-api@0.1.14

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 111 packages
Packages resolved 111
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 310 exposed · ~22,835 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
deleteUserTwoFactorWithId ~107

Disable two-factor authentication for a user using a JSON body rather than URL parameters. OR Disable two-factor authentication for a user.

NameTypeReqDescription
codestring–The two-factor code used verify the the caller knows the two-factor secret.
methodIdstring–The two-factor method identifier you wish to disable
requestBodyobject–The JSON request body.
userIdstringyesThe Id of the User for which you're disabling two-factor authentication.

No output schema declared.

No examples provided.

deleteUserWithId ~164

Deletes the user based on the given request (sent to the API as JSON). This permanently deletes all information, metrics, reports and data associated with the user. OR Deletes the user for the given Id. This permanently deletes all information, metrics, reports and data associated with the user. OR Deactivates the user with the given Id.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
hardDeletestring––
requestBodyobject–User API delete request object for a single user.
userIdstringyesThe Id of the user to delete (required).

No output schema declared.

No examples provided.

deleteWebAuthnCredentialWithId ~41

Deletes the WebAuthn credential for the given Id.

NameTypeReqDescription
idstringyesThe Id of the WebAuthn credential to delete.

No output schema declared.

No examples provided.

deleteWebhookWithId ~33

Deletes the webhook for the given Id.

NameTypeReqDescription
webhookIdstringyesThe Id of the webhook to delete.

No output schema declared.

No examples provided.

enableTwoFactorWithId ~49

Enable two-factor authentication for a user.

NameTypeReqDescription
requestBodyobject–The JSON request body.
userIdstringyesThe Id of the user to enable two-factor authentication.

No output schema declared.

No examples provided.

exchangeRefreshTokenForJWTWithId ~34

Exchange a refresh token for a new JWT.

NameTypeReqDescription
requestBodyobject–The JSON request body.

No output schema declared.

No examples provided.

forgotPasswordWithId ~44

Begins the forgot password sequence, which kicks off an email to the user so that they can reset their password.

NameTypeReqDescription
requestBodyobject–Forgot password request object.

No output schema declared.

No examples provided.

generateKey ~34

Generate a new RSA or EC key pair or an HMAC secret.

NameTypeReqDescription
requestBodyobject–Key API request object.

No output schema declared.

No examples provided.

generateKeyWithId ~60

Generate a new RSA or EC key pair or an HMAC secret.

NameTypeReqDescription
keyIdstringyesThe Id for the key. If not provided a secure random UUID will be generated.
requestBodyobject–Key API request object.

No output schema declared.

No examples provided.

generateTwoFactorRecoveryCodesWithId ~55

Generate two-factor recovery codes for a user. Generating two-factor recovery codes will invalidate any existing recovery codes.

NameTypeReqDescription
userIdstringyesThe Id of the user to generate new Two Factor recovery codes.

No output schema declared.

No examples provided.

generateTwoFactorSecretUsingJWTWithId ~69

Generate a Two Factor secret that can be used to enable Two Factor authentication for a User. The response will contain both the secret and a Base32 encoded form of the secret which can be shown to a User when using a 2 Step Authentication application such as Google Authenticator.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

identityProviderLoginWithId ~103

Handles login via third-parties including Social login, external OAuth and OpenID Connect, and other login systems.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
requestBodyobject–Login API request object used for login to third-party systems (i.e. Login with Facebook).

No output schema declared.

No examples provided.

importKey ~34

Import an existing RSA or EC key pair or an HMAC secret.

NameTypeReqDescription
requestBodyobject–Key API request object.

No output schema declared.

No examples provided.

importKeyWithId ~60

Import an existing RSA or EC key pair or an HMAC secret.

NameTypeReqDescription
keyIdstringyesThe Id for the key. If not provided a secure random UUID will be generated.
requestBodyobject–Key API request object.

No output schema declared.

No examples provided.

importRefreshTokensWithId ~144

Bulk imports refresh tokens. This request performs minimal validation and runs batch inserts of refresh tokens with the expectation that each token represents a user that already exists and is registered for the corresponding FusionAuth Application. This is done to increases the insert performance. Therefore, if you encounter an error due to a database key violation, the response will likely offer a generic explanation. If you encounter an error, you may optionally enable additional validation to receive a JSON response body with specific validation errors. This will slow the request down but will allow you to identify the cause of the failure. See the validateDbConstraints request parameter.

NameTypeReqDescription
requestBodyobject–Refresh Token Import request.

No output schema declared.

No examples provided.

importUsersWithId ~138

Bulk imports users. This request performs minimal validation and runs batch inserts of users with the expectation that each user does not yet exist and each registration corresponds to an existing FusionAuth Application. This is done to increases the insert performance. Therefore, if you encounter an error due to a database key violation, the response will likely offer a generic explanation. If you encounter an error, you may optionally enable additional validation to receive a JSON response body with specific validation errors. This will slow the request down but will allow you to identify the cause of the failure. See the validateDbConstraints request parameter.

NameTypeReqDescription
requestBodyobject–Import request.

No output schema declared.

No examples provided.

importWebAuthnCredentialWithId ~39

Import a WebAuthn credential

NameTypeReqDescription
requestBodyobject–API request to import an existing WebAuthn credential(s)

No output schema declared.

No examples provided.

issueJWTWithId ~150

Issue a new access token (JWT) for the requested Application after ensuring the provided JWT is valid. A valid access token is properly signed and not expired. <p> This API may be used in an SSO configuration to issue new tokens for another application after the user has obtained a valid token from authentication.

NameTypeReqDescription
applicationIdstring–The Application Id for which you are requesting a new access token be issued.
refreshTokenstring–An existing refresh token used to request a refresh token in addition to a JWT in the response. <p>The target application represented by the applicationId request parameter must have refresh tokens e…

No output schema declared.

No examples provided.

loginPingWithId ~196

Sends a ping to FusionAuth indicating that the user was automatically logged into an application. When using FusionAuth's SSO or your own, you should call this if the user is already logged in centrally, but accesses an application where they no longer have a session. This helps correctly track login counts, times and helps with reporting.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
applicationIdstringyesThe Id of the application that they logged into.
callerIPAddressstring–The IP address of the end-user that is logging in. If a null value is provided the IP address will be that of the client or last proxy that sent the request.
userIdstringyesThe Id of the user that was logged in.

No output schema declared.

No examples provided.

loginPingWithRequestWithId ~135

Sends a ping to FusionAuth indicating that the user was automatically logged into an application. When using FusionAuth's SSO or your own, you should call this if the user is already logged in centrally, but accesses an application where they no longer have a session. This helps correctly track login counts, times and helps with reporting.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
requestBodyobject–Login Ping API request object.

No output schema declared.

No examples provided.

loginWithId ~95

Authenticates a user to FusionAuth. This API optionally requires an API key. See <code>Application.loginConfiguration.requireAuthentication</code>.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
requestBodyobject–Login API request object.

No output schema declared.

No examples provided.

lookupIdentityProviderWithId ~60

Retrieves the identity provider for the given domain. A 200 response code indicates the domain is managed by a registered identity provider. A 404 indicates the domain is not managed.

NameTypeReqDescription
domainstring–The domain or email address to lookup.

No output schema declared.

No examples provided.

modifyActionWithId ~69

Modifies a temporal user action by changing the expiration of the action and optionally adding a comment to the action.

NameTypeReqDescription
actionIdstringyesThe Id of the action to modify. This is technically the user action log Id.
requestBodyobject–The user action request object.

No output schema declared.

No examples provided.

passwordlessLoginWithId ~33

Complete a login request using a passwordless code

NameTypeReqDescription
requestBodyobject–The JSON request body.

No output schema declared.

No examples provided.

patchAPIKeyWithId ~58

Updates an API key with the given Id.

NameTypeReqDescription
keyIdstringyesThe Id of the API key. If not provided a secure random api key will be generated.
requestBodyobject–Authentication key request object.

No output schema declared.

No examples provided.

patchApplicationRoleWithId ~117

Updates, via PATCH, the application role with the given Id for the application.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
applicationIdstringyesThe Id of the application that the role belongs to.
requestBodyobject–The Application API request object.
roleIdstringyesThe Id of the role to update.

No output schema declared.

No examples provided.

patchApplicationWithId ~94

Updates, via PATCH, the application with the given Id.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
applicationIdstringyesThe Id of the application to update.
requestBodyobject–The Application API request object.

No output schema declared.

No examples provided.

patchConnectorWithId ~49

Updates, via PATCH, the connector with the given Id.

NameTypeReqDescription
connectorIdstringyesThe Id of the connector to update.
requestBodyobject–The JSON request body.

No output schema declared.

No examples provided.

patchConsentWithId ~95

Updates, via PATCH, the consent with the given Id.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
consentIdstringyesThe Id of the consent to update.
requestBodyobject–API request for User consent types.

No output schema declared.

No examples provided.

patchEmailTemplateWithId ~96

Updates, via PATCH, the email template with the given Id.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
emailTemplateIdstringyesThe Id of the email template to update.
requestBodyobject–Email template request.

No output schema declared.

No examples provided.

patchEntityTypePermissionWithId ~73

Patches the permission with the given Id for the entity type.

NameTypeReqDescription
entityTypeIdstringyesThe Id of the entityType that the permission belongs to.
permissionIdstringyesThe Id of the permission to patch.
requestBodyobject–Entity Type API request object.

No output schema declared.

No examples provided.

patchEntityTypeWithId ~54

Updates, via PATCH, the Entity Type with the given Id.

NameTypeReqDescription
entityTypeIdstringyesThe Id of the Entity Type to update.
requestBodyobject–Entity Type API request object.

No output schema declared.

No examples provided.

patchEntityWithId ~94

Updates, via PATCH, the Entity with the given Id.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
entityIdstringyesThe Id of the Entity Type to update.
requestBodyobject–Entity API request object.

No output schema declared.

No examples provided.

patchFormFieldWithId ~51

Patches the form field with the given Id.

NameTypeReqDescription
fieldIdstringyesThe Id of the form field to patch.
requestBodyobject–The FormField API request object.

No output schema declared.

No examples provided.

patchFormWithId ~44

Patches the form with the given Id.

NameTypeReqDescription
formIdstringyesThe Id of the form to patch.
requestBodyobject–Form response.

No output schema declared.

No examples provided.

patchGroupWithId ~93

Updates, via PATCH, the group with the given Id.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
groupIdstringyesThe Id of the group to update.
requestBodyobject–Group API request object.

No output schema declared.

No examples provided.

patchIdentityProviderWithId ~53

Updates, via PATCH, the identity provider with the given Id.

NameTypeReqDescription
identityProviderIdstringyesThe Id of the identity provider to update.
requestBodyobject–The JSON request body.

No output schema declared.

No examples provided.

patchIntegrationsWithId ~31

Updates, via PATCH, the available integrations.

NameTypeReqDescription
requestBodyobject–The Integration Request

No output schema declared.

No examples provided.

patchIPAccessControlListWithId ~56

Update the IP Access Control List with the given Id.

NameTypeReqDescription
accessControlListIdstringyesThe Id of the IP Access Control List to patch.
requestBodyobject–The JSON request body.

No output schema declared.

No examples provided.

patchLambdaWithId ~49

Updates, via PATCH, the lambda with the given Id.

NameTypeReqDescription
lambdaIdstringyesThe Id of the lambda to update.
requestBodyobject–Lambda API request object.

No output schema declared.

No examples provided.

patchMessageTemplateWithId ~56

Updates, via PATCH, the message template with the given Id.

NameTypeReqDescription
messageTemplateIdstringyesThe Id of the message template to update.
requestBodyobject–A Message Template Request to the API

No output schema declared.

No examples provided.

patchMessengerWithId ~49

Updates, via PATCH, the messenger with the given Id.

NameTypeReqDescription
messengerIdstringyesThe Id of the messenger to update.
requestBodyobject–The JSON request body.

No output schema declared.

No examples provided.

patchOAuthScopeWithId ~121

Updates, via PATCH, the custom OAuth scope with the given Id for the application.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
applicationIdstringyesThe Id of the application that the OAuth scope belongs to.
requestBodyobject–The Application Scope API request object.
scopeIdstringyesThe Id of the OAuth scope to update.

No output schema declared.

No examples provided.

patchRegistrationWithId ~108

Updates, via PATCH, the registration for the user with the given Id and the application defined in the request.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
requestBodyobject–Registration API request object.
userIdstringyesThe Id of the user whose registration is going to be updated.

No output schema declared.

No examples provided.

patchSystemConfigurationWithId ~34

Updates, via PATCH, the system configuration.

NameTypeReqDescription
requestBodyobject–Request for the system configuration API.

No output schema declared.

No examples provided.

patchTenantWithId ~93

Updates, via PATCH, the tenant with the given Id.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
requestBodyobject–The JSON request body.
tenantIdstringyesThe Id of the tenant to update.

No output schema declared.

No examples provided.

patchThemeWithId ~49

Updates, via PATCH, the theme with the given Id.

NameTypeReqDescription
requestBodyobject–Theme API request object.
themeIdstringyesThe Id of the theme to update.

No output schema declared.

No examples provided.

patchUserActionReasonWithId ~59

Updates, via PATCH, the user action reason with the given Id.

NameTypeReqDescription
requestBodyobject–User Action Reason API request object.
userActionReasonIdstringyesThe Id of the user action reason to update.

No output schema declared.

No examples provided.

patchUserActionWithId ~98

Updates, via PATCH, the user action with the given Id.

NameTypeReqDescription
X-FusionAuth-TenantIdstring–The unique Id of the tenant used to scope this API request. Only required when there is more than one tenant and the API key is not tenant-scoped.
requestBodyobject–User Action API request object.
userActionIdstringyesThe Id of the user action to update.

No output schema declared.

No examples provided.

patchUserConsentWithId ~49

Updates, via PATCH, a single User consent by Id.

NameTypeReqDescription
requestBodyobject–API response for User consent.
userConsentIdstringyesThe User Consent Id

No output schema declared.

No examples provided.

Common questions

What is the io.fusionauth/mcp-api server?

io.fusionauth/mcp-api is listed in the public MCP registry as io.fusionauth/mcp-api. Preview release of FusionAuth API MCP server. This page covers its npm package (@fusionauth/mcp-api).

Is the io.fusionauth/mcp-api server safe to use?

io.fusionauth/mcp-api scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.fusionauth/mcp-api server expose?

io.fusionauth/mcp-api exposes 310 tools: retrieveJsonWebKeySetWithId, retrieveOpenIdConfigurationWithId, createAPIKey, retrieveAPIKeyWithId, updateAPIKeyWithId, and 305 more. Their descriptions and schemas cost roughly 22,835 tokens of context every time the server is loaded.

Is the io.fusionauth/mcp-api server still maintained?

io.fusionauth/mcp-api is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.fusionauth/mcp-api server under?

io.fusionauth/mcp-api declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.