io.fusionauth/mcp-api
NPM · @FUSIONAUTH/MCP-API
Preview release of FusionAuth API MCP server
Available components
Last scanned (15 hours ago)
Scores higher than 53% of npm servers
Category Security
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 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.
- 9 Nov 26 +5
- Source repository: unverified → pass ▲ security
- 8 Nov 26 −7
- Provenance: pass → unverified ▼ security
- Stability: pass → 0.87 functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
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 21 Nov 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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 108 packages
| Packages resolved | 108 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
updateUserVerifyEmail ~146
Re-sends the verification email to the user. If the Application has configured a specific email template this will be used instead of the tenant configuration. OR Re-sends the verification email to the user. OR Generate a new Email Verification Id to be used with the Verify Email API. This API will not attempt to send an email to the User. This API may be used to collect the verificationId for use with a third party system.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | – | The unique Application Id to used to resolve an application specific email template. |
| string | – | The email address of the user that needs a new verification email. | |
| sendVerifyEmail | string | – | – |
No output schema declared.
No examples provided.
updateUserVerifyRegistration ~115
Re-sends the application registration verification email to the user. OR Generate a new Application Registration Verification Id to be used with the Verify Registration API. This API will not attempt to send an email to the User. This API may be used to collect the verificationId for use with a third party system.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | – | The Id of the application to be verified. |
| string | – | The email address of the user that needs a new verification email. | |
| sendVerifyPasswordEmail | string | – | – |
No output schema declared.
No examples provided.
updateUserWithId ~108
Updates the user with the given Id. OR Reactivates the user with the given Id.
| Name | Type | Req | Description |
|---|---|---|---|
| X-FusionAuth-TenantId | string | – | 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. |
| reactivate | string | – | – |
| requestBody | object | – | User API request object. |
| userId | string | yes | The Id of the user to update. |
No output schema declared.
No examples provided.
updateWebhookWithId ~46
Updates the webhook with the given Id.
| Name | Type | Req | Description |
|---|---|---|---|
| requestBody | object | – | Webhook API request object. |
| webhookId | string | yes | The Id of the webhook to update. |
No output schema declared.
No examples provided.
upsertEntityGrantWithId ~113
Creates or updates an Entity Grant. This is when a User/Entity is granted permissions to an Entity.
| Name | Type | Req | Description |
|---|---|---|---|
| X-FusionAuth-TenantId | string | – | 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. |
| entityId | string | yes | The Id of the Entity that the User/Entity is being granted access to. |
| requestBody | object | – | Entity grant API request object. |
No output schema declared.
No examples provided.
validateDeviceWithId ~74
Validates the end-user provided user_code from the user-interaction of the Device Authorization Grant. If you build your own activation form you should validate the user provided code prior to beginning the Authorization grant.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | The client Id. |
| user_code | string | – | The end-user verification code. |
No output schema declared.
No examples provided.
validateJWTWithId ~63
Validates the provided JWT (encoded JWT string) to ensure the token is valid. A valid access token is properly signed and not expired. <p> This API may be used to verify the JWT as well as decode the encoded JWT into human readable identity claims.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vendJWTWithId ~150
It's a JWT vending machine! Issue a new access token (JWT) with the provided claims in the request. This JWT is not scoped to a tenant or user, it is a free form token that will contain what claims you provide. <p> The iat, exp and jti claims will be added by FusionAuth, all other claims must be provided by the caller. If a TTL is not provided in the request, the TTL will be retrieved from the default Tenant or the Tenant specified on the request either by way of the X-FusionAuth-TenantId request header, or a tenant scoped API key.
| Name | Type | Req | Description |
|---|---|---|---|
| requestBody | object | – | The JSON request body. |
No output schema declared.
No examples provided.
verifyIdentityWithId ~36
Administratively verify a user identity.
| Name | Type | Req | Description |
|---|---|---|---|
| requestBody | object | – | Identity verify request. Used to administratively verify an identity. |
No output schema declared.
No examples provided.
verifyUserRegistrationWithId ~131
Confirms a user's registration. The request body will contain the verificationId. You may also be required to send a one-time use code based upon your configuration. When the application is configured to gate a user until their registration is verified, this procedures requires two values instead of one. The verificationId is a high entropy value and the one-time use code is a low entropy value that is easily entered in a user interactive form. The two values together are able to confirm a user's registration and mark the user's registration as verified.
| Name | Type | Req | Description |
|---|---|---|---|
| requestBody | object | – | The JSON request body. |
No output schema declared.
No examples provided.
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
claude mcp add io-fusionauth-mcp-api -- npx -y @fusionauth/mcp-api
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 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 21 November 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.
What did VerifyMCP test on the io.fusionauth/mcp-api server?
VerifyMCP ran 16 checks on io.fusionauth/mcp-api, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.