Power Portals Pro
NUGET · POWERPORTALSPRO.MCP
Component API, code samples and Dataverse metadata for building Power Portals Pro portals.
Available components
Last scanned (8 hours ago)
Scores higher than 66% of NuGet servers
Category Cloud Infrastructure
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 28490 tokens (~271/item across 105 items; 105 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
- Stability check failed: the tool surface changed between 10.0.0 and 13.0.0: 0 tool removals, 1 breaking changes, 35 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 13 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 106 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 12.0.0 → 13.0.0 functional
- 1 Nov 26 0
- Schema quality: 23093 → 27552 ▼ functional
- Package version: 11.4.0 → 12.0.0 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 26 Oct 26 0
- Package version: 11.0.0 → 11.4.0 functional
- 23 Oct 26 0
- Package version: 11.3.0 → 11.4.0 functional
- 22 Oct 26 0
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 11.2.0 → 11.3.0 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 5 Nov 2026 · Analysed nuget/PowerPortalsPro.Mcp@13.0.0
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unverified |
Signer
| Signed as | Repository signature, names nuget.org |
|---|---|
| Subject | CN=NuGet.org Repository by Microsoft,O=NuGet.org Repository by Microsoft,L=Redmond,ST=Washington,C=US |
| Issuer | CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1,O=DigiCert\, Inc.,C=US |
| Valid from | 23 Feb 2024 |
| Valid until | 18 May 2027 |
| Service index | https://api.nuget.org/v3/index.json |
| Owners | PowerPortalsPro |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
Registry declarations For information only
What the registry and the package's own manifest say about this version. The publisher or the registry writes these, nothing here is verified, and none of it affects the score.
| Repository type | git |
|---|---|
| Commit | 0bb48589fecc335d2fd9892860d684eaa4307a0e |
| Project URL | https://github.com/orgs/Power-Portals-Pro |
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 →
swap_slots ~328
Swap two deployment slots of the App Service — usually a tested slot into production. Each slot keeps its own environment settings, so the build from the UAT slot ends up serving production against production's Dataverse, and production's previous build moves to the UAT slot, one swap away. App Service restarts and warms the incoming instances with the target's settings before it moves traffic, so nothing else needs restarting. Refused when the two slots run against different environments and D365__Url is not sticky — that swap would put production's users on the other environment's data. Also warns when the target environment's Power Portals Pro solution is older than the source's. The user is asked to confirm; the first call only returns what will change, to show them, and the second passes the code it names as `confirm`.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string|null | – | Leave out on the first call, which changes nothing and returns the details to show the user. On the second, the code that call names. |
| environment | string|null | – | The environment whose linked slot holds the build to promote — an alternative to `source`. |
| name | string|null | – | The web app name. Omit to use the one recorded in this workspace's binding. |
| resourceGroup | string|null | – | The resource group, when the name is ambiguous. |
| source | string|null | – | The slot holding the build to promote, e.g. "uat". Omit it to use the slot linked to `environment`. |
| target | string|null | – | The slot to swap into. Defaults to production. |
No output schema declared.
No examples provided.
update_portal_role ~276
Change a Portal Role: rename it, set its description, or activate/deactivate it. Only the arguments you pass are changed. Deactivating is the safe way to switch a role off — an inactive role grants nothing and mints no claim, but its assignments survive, so reactivating restores everyone who held it. Renaming is the dangerous one: the name is the only thing joining the record to the AddPortalRole call, so renaming here without changing the code silently revokes the role from everybody holding it.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean|null | – | true to activate, false to deactivate. Omit to leave the state alone. |
| description | string|null | – | A new description. Pass an empty string to clear it. |
| environment | string|null | – | Which of this folder's Dataverse environments to use: its name (e.g. "test"), its position in the list ("2") or its URL. Omit it to use the primary environment, and only name another when the user as… |
| name | string | yes | The current name of the role to change. |
| newName | string|null | – | A new name. Change the matching AddPortalRole call too, or the role stops granting anything. |
No output schema declared.
No examples provided.
update_portal_role_configuration ~237
Change how a role is handed to newly registered users: switch its assignment mode, replace its FetchXML criteria, or activate/deactivate the row. Only the arguments you pass are changed. Criteria is validated before writing, the same as on create. Assignment needs both this row and the role it names to be active.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean|null | – | true to activate, false to deactivate. Omit to leave the state alone. |
| assignmentMode | string|null | – | New assignment mode: "automatic", "criteria" or "none". |
| criteria | string|null | – | New FetchXML criteria, rooted in "contact". Pass an empty string to clear it. |
| environment | string|null | – | Which of this folder's Dataverse environments to use: its name (e.g. "test"), its position in the list ("2") or its URL. Omit it to use the primary environment, and only name another when the user as… |
| roleName | string | yes | Name of the Portal Role whose configuration row should change. |
No output schema declared.
No examples provided.
update_portal_website ~247
Change a Power Portals Pro Website record: correct its URL, set a new license key, or activate/deactivate it. Only the arguments you pass are changed. Deactivating has the same effect as deleting — every data endpoint on that host starts returning 402 — but is reversible, so prefer it. License key values are never read back, only written.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean|null | – | true to activate, false to deactivate. Omit to leave the state alone. |
| environment | string|null | – | Which of this folder's Dataverse environments to use: its name (e.g. "test"), its position in the list ("2") or its URL. Omit it to use the primary environment, and only name another when the user as… |
| licenseKey | string|null | – | A new license key. Pass an empty string to clear it, which makes the check fail. |
| newUrl | string|null | – | A corrected URL. The license check matches this against the request's host. |
| url | string | yes | The current URL of the record to change. |
No output schema declared.
No examples provided.
whats_new ~142
Return PowerPortalsPro release notes, newest first. Use it to check when a feature arrived or whether something changed behavior, especially if the project's pinned version is older than this server's.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum releases to return (1-10, default 3). |
| sinceVersion | string|null | – | Only include releases after this version, e.g. "6.1". Omit for the most recent few. |
| version | string|null | – | Return only this release's notes, in full rather than shortened, e.g. "9.1.0.0". Use it when get_upgrade_plan omits a breaking change's detail. |
No output schema declared.
No examples provided.
How do I install the Power Portals Pro MCP server?
Power Portals Pro runs locally as a NuGet package, launched with dnx PowerPortalsPro.Mcp@13.0.0 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · PowerPortalsPro.Mcp
claude mcp add power-portals-pro-powerportalspro-mcp -- dnx PowerPortalsPro.Mcp@13.0.0 --yes
What is the Power Portals Pro MCP server?
Power Portals Pro is an MCP server listed in the public MCP registry as io.github.Power-Portals-Pro/powerportalspro-mcp. Component API, code samples and Dataverse metadata for building Power Portals Pro portals. This page covers its NuGet package (PowerPortalsPro.Mcp).
Is the Power Portals Pro MCP server safe to use?
Power Portals Pro scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Power Portals Pro MCP server expose?
Power Portals Pro exposes 105 tools: add_app_registration_certificate, add_app_registration_federated_credential, add_app_registration_redirect_uri, add_app_registration_secret, add_powerbi_rls_role, and 100 more. Their descriptions and schemas cost roughly 28,369 tokens of context every time the server is loaded.
Is the Power Portals Pro MCP server still maintained?
Power Portals Pro is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.